<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
0D54z00007wW8XICA0Okta Classic EngineDirectoriesAnswered2022-08-16T22:33:59.000Z2022-08-15T13:48:37.000Z2022-08-16T22:33:59.000Z

BrandonD.45175 (Customer) asked a question.

Okta Username Mapping is not Pushing Attribute to Microsoft 365 App

Hello, for our company, we have federated a domain within our Microsoft Office environment (@ardeo.org) via Okta's Admin portal. I was recently changing one user's Microsoft username and email from (firstname.lastname@ardeo.org) to (firstname.lastname@ardeoeducation.org) and then went ahead and tried to switch it back. The email changes back to its former state, however the username isn't reflecting the update which is an issue since that would mean that for the particular user, a potential threat could sign in using that user account since it's not solely SSO i.e. the non-federated domain being the current username allows for SWA access. I am trying to figure out how to get Okta to push the updates I make on Okta's end to be reflected in Microsoft. Let me know if you would like me to provide screenshots for further clarification, however I believe a call would be more beneficial in diving deeper and diagnosing the issue.

 

Best,

 

Brandon


This question is closed.
Loading
Okta Username Mapping is not Pushing Attribute to Microsoft 365 App