Skip to content

Commit 4d338fd

Browse files
Merge pull request #232629 from kenwith/patch-63
Adds updates for acrolinx - clarity.
2 parents 4f5cd0d + a7f6eea commit 4d338fd

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/active-directory/app-provisioning/customize-application-attributes.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.workload: identity
1010
ms.topic: tutorial
11-
ms.date: 03/28/2023
11+
ms.date: 03/29/2023
1212
ms.author: kenwith
1313
ms.reviewer: arvinh
1414
---
@@ -206,7 +206,7 @@ Use the steps in the example to provision roles for a user to your application.
206206

207207
![Add SingleAppRoleAssignment](./media/customize-application-attributes/edit-attribute-singleapproleassignment.png)
208208
- **Things to consider**
209-
- 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.
210210
- SingleAppRoleAssignments isn't compatible with setting scope to "Sync All users and groups."
211211
- **Example request (POST)**
212212

@@ -321,9 +321,9 @@ Certain attributes such as phoneNumbers and emails are multi-value attributes wh
321321

322322
## Restoring the default attributes and attribute-mappings
323323

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.
325325

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.
327327

328328
> [!IMPORTANT]
329329
> 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
334334
- 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.
335335
- A recommended best practice is to keep the number of consecutive changes to your attribute-mappings at a minimum.
336336
- 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.
338338
- The Azure AD provisioning service doesn't support provisioning null values.
339339
- They primary key, typically "ID", shouldn't be included as a target attribute in your attribute mappings.
340340
- 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

Comments
 (0)