Read a sample: 1. The Access Question: Who Can Do What, and Where?
On her first week as a cloud administrator, Maya receives a request that sounds straightforward:
> “Please give Jordan access to Azure so he can check the customer portal.”
Maya has enough experience in IT to know that “access” can mean almost anything. Does Jordan need to see whether the portal’s resources exist? Restart an application? Read customer records? Change settings? The request does not say.
She could search for Jordan’s name, find a role that sounds useful, and assign it broadly. The request might then disappear from her queue. But she would not know whether she had solved the right problem—or granted access Jordan never needed.
Instead, Maya asks three questions:
1. Who needs access?
2. What do they need to do?
3. Where do they need to do it?
Those questions form the foundation of this book. Azure access can involve more details than a single sentence can capture, but the identity-role-scope model gives you a reliable place to begin. Identify the person or other security principal, understand the actions required, and locate the boundary within which those actions should be allowed.
This chapter introduces a fictional organization, separates signing in from receiving permission, and gives you a safe way to approach the examples that follow. You do not need to memorize a catalog of Azure roles before you can think clearly about access. You need a useful set of questions.
Northwind Field Services is a fictional company that coordinates maintenance visits for commercial buildings. Its employees schedule work, support technicians, and maintain a customer portal. Northwind uses Microsoft cloud services and has Azure resources that support some of its applications.
The company’s cloud environment includes:
- A Microsoft Entra tenant, where identities such as employee accounts and groups are managed.
- An Azure subscription associated with that tenant.
- Resource groups that organize Azure resources for different purposes.
- Resources used by the customer portal, as well as separate resources used for testing.
You will meet more details of this environment in later chapters. For now, picture the subscription as containing a production area and a test area. The production area supports the live customer portal. The test area gives the team a place to try changes without deliberately changing the live application.
Maya works on Northwind’s infrastructure team. Jordan is an application support technician. Jordan has been asked to investigate a reported issue with the customer portal, but the original request does not specify the tasks he needs to perform.
After a conversation with the application owner, Maya learns that Jordan’s immediate task is to inspect the portal’s Azure resource settings and report what he finds. He is not being asked to change those settings or read customer data. The application owner identifies the production resource group that contains the relevant portal resources.
The revised request is much more useful:
> Jordan needs to inspect the Azure settings of the customer portal resources in the production portal resource group so he can assist with an investigation.
This still requires verification. Maya must confirm the correct identity, resource group, and available role before making an assignment. But the request now describes a purpose, a set of intended actions, and a boundary. It is an access request she can evaluate rather than a vague invitation to grant broad privileges.
Before Azure can evaluate many access requests, it needs an identity to evaluate. Authentication is the process of establishing that an identity attempting to sign in has satisfied the applicable sign-in requirements.
For a person, that process might involve a password and an additional verification method. The exact experience depends on the organization’s configuration and policies. Microsoft Entra ID is the identity service used in the scenarios in this book; Northwind uses it to manage identities and support sign-in.
A successful sign-in answers a question like this:
> Is this sign-in recognized as Jordan’s account under the applicable requirements?
It does not answer the whole access question. Jordan may sign in successfully and still be unable to view the customer portal’s Azure resources. That can be the expected result if he has not been granted the necessary permissions.
The distinction is familiar outside the cloud. Showing an identification badge at a building entrance may establish who you are. It does not necessarily give you permission to enter the server room, open a personnel file, or change the heating controls. Each of those actions may have its own access rules.
In practice, sign-in can also be affected by conditions such as multifactor authentication or organizational policies. Those protections matter, but they are not substitutes for choosing the correct Azure permissions. Chapter 10 places sign-in protections in context after you have a firmer grasp of identities and roles.
Authorization is the process of determining whether an authenticated identity is permitted to perform a particular action in a particular context.
When Jordan attempts to view an Azure resource, the relevant question is not merely whether he has an account. It is whether his identity has access that permits the requested action at the resource in question. If he attempts a different action, such as changing a setting, the answer may be different.
This distinction helps explain two common situations:
- Jordan can sign in but cannot see the portal resource group. Authentication may have succeeded, while the required Azure authorization is absent or applies somewhere else. - Jordan can view a resource…