Skip to content

Commit d830ab8

Browse files
authored
Updates for consistency.
1 parent af4590a commit d830ab8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ There are four different mapping types supported:
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.
6161
- **Expression** - the target attribute is populated based on the result of a script-like expression.
62-
For more information about expressions, see [Writing Expressions for Attribute-Mappings in Azure Active Directory](../app-provisioning/functions-for-customizing-application-data.md).
62+
To learn more about expressions, see [Writing Expressions for Attribute-Mappings in Azure Active Directory](../app-provisioning/functions-for-customizing-application-data.md).
6363
- **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.
6464

6565
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)