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
- Ensure that multiple roles aren't assigned to a user. There is no guarantee which role is provisioned.
209
+
- Ensure that multiple roles aren't assigned to a user. There's no guarantee which role is provisioned.
210
210
- SingleAppRoleAssignments isn't compatible with setting scope to "Sync All users and groups."
211
211
-**Example request (POST)**
212
212
@@ -321,9 +321,9 @@ Certain attributes such as phoneNumbers and emails are multi-value attributes wh
321
321
322
322
## Restoring the default attributes and attribute-mappings
323
323
324
-
Should you need to start over and reset your existing mappings back to their default state, you can select the **Restore default mappings** check box and save the configuration. Doing so sets all mappings and scoping filters as if the application was just added to your Azure AD tenant from the application gallery.
324
+
Should you need to start over and reset your existing mappings back to their default state, you can select the **Restore default mappings** check box and save the configuration. Doing so sets all mappings and scoping filters as if the application was added to your Azure AD tenant from the application gallery.
325
325
326
-
Selecting this option will effectively force a resynchronization of all users while the provisioning service is running.
326
+
Selecting this option forces a resynchronization of all users while the provisioning service is running.
327
327
328
328
> [!IMPORTANT]
329
329
> We strongly recommend that **Provisioning status** be set to **Off** before invoking this option.
@@ -334,7 +334,7 @@ Selecting this option will effectively force a resynchronization of all users wh
334
334
- Updating attribute-mappings has an impact on the performance of a synchronization cycle. An update to the attribute-mapping configuration requires all managed objects to be reevaluated.
335
335
- A recommended best practice is to keep the number of consecutive changes to your attribute-mappings at a minimum.
336
336
- Adding a photo attribute to be provisioned to an app isn't supported today as you can't specify the format to sync the photo. You can request the feature on [User Voice](https://feedback.azure.com/d365community/forum/22920db1-ad25-ec11-b6e6-000d3a4f0789)
337
-
- The attribute IsSoftDeleted is often part of the default mappings for an application. IsSoftdeleted can be true in one of four scenarios (the user is out of scope due to being unassigned from the application, the user is out of scope due to not meeting a scoping filter, the user has been soft deleted in Azure AD, or the property AccountEnabled is set to false on the user). It's not recommended to remove the IsSoftDeleted attribute from your attribute mappings.
337
+
- The attribute `IsSoftDeleted` is often part of the default mappings for an application. `IsSoftdeleted` can be true in one of four scenarios: 1) The user is out of scope due to being unassigned from the application. 2) The user is out of scope due to not meeting a scoping filter. 3) The user has been soft deleted in Azure AD. 4) The property `AccountEnabled` is set to false on the user. It's not recommended to remove the `IsSoftDeleted` attribute from your attribute mappings.
338
338
- The Azure AD provisioning service doesn't support provisioning null values.
339
339
- They primary key, typically "ID", shouldn't be included as a target attribute in your attribute mappings.
340
340
- The role attribute typically needs to be mapped using an expression, rather than a direct mapping. For more information about role mapping, see [Provisioning a role to a SCIM app](#Provisioning a role to a SCIM app).
0 commit comments