Skip to content

Commit 21725cf

Browse files
Merge pull request #300256 from Harikrishnan-M-B/patch-44
Remove KV references
2 parents b61631e + ca390e0 commit 21725cf

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/frontdoor/origin-authentication-with-managed-identities.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ Managed identities are specific to the Microsoft Entra tenant where your Azure s
3939

4040
1. Choose either a **System assigned** or **User assigned** managed identity.
4141

42-
- **[System assigned](#system-assigned)** - A managed identity tied to the Azure Front Door profile lifecycle, used to access Azure Key Vault.
42+
- **[System assigned](#system-assigned)** - A managed identity tied to the Azure Front Door profile lifecycle.
4343

44-
- **[User assigned](#user-assigned)** - A standalone managed identity resource with its own lifecycle, used to authenticate to Azure Key Vault.
44+
- **[User assigned](#user-assigned)** - A standalone managed identity resource with its own lifecycle.
4545

4646
### System assigned
4747

@@ -51,7 +51,7 @@ Managed identities are specific to the Microsoft Entra tenant where your Azure s
5151

5252
1. Confirm the creation of a system managed identity for your Front Door profile by selecting **Yes** when prompted.
5353

54-
1. Once created and registered with Microsoft Entra ID, use the **Object (principal) ID** to grant Azure Front Door access to your Azure Key Vault.
54+
1. Once created and registered with Microsoft Entra ID, use the **Object (principal) ID** to grant Azure Front Door access to your origin.
5555

5656
:::image type="content" source="./media/managed-identity/system-assigned-created.png" alt-text="Screenshot of the system assigned managed identity registered with Microsoft Entra ID.":::
5757

0 commit comments

Comments
 (0)