Currently Conditional Access policies can be applied to all apps or to individual apps. Organizations with a large number of apps might find this process difficult to manage across multiple Conditional Access policies.
Application filters for Conditional Access allow organizations to tag service principals with custom attributes. These custom attributes are then added to their Conditional Access policies. Filters for applications are evaluated at token issuance runtime, a common question is if apps are assigned at runtime or configuration time.
In this document, you create a custom attribute set, assign a custom security attribute to your application, and create a Conditional Access policy to secure the application.
Assign roles
Custom security attributes are security sensitive and can only be managed by delegated users. One or more of the following roles should be assigned to the users who manage or report on these attributes.
Read the definition of custom security attributes.
Assign the appropriate role to the users who manage or report on these attributes at the directory scope. For detailed steps, see Assign Microsoft Entra roles.
Važno
By default, Global Administrator and other administrator roles do not have permissions to read, define, or assign custom security attributes.
Create an Attribute set named ConditionalAccessTest.
Create New attributes named policyRequirement that Allow multiple values to be assigned and Only allow predefined values to be assigned. We add the following predefined values:
legacyAuthAllowed
blockGuestUsers
requireMFA
requireCompliantDevice
requireHybridJoinedDevice
requireCompliantApp
Bilješka
Conditional Access filters for applications only works with custom security attributes of type "string". Custom Security Attributes support creation of Boolean data type but Conditional Access Policy only supports "string".
Conditional Access gives a fine granularity of control over which users can do specific activities, access which resources, and how to ensure data and systems are safe.