Sync Unsupported User Profile Attributes for Microsoft Office 365 Provisioning in Okta
Last Updated:
Overview
Each provisioning type has a list of supported attributes that map from Okta into the Microsoft Office 365 instance. Sync unsupported user profile attributes, such as EmployeeType and EmployeeID, by mapping the unsupported attribute to a different supported Microsoft Office 365 attribute.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Microsoft Office 365
- Provisioning
- Mappings
Solution
How does Okta sync unsupported user profile attributes for Microsoft Office 365 provisioning?
Map the unsupported attribute, such as <employeeID>, to a different supported Microsoft Office 365 attribute, such as <ExtensionAttribute1>.
NOTE: This is a sample configuration for mapping an Active Directory (AD) attribute to an Okta attribute and mapping it to the Microsoft Office 365 ExtensionAttribute1. The Okta attribute can originate from Okta or any other profile source.
- Add a custom attribute to the Okta profile to map the AD attribute to Okta by navigating to the Profile Editor and adding the new attribute.
- Navigate to Profile Editor and select User (default).
- Select Add Attribute.
- Enter
<FromADemployeeID>as the attribute.
Review the sample attribute configuration in the provided image to verify the custom attribute details.
- Map the AD attribute to the newly added Okta attribute in the Profile Editor by configuring the Active Directory to Okta mappings.
- Navigate to Profile Editor and select Active Directory.
- Select Mappings and choose AD to Okta.
Review the AD attribute mapping configuration in the provided image to confirm the correct mapping from Active Directory to Okta.
- Map the Okta attribute to the supported Microsoft Office 365 attribute in the Profile Editor by configuring the Okta User to Microsoft Office 365 mappings.
- Navigate to Profile Editor and select Office 365.
- Select Mappings and choose Okta User to Microsoft Office 365.
Review the Okta attribute mapping configuration in the provided image to ensure the Okta attribute maps correctly to the Microsoft Office 365 extension attribute.
