<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
0D54z00008Oeo24CABOkta Classic EngineAdministrationAnswered2024-03-25T09:07:18.000Z2022-11-17T21:26:05.000Z2022-11-19T04:13:06.000Z
  • User16594883467582706479 (Customer Support Online Experience)

    Hi, @gsee5 (gsee5)​ 

     

    Thank you for posting on our Community page!

     

    I did some research and found this article which might help with your use case:

     

    Hope this helps!

     

    Thank you for reaching out to our Community and have a great day!

     

    _____________________________________________________________________________

    The Okta Community November newsletter is here. Get product updates and see our top contributing members.

    _____________________________________________________________________________

    If my answer helped, remember to select it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

    _____________________________________________________________________________

     

    Expand Post
  • gsee5 (gsee5)

    Thank you for the quick response Laura.

    Actually the application we use SSO for is Veeva. So when a user tries to login to Veeva CRM, the signle sign on from Azure AD works and gets him/her logged into Veeva. Now since the domain is channging on O365, do I need to change anything in the Veeva App in OKta dashboard ?

This question is closed.
Loading
Adding Multiple domains in Azure AD for SSO