Azure App Configuration Managed Identity. With a managed identity, your code can use the service principal created for the azure service it runs on. By using access policies on the azure key vault, we can grant access to the azure function app, and if it's using managed identity it can do this without credentials anywhere in configuration.
The pre v3 api connectwithmanagedidentity() worked locally in the past is because it falls back to local credentials automatically when it detects managed. The managed identities for azure resources feature in azure active directory (azure ad) solves this problem. App developers can use optional claims to specify which claims they want in the tokens sent to their application, which is useful when migrating apps to the microsoft identity platform (e.g.
These managed identities are created by the user and can span multiple services.
Use managed identities to access app configuration. But if you notice when we use the azure.identity library and managedidentitycredential to access these resources, when you try to run the application locally do debug, the application won’t run and throw an exception when trying to access azure app configuration and azure key vault. The azure functions can use the system assigned identity to access the key vault. Identity identity manage user identities and access to protect against advanced threats across.
