User16751286156482744763 (Customer Success - SLED) asked a question.
Hi Team --
I am reaching out on behalf of our customer. The team were originally trying to map an EmployeeID attribute (which is a standard, default attribute in AzureAD) to Office 365. It was recommended to add the custom attribute to the app profile, in order to be able to sync a value from Okta to O365.
The team has mapped the employeeNumber attribute from OKTA to the ExtensionAttribute1 attribute in AzureAD and that is working, however that means they still aren’t sending any data to the Employee ID attribute in AzureAD. The fact that we can’t map anything from the OKTA profile to the Employee ID attribute in AzureAD is the concern here.
Why would a default field in AzureAD like Employee ID not be supported for SCIM from OKTA?
https://help.okta.com/en-us/Content/Topics/Apps/Office365/References/map-custom-atrributes.htm*2
cc: dgeorge1@charterschoolsusa.com
Hi @User16751286156482744763 (Customer Success - SLED) , Thank you for reaching out to the Okta Community!
I recommend opening up case to work with one of our Support Engineers as this requires a review of the current configuration. The public forum is not ideal for in-depth troubleshooting.
That being said, you might want to start by looking at the following article that seems to reference the issue you are seeing.
https://support.okta.com/help/s/article/Office-365-Universal-Sync-Extension-Attribute-issue-extensionAttribute1-through-extensionAttribute15?language=en_US
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Okta Identity Engine (OIE) Ask Me Anything: Get answers from product experts by clicking here.