A system-assigned managed identity provides App1 with an automatically created and managed identity in Microsoft Entra ID. Behind the scenes, Azure issues and automatically rotates an X.509 certificate as the credential for this identity, so no keys, tokens, or secrets need to be manually created, stored, or rotated by an administrator. After enabling the managed identity, you simply assign App1's identity an appropriate RBAC role (such as Cognitive Services User) on CSAccount1, and the app authenticates using Microsoft Entra ID tokens obtained transparently through this managed credential. This keyless approach requires the least ongoing administrative effort compared to manually managing a subscription key, OAuth token, or SAS token.
Community Discussion