Everyday Guidebooks
Cover of Azure for Beginners

Cybersecurity & IT

Azure for Beginners: Identity and Access Explained

A Practical Guide to Users, Roles, Scopes, and Permission Reviews for New Administrators

by Todd Michael

Available now

If you have searched for azure for beginners and found yourself lost among tenants, subscriptions, roles, and permissions, this guide offers a focused place to start.

Azure for Beginners: Identity and Access Explained follows the path from a person or application identity to the access it receives over Azure resources. Plain-English explanations and text-based walkthroughs show you how to choose a role, select an appropriate scope, make an assignment, and check what access remains afterward.

Using a consistent fictional organization, you will explore users, groups, administrative roles, inherited permissions, service identities, and common troubleshooting situations. You will also learn to recognize privilege mistakes, document decisions, and conduct a practical access review.

Written for new administrators and certification learners, this independent guide focuses on building durable understanding rather than promising an exam pass. Examples include safety notes, verification steps, and reminders to check current Microsoft documentation as interfaces and licensing requirements change.

Contents
  1. 1. The Access Question: Who Can Do What, and Where?
  2. 2. Tenants, Subscriptions, and Resources
  3. The Identity Home: A Microsoft Entra Tenant
  4. The Subscription: A Boundary for Azure Resources
  5. Resource Groups: Organizing Resources Inside a Subscription
  6. Resources: The Things People Need to Work With
  7. Put the Map Together
  8. A Request at the Correct Boundary
  9. Finding Your Place in the Azure Portal
  10. Common Boundary Mistakes
  11. From Map to Membership
  12. 3. People and Groups in Microsoft Entra ID
  13. 4. Administrative Roles Are Not All the Same
  14. 5. Azure RBAC: Principals, Roles, and Assignments
  15. 6. Scopes and Inherited Access
  16. 7. Choose the Right Access Before You Assign It
  17. 8. Walkthrough: Assign and Verify Azure Access
  18. The Practice Scenario
  19. Before You Open Access Control
  20. Find the Correct Resource Group
  21. Add the Reader Assignment
  22. Verify the Assignment Record
  23. Test the Intended Task
  24. Understand What the Assignment Does—and Does Not—Prove
  25. Remove the Practice Assignment
  26. 9. Applications and Managed Identities
  27. 10. Sign-In Protection and Access Conditions
  28. 11. Find Out Who Has Access
  29. 12. Troubleshoot Permission Problems
  30. 13. Avoid and Correct Privilege Mistakes
  31. 14. Run a Practical Access Review
  32. Set the Boundaries of the Review
  33. Gather Evidence Before Asking for Decisions
  34. Review Human Access Through Groups
  35. Review the Application Identity as an Identity
  36. Make Decisions Traceable
  37. Plan Changes Without Losing Evidence
  38. Verify the Outcome, Not Just the Click
  39. A Reusable Review Checklist
  40. Keep an Action Log

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…

More Cybersecurity & IT

Cover of The White Hat Bible, Volume 1The White Hat Bible, Volume 1Available nowCover of The White Hat Bible, Volume 2The White Hat Bible, Volume 2Available nowCover of The White Hat Bible, Volume 3The White Hat Bible, Volume 3Available nowCover of The White Hat Bible, Volume 4The White Hat Bible, Volume 4Available nowThe White Hat Bible, Volume 5Available nowCover of The White Hat Pocket GuideThe White Hat Pocket GuideAvailable now

About Todd Michael

Todd Michael is an American author and the founder of ToddMichael.tv. He writes practical, plain-English books on money, health, preparedness, technology, games, humor and more.

About the author Todd Michael · Todd Michael’s author site

Part of the ToddMichael.tv network.