Migration Assessment Scan: Custom Profile Property Mappings

Learn how to mitigate issues with Custom Profile Property mappings during migration.

Overview

In the source environment, it was possible to add additional profile property mappings to the User Profile Service Application via a standard change request (CR). The profile property mappings enable SharePoint to pull in profile property values from data sources outside of SharePoint. For example, you could map a profile property to an attribute in Active Directory. During a profile sync, SharePoint populated the user's profile with the value from Active Directory. Another scenario was to leverage Business Connectivity Services (BCS) to populate profile property values from a database or web service.

The target environment leverages Azure Active Directory (AAD) to populate the SharePoint profile values. SharePoint will synchronize the most common profile data from Azure Active Directory into SharePoint. The target environment does not support extending the AAD schema and configuring additional profile property mappings. If you need to populate data that is not provided by the out of the box profile property mappings, it is required to write a program that will push the values you want into the profile properties in the service.

For guidance on updating profile property values leveraging the Client Side Object Model (CSOM), see:

This scan output will provide you with a list of profile property mappings that will not be included in the target environment. This will enable you to make a decision on the direction moving forward.

Data Migration

The target environment will contain the default profile property mappings for SharePoint.

Important: Any site that is configured as “No Access” (locked), in SharePoint will be skipped. To see a list of locked site collections see the Locked Sites scan output.

Preparing for Migration

If the property mappings listed in the scan output are leveraged in a SharePoint add-in or company portal, we advise you to look into the sync application discussed in the following post to ensure that profile property data not included by default continues to be updated post migration.

Post Migration

If you built a profile property sync tool, ensure the tool functions post migration.

Scan Result Reports

The following table describes the columns in the CustomProfilePropertyMappings.csv report.

This scan report contains a list of all the profile property mappings that will not exist in the target environment. If you have multiple profile sync connections, you may see multiple mappings for a single profile property.

Note: Source environments will contain some properties that were previously used in a feature called Phonetic Search. This feature enabled you to search for a person’s name, and the search results would return names that were similar to the name entered. This functionality no longer relies on these properties in the target environment, and as a result, they will be present in your report. If you are not explicitly using the following properties in any of your customization, you will not need to take any action on these entries.

Property Display Name

Property Name

Mapping

Phonetic First Name

SPS-PhoneticFirstName

MsDS-PhoneticFirstName

Phonetic Display Name

SPS-PhoneticDisplayName

MsDS-PhoneticDisplayName

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×