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: docs/authentication/enterprise-connections/saml/azure.mdx
+8-6Lines changed: 8 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ description: Learn how to allow users to sign up and sign in to your Clerk app w
24
24
25
25
Enabling SAML with Microsoft Azure Entra ID (formerly [Active Directory](https://learn.microsoft.com/en-us/entra/fundamentals/new-name)) allows your users to sign up and sign in to your Clerk application with their Microsoft account.
26
26
27
-
This process requires configuration changes in both the Clerk dashboard, and in your customer's Microsoft Entra ID settings in their Azure account.
27
+
This process requires configuration changes in both the Clerk Dashboard, and in your customer's Microsoft Entra ID settings in their Azure account.
28
28
29
29
<Steps>
30
30
## Create a Microsoft Entra ID SAML connection in Clerk
@@ -110,7 +110,7 @@ This process requires configuration changes in both the Clerk dashboard, and in
110
110
111
111
1. Still on the **Set up Single Sign-On with SAML** page, find the **Attributes & Claims** section.
112
112
1. Select **Edit**.
113
-
1 Verify that the above three attributes and values are present.
113
+
1. Verify that the above three attributes and values are present.
114
114
115
115
**Step 5: Share the application's metadata URL**
116
116
@@ -121,9 +121,11 @@ This process requires configuration changes in both the Clerk dashboard, and in
121
121
122
122
## Add App Federation Metadata URL in the Dashboard
123
123
124
-
Now that you know the Microsoft app's **App Federation Metadata URL**, you can add it to the Clerk connection, completing the SAML connection configuration.
124
+
After following the instructions in the email, your customer should have sent you the Microsoft app's **App Federation Metadata URL**. Now, you're going to add it to the Clerk connection, completing the SAML connection configuration.
125
125
126
-
1. Navigate back to the **Clerk Dashboard**. In the **Identity Provider Configuration** section, under **App Federation Metadata Url**, paste the **App Federation Metadata URL**.
126
+
1. Navigate to the [**SSO connections**](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) page in the Clerk Dashboard.
127
+
1. Select the SAML connection.
128
+
1. In the **Identity Provider Configuration** section, under **App Federation Metadata Url**, paste the **App Federation Metadata URL**.
127
129
1. Select **Fetch & save**.
128
130
129
131
## Enable the connection in Clerk
@@ -135,7 +137,7 @@ This process requires configuration changes in both the Clerk dashboard, and in
135
137
136
138
To make the connection available for users of that IDP to authenticate with:
137
139
138
-
1. Navigate back to the Clerk Dashboard where you should still have the connection's configuration page open. If not, navigate to the SSO connections page and select the connection.
139
-
1. At the top of the page, toggle on Enable connection and select Save.
140
+
1. Navigate back to the Clerk Dashboard where you should still have the connection's configuration page open. If not, navigate to the [**SSO connections**](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) page and select the connection.
141
+
1. At the top of the page, toggle on **Enable connection** and select **Save**.
0 commit comments