Skip to content

Commit c6fb9fa

Browse files
authored
Updates spacing.
1 parent d830ab8 commit c6fb9fa

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,8 +58,7 @@ There are four different mapping types supported:
5858

5959
- **Direct** – the target attribute is populated with the value of an attribute of the linked object in Azure AD.
6060
- **Constant** – the target attribute is populated with a specific string you specified.
61-
- **Expression** - the target attribute is populated based on the result of a script-like expression.
62-
To learn more about expressions, see [Writing Expressions for Attribute-Mappings in Azure Active Directory](../app-provisioning/functions-for-customizing-application-data.md).
61+
- **Expression** - the target attribute is populated based on the result of a script-like expression. To learn more about expressions, see [Writing Expressions for Attribute-Mappings in Azure Active Directory](../app-provisioning/functions-for-customizing-application-data.md).
6362
- **None** - the target attribute is left unmodified. However, if the target attribute is ever empty, it's populated with the Default value that you specify.
6463

6564
Along with these four basic types, custom attribute-mappings support the concept of an optional **default** value assignment. The default value assignment ensures that a target attribute is populated with a value if there's not a value in Azure AD or on the target object. The most common configuration is to leave this blank.

0 commit comments

Comments
 (0)