Skip to content

Commit 3b860ae

Browse files
Update origin-authentication-with-managed-identities.md
1 parent 4a56033 commit 3b860ae

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -67,10 +67,10 @@ Managed identities are specific to the Microsoft Entra tenant where your Azure s
6767

6868
> [!Note]
6969
> The association will only work if
70-
> 1) the origin group does not contain any origins with private link enabled.
71-
> 2) the health probe protocol is set to 'HTTPS' under origin group settings.
72-
> 3) the forwarding protocol is set to 'HTTPS Only' under route settings.
73-
> 4) the forwarding protocol is set to 'HTTPS Only' in case you are using a 'Route configuration override' action in rulesets.
70+
> * the origin group does not contain any origins with private link enabled.
71+
> * the health probe protocol is set to 'HTTPS' under origin group settings.
72+
> * the forwarding protocol is set to 'HTTPS Only' under route settings.
73+
> * the forwarding protocol is set to 'HTTPS Only' in case you are using a 'Route configuration override' action in rulesets.
7474
7575
1. Navigate to your existing Azure Front Door profile and open origin groups.
7676
2. Select an existing origin group which has origins already configured.

0 commit comments

Comments
 (0)