Contents
Can a custom user profile be imported into Active Directory?
The import only works for user profile properties that have not been set to be editable by end users. This is to prevent the user profile import process from overriding any information that an end user has already updated. Additionally, the import only allows custom properties that are not Active Directory core properties.
What to do if a user profile is not imported?
Option 1: Turn them into “managed” profiles so profile import / sync can update and maintain them. If you intended these user profiles to be imported, but they weren’t (and therefore were created as “stub” profiles) then you need to start by determining why they were not imported.
Are there any non-imported user profiles in SharePoint?
They were not created by Profile Sync / AD Import / Sync with External Identity Manager. We also refer to these as “unmanaged”, or “stub” profiles because they typically only contain the minimum amount of user data — usually just the users account name. Note: in this article, I will use the terms profile import / profile sync interchangeably.
How to create custom properties in user profile?
Because there are no remote APIs for creating custom properties in the user profile service, this step must be performed manually for each of the tenants where custom user profile properties are needed (this only needs to be done once per tenant). Only user profile properties that are not “allowed to be edited by end users” can be imported.
APPLIES TO: 2013 2016 2019 SharePoint in Microsoft 365 You can use the SharePoint Active Directory import option (AD import) as an alternative to using Microsoft Identity Manager (MIM) to import user profile data from Active Directory Domain Services (AD DS) in your domain.
Where do I find the user profile Service property?
The user profile service property used for the lookup depends on the value of idType. A map from the source property name to the user profile service property name. Note that the user profile service properties must already exist. The key is the property name used in the source file; the value is the property name used in the user profile service.
Can a JSON object be imported into a user profile?
Only user profile properties that are not “allowed to be edited by end users” can be imported. Trying to import a JSON object property to a user profile property that is marked as “editable by end users” results in an exception when the CSOM API is called.