An access control model that grants or denies access by evaluating attributes of the user, the resource and the environment, such as role, device health and location, against policies at request time.
Title graphic: Attribute-based access control (ABAC) (Concept)
Attribute-based access control (ABAC) is an access control model that grants or denies access by evaluating attributes of the user, the resource and the environment against policies at the time of a request. Typical attributes include a user's role, the health of a device and the location of a request. Because the decision is made when the request arrives, the outcome can change as conditions change, without the need to rewrite permission assignments. In the M365.FM knowledge base the concept sits under the broader topic of identity and security tools.
The purpose of ABAC is finer-grained and more flexible authorization than a model based only on fixed roles. A policy compares attribute values and returns an allow or deny result. Attributes can describe the security principal, such as a department or a role, the resource, such as a tag or classification on a file, and the environment, such as device state, network path or location. Combining these three groups lets an organization express rules that follow business context rather than only group membership.
Microsoft Learn describes this approach in the form of Azure attribute-based access control (Azure ABAC). Azure ABAC builds on Azure role-based access control (RBAC) by adding role assignment conditions to existing role assignments. A condition is an optional additional check, written as an expression made of an attribute, an operator and a value, which evaluates to true or false. Attributes are key-value pairs, for example a project tag. They can come from blob storage properties, from the request environment, or from custom security attributes on the principal. Typical examples in the documentation allow reading only blobs that carry a certain tag, or allow writing only through a private link.
The documentation lists three benefits: more fine-grained access control, fewer role assignments, which matters because subscriptions have an assignment limit, and the ability to use business-related attributes. It also names limits. Conditions currently apply only to roles with Blob Storage or Queue Storage data actions, creating them requires permission to write role assignments, and they cannot be used to explicitly deny access. The visual editor supports a limited number of expressions per condition, while the code editor allows more.
ABAC is usually discussed alongside Role-Based Access Control (RBAC) and, in some designs, Relationship-Based Access Control (ReBAC). RBAC fits stable teams with predictable permissions, while ABAC adds further checks for dynamic environments. The episode "How to Govern Microsoft Copilot in the Enterprise" says that many enterprises now use hybrid models combining both, so that critical data stays protected and permissions can be adjusted as risks change. In that episode ABAC is part of a wider governance approach that also includes verifying each access request with strong authentication, granting only the permissions needed for a task, and designing systems as if a breach could happen at any time. The same episode addresses legacy "open by default" setups, where users can reach more data than they need.
The episode "How to Build Private RAG with SharePoint and n8n" applies the concept to retrieval-augmented generation. It recommends using authorization controls to decide which documents each user can access, supported by document classification, user-document mapping and metadata tagging. It names RBAC, ABAC and ReBAC as standard authorization models and describes pre-query and post-query filtering at query time so that users only see documents they are allowed to access. Permission filters are enforced through the API, and embeddings are stored securely. According to the episode, these steps help prevent risks such as Denial of Wallet (DoW) and Denial of Service (DoS).
In practice, the decision around ABAC is often whether roles alone are sufficient or whether context such as resource tags, device health or location should influence access. Metadata quality matters, since a policy can only evaluate attributes that are accurately assigned to users and resources.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
This episode argues that sensitivity labels are widely misunderstood and often give organizations a false sense of security. While they appear to enforce governance, in reality they are static, incomplete, and poorly maintained—making them ineffective in…
Articles about Attribute-based access control (ABAC) (2)
Articles in which Attribute-based access control (ABAC) is a topic:
Microsoft Entra Groups Guide · Mirko Peters Learn Microsoft Entra groups with practical guidance on security, governance, access control, implementation, and real-world use.
PIM Vs RBAC Guide · Mirko Peters Learn PIM vs RBAC with practical guidance on architecture, security, governance, implementation, and real-world use.
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What is attribute-based access control (ABAC)? (AI)
ABAC is an access control model that grants or denies access by evaluating attributes of the user, the resource and the environment, such as role, device health and location, against policies when a request is made.
How does Azure ABAC relate to Azure RBAC? (AI)
According to Microsoft Learn, Azure ABAC builds on Azure role-based access control by adding role assignment conditions to existing role assignments. A condition is an expression of attribute, operator and value that evaluates to true or false.
Why does ABAC come up in the Copilot and private RAG episodes? (AI)
The episodes present ABAC as one of several authorization models, alongside RBAC and ReBAC, used to control which documents or data a user can reach. They describe hybrid RBAC and ABAC approaches for Copilot governance and query-time filtering for private RAG.
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.