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: src/content/docs/cloudflare-one/identity/idp-integration/entra-id.mdx
+55-36Lines changed: 55 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,6 +108,24 @@ More narrow permissions may be used, however this is the set of permissions that
108
108
109
109
To [test](/cloudflare-one/identity/idp-integration/#test-idps-in-zero-trust) that your connection is working, select **Test**.
110
110
111
+
#### UPN and email
112
+
113
+
If your organization's UPNs do not match users' email addresses, you must add a custom claim for email. For example, if your organization's email format is `[email protected]` but the UPN is `[email protected]`, you must create an email claim if you are configuring email-based policies.
114
+
115
+
By default, Cloudflare will look for an `email` claim in the JSON response. If an `email` claim does not exist, it will look for the unique claim name you created to represent email (for example, `email_identifier`). Last, if neither option exists, Cloudflare will then look for the UPN claim sent in the JSON response.
116
+
117
+
To receive an email claim in a JSON response from Microsoft Entra, you must:
118
+
119
+
1. In the [Microsoft Entra admin center](https://entra.microsoft.com/), go to **Application** > **App registration** > select the relevant application > **Manage** > **Token configuration**.
120
+
2. Add a claim for email.
121
+
122
+

123
+
124
+
The example above includes both a UPN claim and an email claim. Because an email claim was created in the Microsoft Entra configuration, Cloudflare will look for the `email` key-value pair in the JSON response.
125
+
126
+
3. If you gave your email claim another name than `email`, in [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Authentication** > **Azure AD** > **Edit**.
127
+
4. Under **Optional configurations** > **Email claim**, enter the name of the claim representing your organization's email addresses.
128
+
111
129
## Synchronize users and groups
112
130
113
131
The Microsoft Entra ID integration allows you to synchronize IdP groups and automatically deprovision users using [SCIM](/cloudflare-one/identity/users/scim/).
@@ -120,7 +138,7 @@ The Microsoft Entra ID integration allows you to synchronize IdP groups and auto
@@ -139,9 +157,9 @@ SCIM requires a separate enterprise application from the one created during [ini
139
157
140
158
5. Once the SCIM application is created, [assign users and groups to the application](https://learn.microsoft.com/entra/identity/enterprise-apps/assign-user-or-group-access-portal).
141
159
142
-
:::note
143
-
Groups in this SCIM application should match the groups in your other [Cloudflare Access enterprise application](/cloudflare-one/identity/idp-integration/entra-id/#set-up-entra-id-as-an-identity-provider). Because SCIM group membership updates will overwrite any groups in a user's identity, assigning the same groups to each app ensures consistent policy evaluation.
144
-
:::
160
+
:::note
161
+
Groups in this SCIM application should match the groups in your other [Cloudflare Access enterprise application](/cloudflare-one/identity/idp-integration/entra-id/#set-up-entra-id-as-an-identity-provider). Because SCIM group membership updates will overwrite any groups in a user's identity, assigning the same groups to each app ensures consistent policy evaluation.
162
+
:::
145
163
146
164
6. Go to **Provisioning** and select **Get started**.
147
165
@@ -159,7 +177,7 @@ SCIM requires a separate enterprise application from the one created during [ini
159
177
160
178
To check which users and groups were synchronized, select **View provisioning logs**.
161
179
162
-
<Renderfile="access/verify-scim-provisioning"/>
180
+
<Renderfile="access/verify-scim-provisioning"/>
163
181
164
182
### Provisioning attributes
165
183
@@ -207,38 +225,39 @@ Access and Gateway policies for an Entra group will also apply to all [nested gr
207
225
## Force user interaction during WARP reauthentication
208
226
209
227
You can require users to re-enter their credentials into Entra ID whenever they [re-authenticate their WARP session](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-sessions/). To configure this setting:
228
+
210
229
1. Make a `GET` request to the [Identity Providers endpoint](/api/resources/zero_trust/subresources/identity_providers/) and copy the response for the Entra ID identity provider.
211
230
2.[Update the Entra ID identity provider](/api/resources/zero_trust/subresources/identity_providers/methods/update/) using a `PUT` request. In the request body, include all existing configurations and set the `prompt` parameter to either `login` or `select_account`. For example,
0 commit comments