Skip to content

Commit ee9ea2c

Browse files
authored
add preview note
1 parent 9d5f52d commit ee9ea2c

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/frontdoor/managed-identity.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,10 @@ ms.author: duau
1313

1414
Azure Front Door also supports using managed identities to access Key Vault certificate. A managed identity generated by Azure Active Directory (Azure AD) allows your Azure Front Door instance to easily and securely access other Azure AD-protected resources, such as Azure Key Vault. Azure manages this identity, 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?](../active-directory/managed-identities-azure-resources/overview.md).
1515

16+
> [!IMPORTANT]
17+
> Migration identity for Azure Front Door is currently in PREVIEW.
18+
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
19+
1620
> [!NOTE]
1721
> Once you enable managed identities in Azure Front Door and grant proper permissions to access Key Vault, Azure Front Door will always use managed identities to access Key Vault for customer certificate.
1822
>

0 commit comments

Comments
 (0)