Using RBAC and ABAC description

Author: rolyon

articles/role-based-access-control/conditions-overview.md

@@ -6,7 +6,7 @@ manager: femila
 ms.service: role-based-access-control
 ms.subservice: conditions
 ms.topic: overview
-ms.date: 04/01/2024
+ms.date: 05/19/2025
 ms.author: rolyon
 #Customer intent: As a dev, devops, or it admin, I want to learn how to constrain access within a role assignment by using conditions.
 ---
@@ -21,6 +21,8 @@ Attribute-based access control (ABAC) is an authorization system that defines ac
 
 Azure ABAC builds on Azure RBAC by adding role assignment conditions based on attributes in the context of specific actions. A *role assignment condition* is an additional check that you can optionally add to your role assignment to provide more fine-grained access control. A condition filters down permissions granted as a part of the role definition and role assignment. For example, you can add a condition that requires an object to have a specific tag to read the object. You cannot explicitly deny access to specific resources using conditions.
 
+Using Azure RBAC and Azure ABAC together integrates the benefits of both access control models. Azure RBAC is more straightforward to implement due to its close alignment with business logic, while Azure ABAC provides greater flexibility in some key scenarios. By combining these two methods, organizations can achieve a more sophisticated level of authorization.
+
 ## Why use conditions?
 
 There are three primary benefits for using role assignment conditions: