<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D50Z00008G7UhfSAFOkta Classic EngineOkta Integration NetworkAnswered2024-04-19T07:26:56.000Z2018-04-30T09:42:33.000Z2018-08-22T18:45:33.000Z
Office 365 Attribute Mapping

Hello,

 

I have just found this topic : 

https://support.okta.com/help/Documentation/Knowledge_Article/Technical_Documentation/An-updated-AD-attribute-is-not-being-pushed-to-an-application-that-has-provisioning-and-Update-User-Attributes-enabled

 

We are planning to migrate to O365 Online soon.

 

Am I forced to create more than 100 attributes manually on Okta, and map them twice from AD=>Okta and Okta=>O365?

Or is it a bug that is planned to be fixed, so that I can use directly the "hasDirectoryUser()?findDirectoryUser " to map them directly from AD to O365?

 

Thanks for your help,

Clement


  • mike.davie1.5312945692819849E12 (Customer First Programs)

    The default mapping with "hasDirectoryUser()?findDirectoryUser()" does work for the supported attributes and you should not have to create custom attributes and change the mapping. The supported attributes will depend on which provisioning type you are using and can be seen at https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Okta_Enhancements_Office_365_Integration.htm

     

    The issue in that topic is usually only seen when trying to map one of the unsupported attributes, like ProxyAddresses, with the User Sync provisioning type. However, "hasDirectoryUser()?findDirectoryUser()" will work for that attribute in Universal Sync and changes in AD are updated in O365 as well. 

    Expand Post
This question is closed.
Loading
Office 365 Attribute Mapping