Use managed identities to access Azure Key Vault certificates
A managed identity generated by Microsoft Entra ID allows your Azure Front Door instance to easily and securely access other Microsoft Entra protected resources, such as Azure Key Vault. Azure manages the identity resource, so you don't have to create or rotate any secrets. For more information about managed identities, see What are managed identities for Azure resources?.
Once you enable managed identity for Azure Front Door and grant proper permissions to access your Azure Key Vault, Front Door only uses managed identity to access the certificates. If you don't add the managed identity permission to your Key Vault, custom certificate autorotation and adding new certificates fails without permissions to Key Vault. If you disable managed identity, Azure Front Door falls back to using the original configured Microsoft Entra App. This solution isn't recommended and will be retired in the future.
You can grant two types of identities to an Azure Front Door profile:
A system-assigned identity is tied to your service and is deleted if your service is deleted. The service can have only one system-assigned identity.
A user-assigned identity is a standalone Azure resource that can be assigned to your service. The service can have multiple user-assigned identities.
Managed identities are specific to the Microsoft Entra tenant where your Azure subscription is hosted. They don't get updated if a subscription gets moved to a different directory. If a subscription gets moved, you need to recreate and reconfigure the identity.
Prerequisites
Before you can set up managed identity for Azure Front Door, you must have an Azure Front Door Standard or Premium profile created. To create a new Front Door profile, see create an Azure Front Door.
Enable managed identity
Go to an existing Azure Front Door profile. Select Identity from under Security on the left side menu pane.
Select either a System assigned or a User assigned managed identity.
System assigned - a managed identity is created for the Azure Front Door profile lifecycle and is used to access Azure Key Vault.
User assigned - a standalone managed identity resource is used to authenticate to Azure Key Vault and has its own lifecycle.
Toggle the Status to On and then select Save.
You're prompted with a message to confirm that you would like to create a system managed identity for your Front Door profile. Select Yes to confirm.
Once the system assigned managed identity has been created and registered with Microsoft Entra ID, you can use the Object (principal) ID to grant Azure Front Door access to your Azure Key Vault.
Configure Key Vault access policy
Navigate to your Azure Key Vault. Select Access policies from under Settings and then select + Create.
On the Permissions tab of the Create an access policy page, select List and Get under Secret permissions. Then select Next to configure the principal tab.
On the Principal tab, paste the object (principal) ID if you're using a system managed identity or enter a name if you're using a user assigned manged identity. Then select Review + create tab. The Application tab is skipped since Azure Front Door gets selected for you already.
Review the access policy settings and then select Create to set up the access policy.
Verify access
Go to the Azure Front Door profile you enabled managed identity and select Secrets from under Security.
Confirm Managed identity appears under the Access role column for the certificate used in Front Door.
Next steps
- Learn more about End-to-end TLS encryption.
- Learn how to configure HTTPS on an Azure Front Door custom domain.
Feedback
Submit and view feedback for