JaredL.03487 (Customer) asked a question.
I am in the process of migrating from an on-premise, NON-Microsoft email environment to Exchange Online. I already have Universal Sync and provisioning to 365 enabled and working, and I recently extended my AD schema to include Exchange attributes.
What I am finding is that the Exchange attributes set in AD are not syncing up to 365. For example, I have changed mailNickname, msExchHideFromAddressLists, and msExchSenderHintTranslations on a test user, but those values do not show up in 365. Those attributes are not mapped from AD to Okta, but I believe that is expected based on documentation (page 30 - https://support.okta.com/help/servlet/fileField?id=0BE2A00000004Sj) and should pass directly to 365. Universal Sync and provisioning are able to create users (with mailboxes) in 365 but without any of the Exchange attributes set in AD.
Any ideas on why the Exchange attributes will not push up? I do not see any errors in the import/sync process. I am able to successfully create distribution lists.
An additional note to my original description/question:
I know that Azure AD Connect requires a refresh to recognize the schema change after extending Exchange attributes in AD. Is anyone aware if a similar process/requirement exists for Okta when Universal Sync is in the mix?
you either need to bring the values into Okta then map to o365 or use AAD connect to sync the users.... we stuck with AAD connect