What is RBAC? Role-based access control meaning and examples
Microsoft's admin thresholds and how roles work in Teams, Exchange, SharePoint and Active Directory, plus NIST's least privilege definition, zero trust, scoping in Azure, AWS and Azure Virtual Desktop, what to check in a tool's RBAC and a seven-step setup for MSPs and IT teams.
Updated: November 2026
Somebody on your team has more admin rights than their job needs. They probably got them on day one because it was quicker than working out what they needed. Role-based access control (RBAC) is how MSPs and in-house IT teams fix that without reviewing every account by hand, and this guide explains the RBAC meaning with examples from the tools your techs log into every day.
TL;DR
- RBAC meaning. Role-based access control gives permissions to roles and roles to people, so a job change is one role swap.
- Least privilege. The goal RBAC serves, and a NIST control (SP 800-53 AC-6): access limited to what assigned tasks need.
- Microsoft's targets. Fewer than five Global Administrators, fewer than ten privileged role assignments and two break-glass accounts.
- Microsoft 365. Entra roles cover Teams, Exchange and SharePoint admin work, and Exchange Online adds its own role groups.
- Zero trust. NIST SP 800-207 builds least privilege into zero trust, so roles set the ceiling and each request is still checked.
- For MSPs. GDAP gives partners specific roles in each client tenant for a set period instead of Global Admin.
- For IT teams. Export who holds what, assign roles to groups and make privileged roles eligible through PIM.
What is RBAC?
RBAC, or role-based access control, is a way of granting access where permissions belong to roles and people get roles. A helpdesk tech gets the "password reset" role, not a list of 40 separate rights. When someone changes jobs, you swap their role and every permission follows.
That's the whole idea. You manage a short list of roles instead of a long list of people.
The model rests on three rules, the ones security exams like to ask about:
- Role assignment. A person can only use a permission if they hold a role.
- Role authorization. The role a person uses has to be one they've been approved for.
- Permission authorization. A person can only use permissions their active role allows.
In plain terms: no role, no access. And the role decides the access, not the person asking for it.
RBAC in the tools you already run
On paper the model is users, roles and permissions. In practice you meet RBAC in three places every week.
Microsoft Entra ID. Entra ships over 65 built-in roles, per Microsoft's own guidance, updated June 2026. There are roles for users and groups, and roles for Exchange, SharePoint and Intune. If none fits, you can build a custom role, and administrative units let you scope a role to one region or department. A regional helpdesk admin can reset passwords for their office and nobody else's.
Microsoft 365 admin roles. These are the same Entra roles, shown in the Microsoft 365 admin center. The trap is Global Administrator. It's the default for whoever set up the tenant, and it can change almost everything.
Your RMM and help desk. Technician roles decide who can run scripts, open remote sessions, see which clients and approve patches. A tier-1 tech who only needs remote control shouldn't be able to push a script to every endpoint.
For MSPs there's a fourth place: partner access to client tenants. Microsoft replaced the old delegated admin model, which handed partners Global Admin, with granular delegated admin privileges (GDAP). Partners now request specific roles for a set period. In this r/msp thread, a customer lists 13 admin roles their licensing supplier holds and asks which ones they need. The replies point to Microsoft's list of least-privileged roles by task.
RBAC in Microsoft Teams, Exchange and SharePoint
Each Microsoft 365 workload has its own admin roles, so workload jobs rarely need a tenant-wide role. Teams has seven, from Teams Administrator down to the read-only Teams Reader. A help desk that troubleshoots call quality can work as Teams Communications Support Engineer instead of full Teams Administrator.
Exchange Online runs its own RBAC underneath the Entra roles. Role groups such as Organization Management, Recipient Management and Help Desk set what admins can do, and role assignment policies set what users can change in their own mailbox. RBAC for Applications, part of Exchange Online permissions, limits an app to the mailboxes it needs instead of the whole tenant.
In SharePoint, the SharePoint Administrator role creates and manages sites, designates site admins and controls sharing for the tenant. Site admins manage a single site without any Microsoft 365 admin role. For audits, Global Reader is the read-only counterpart to Global Administrator, so a reviewer can see settings without changing them.
RBAC in Active Directory
On-premises Active Directory handles roles through groups. Microsoft's least-privilege administration guidance describes RBAC for AD DS as creating roles, delegating rights and permissions to them, and letting each role's members do their day-to-day admin work. For DNS, that can be as simple as adding each DNS administrator to the DNS Admins group.
The same guidance says membership in Enterprise Admins and Domain Admins should be needed only for build or disaster-recovery work: accounts go in temporarily when that access is required, and no day-to-day user accounts stay in either group. If you run both directories, our guide to Entra vs Active Directory covers where each one fits.
What to check in a tool's role-based access
Before you buy an RMM, PSA, password manager or workflow tool, check how its roles work, not only that they exist.
| Check | What to look for |
|---|---|
| Built-in and custom roles | Ready-made roles for common jobs, plus custom roles when none fit |
| Scope | Roles limited to a client, site, device group or department |
| Edition | Roles included in the self-hosted or base edition, not only a higher cloud plan |
| Identity sync | Roles mapped to groups in Entra ID or another identity provider |
| Audit trail | A log of role changes and admin actions you can export as evidence |
| Reviews | A way to list who holds which role, on a schedule |
For compliance tracking, the audit trail and review rows carry the weight, because an auditor asks for evidence of who held access and when someone checked it. Our guide to compliance automation software covers tools that collect that evidence.
Password managers apply the same idea to shared credentials: vault roles decide which technicians can see, edit or share each client's passwords. Our roundup of multi-tenant password managers compares the options built for MSPs.
Least privilege is the point
RBAC is the mechanism. Least privilege is the goal: each person gets exactly the access their job needs, over the narrowest scope, for the shortest time.
NIST's glossary defines the principle the same way: a system should restrict the access privileges of users, and of processes acting for them, to the minimum needed for their assigned tasks. NIST SP 800-53 also lists it as a formal security control, AC-6 Least Privilege.
Microsoft puts numbers on it. Its Entra best-practice guidance recommends fewer than five Global Administrators, fewer than ten privileged role assignments, and two cloud-only emergency access accounts kept for break-glass situations. Entra shows a warning card once you pass those thresholds, which makes it a quick check in any tenant.
The reason is simple. A compromised account can only do what its role allows. The Verizon 2026 DBIR found credential abuse was the first step in 13% of breaches, second only to exploited vulnerabilities at 31%. When the account an attacker lands on is a password-reset role, that's a bad day. When it's a Global Admin, it's the whole tenant.
Standing access is the other half. Privileged Identity Management (PIM) makes someone eligible for a role instead of holding it permanently. They activate it when needed, for a set time, and it drops off by itself.
This r/sysadmin thread is a good reminder of how often the opposite happens. A new hire gets full domain admin in their first week. One of the top replies asks whether anyone else is unsurprised he got domain admin right away, because it happens that often.
For the admin accounts themselves, our guide to privileged access management covers vaulting, session recording and the tools that do it.
The principle of least privilege: an example
Take a tier-1 tech who resets passwords for one office. The quick setup is User Administrator, which manages all aspects of users and groups. The least-privilege setup is Password Administrator, which resets passwords for non-administrators and other Password Administrators, scoped to that office through an administrative unit.
Time is the third limit: make the role eligible through PIM so it's active only while the tech works the ticket. Administrative units need a Microsoft Entra ID P1 license for each admin assigned a role over one. For an MSP, the role comes through GDAP and covers that one client's tenant, not every client you manage.
Zero trust vs least privilege
Least privilege decides how much access an identity gets. Zero trust decides whether each request gets through, checking identity, device and context every time instead of trusting the network. NIST SP 800-207 builds one into the other: access is granted per session, with the least privileges needed to complete the task.
In practice the two work as layers. RBAC and PIM set the ceiling for what an account can do, and Conditional Access decides whether a given sign-in, from a given device, gets to use it. A zero trust rollout without least privilege still leaves a verified account with too much reach.
Least privilege in IAM and the cloud
Least privilege covers every identity, not only people: service accounts, app registrations and AI agents need the same limits. Azure assigns roles at four scopes (management group, subscription, resource group and resource), and Microsoft's scope guidance explains why narrow wins: a smaller scope limits what's at risk if the identity is compromised.
Permissions also add up. Microsoft describes Azure RBAC as an additive model, where effective permissions are the sum of every role assignment, so a Reader role on one resource group doesn't cancel Contributor on the subscription above it.
AWS takes the same path. Its IAM best practices start with AWS managed policies, move toward least-privilege permissions, and use IAM Access Analyzer to generate least-privilege policies based on access activity.
For tools that manage identities across apps and clients, see our guide to IAM solutions.
Least privilege for Azure Virtual Desktop
Azure Virtual Desktop splits its work into built-in roles, so the help desk doesn't need Contributor. Users get Desktop Virtualization User on the application group they connect to. Help desk staff get Desktop Virtualization User Session Operator, which sends messages, disconnects sessions and signs users out. Host operators get Desktop Virtualization Session Host Operator to view and remove session hosts and change drain mode.
Desktop Virtualization Contributor manages everything except user and group assignment, which also needs User Access Administrator. On Microsoft Entra joined session hosts in host pools without a session host configuration, users also need Virtual Machine User Login, and admins who need local admin rights get Virtual Machine Administrator Login, assigned to groups rather than individuals. Microsoft's AVD role list covers the rest.
RBAC vs ABAC, and when roles stop scaling
RBAC has one well-known failure: role explosion. Every exception becomes a new role. "Helpdesk, but can also manage the Paris printers" turns into its own role, then another, until nobody knows what half the roles do.
Attribute-based access control (ABAC) answers a different question. Instead of "what's your role", it asks "what's true right now": your department, your device, your location, the data's sensitivity. It's more flexible and harder to audit.
You rarely have to pick one. Entra already layers them: roles decide what an admin can do, and Conditional Access checks device and location before the role works. Start with roles. Add attributes where the exceptions pile up.
How to set up RBAC for an IT team
You don't need a project plan. You need an afternoon and the admin portals.
- List who holds what. Export every admin role assignment in Entra and your RMM. Everything else builds on this list.
- Define roles by job, not by person. Tier-1, tier-2, security, billing. If a role has one member, it's probably a person, not a job.
- Assign roles to groups. Add people to a group and give the group the role, so onboarding and offboarding are one change.
- Split daily and admin accounts. Email and browsing on one account, admin work on another.
- Make privileged roles eligible, not permanent. Use PIM, or your tool's equivalent, for anything that can change security settings.
- Review quarterly. Microsoft recommends recurring access reviews, because people move teams and quietly collect access.
- Keep two break-glass accounts. Cloud-only, excluded from normal sign-in rules, tested and locked away.
On endpoints, the same thinking applies to local admin rights. Our endpoint privilege management guide covers removing local admin without flooding the help desk.
This short explainer from Mike Chapple covers the model, and it's a good one to send a non-technical colleague.
Give AI agents a role too
The newest accounts in your environment aren't people. AI agents that restart services, run scripts or reset passwords need a role like any tech, and the same rules apply: the narrowest scope that does the job, and a human approval for anything risky.
Ask two questions of any agent before it touches production. What can it change on its own? And where is the record of what it did? OpenFrame, which Flamingo builds, is open, AI-native infrastructure for IT and security with agents working inline: Fae resolves support requests, Mingo runs IT operations, and risky actions wait at an approval block for a technician. Our IT automation guide covers the full set of guardrails.
Start with the export
RBAC comes down to one habit: give access to roles, give roles to people, and check the list on a schedule. Microsoft's own thresholds are a good first target: fewer than five Global Admins, fewer than ten privileged assignments.
Pull the role export this week and count. For the next layer, read how RMM security protects the tool that can touch every endpoint you manage.

Content Marketing Lead
Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.
Related Content
Frequently Asked Questions
/blog/what-is-rbac
Still deciding?
Ask Mingo answers from our docs and customer stories.