You are designing the security architecture for a suite of internally developed Azure microservices. One of the backend services, OrderProcessor, is registered as a Web API in Microsoft Entra ID. You must enforce a policy where other client microservices (which authenticate daemon-to-daemon using the client credentials flow) cannot acquire an access token for OrderProcessor unless they have been explicitly assigned permission by an administrator. If an unassigned client service attempts to request a token for OrderProcessor, Microsoft Entra ID must deny the token request at the token endpoint. Which configuration step must you perform to enforce this behavior?
- Set the appRoleAssignmentRequired property to true on the OrderProcessor service principal.Cevap
- BSet the appRoleAssignmentRequired property to true on the application registrations of each client microservice.
- CConfigure a Key Vault access policy on the Azure Key Vault instance containing the client microservice credentials.
- DConfigure the oauth2PermissionScopes in the application manifest of OrderProcessor to require administrator consent.
Cevap
Set the appRoleAssignmentRequired property to true on the OrderProcessor service principal.
The correct action is to set the appRoleAssignmentRequired property to true on the OrderProcessor service principal. In Microsoft Entra ID, the service principal represents the local instance of an application within a tenant. Setting this property to true restricts token issuance for that API/resource to only those users and service principals that have been explicitly assigned to one of the application's defined roles.
Adım Adım Çözüm
Anahtar Kavram
Enforcing application assignment requirements on service principals for daemon-to-daemon token acquisition.