You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/frontdoor/origin-authentication-with-managed-identities.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,3 +121,4 @@ Managed identities are specific to the Microsoft Entra tenant where your Azure s
121
121
* It is recommended that you use different managed identities for origin authentication and for AFD to Azure Key Vault authentication.
122
122
* For best practices while using managed identities, refer to [Managed identity best practice recommendations](/entra/identity/managed-identities-azure-resources/managed-identity-best-practice-recommendations).
123
123
* For best practices while assigning RBAC role for Azure storage account, refer to [Assign an Azure role for access to blob data](../storage/blobs/assign-azure-role-data-access.md)
124
+
* When origin authentication is enabled on an origin group, Front Door includes the access token in the Authorization header for health probes probing the origins within the origin group, not just for end-user traffic requests.
0 commit comments