<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
0D5WR00002Kw3MU0AZOkta Classic EngineCustom URL DomainsAnswered2026-10-30T18:07:31.000Z2026-10-26T18:40:13.000Z2026-10-30T18:07:31.000Z

VictorK.52186 (Customer) asked a question.

Rename Okta domain after company rebrand

My company rebranded a few years ago, after having Okta set up. When we authenticate to access an application, the URL is still oldcompanyname.okta.com. We would like to change it to newcompanyname.okta.com. When I asked here a couple of years ago, I was told that I had to "break" the federations and redo them, which probably also means that I need to re-on board every user.

 

Is this still the case?

 

I have two applications - Microsoft 365 and Raiser's Edge. Sign on methods are WS-Federation and OpenID Connect respectively.

 

Thanks


  • Paul S. (Okta, Inc.)

    Hello @VictorK.52186 (Customer)​ Thank you for posting on our Community page!

     

    You do not need to re-onboard or re-create your users, but changing the URL does require updating the federation settings for both applications and will force a company-wide MFA re-enrollment.

    When you change the Okta org URL, the underlying user identities (like their UPNs, emails, and ImmutableIDs) remain intact. You do not have to delete and recreate users in Microsoft 365, Raiser's Edge, or Okta. However, because the URL acts as the "Issuer" for your authentication tokens, the existing federations will break until you point them to the new URL.

     

    1. Application Updates (The "Broken" Federations)

    You must update the configuration in both applications to trust the new Okta URL. This is a configuration swap, not a tear-down-and-rebuild:

    • Microsoft 365 (WS-Federation): You will need to use PowerShell (via MS Graph or the MSOnline module) to update your domain's federation settings. Specifically, you will update the IssuerUri, PassiveLogOnUri, and LogOffUri to point to the new newcompanyname.okta.com endpoints.
    • Raiser's Edge (OpenID Connect): You will need to log into the Raiser's Edge SSO configuration and update the OIDC Issuer URL and the well-known discovery endpoint (/.well-known/openid-configuration) to the new Okta domain.

     

    NOTE : You will also have to update all other SSO configurations (SAML) that you might have not only WS-FED and OIDC applications.

     

    2. The User Impact: MFA Re-enrollment

    While you don't have to re-onboard users into their applications, you will have to re-onboard their devices.

    Okta's official documentation states that Okta Verify enrollments are directly associated with your specific Okta subdomain. If Okta Support renames your subdomain, you must reset all active Okta Verify enrollments. Every single user will be forced to re-register their authenticator app on their phone. Additionally, if you use FIDO2/WebAuthn (Passkeys, YubiKeys, Windows Hello), those are strictly bound to the domain name and will also require total re-enrollment.

     

    I would recommend to also review our article on this matter:

    https://support.okta.com/help/s/article/how-to-rename-or-change-an-okta-subdomain?language=en_US

     

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

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best
  • Paul S. (Okta, Inc.)

    Hello @VictorK.52186 (Customer)​ Thank you for posting on our Community page!

     

    You do not need to re-onboard or re-create your users, but changing the URL does require updating the federation settings for both applications and will force a company-wide MFA re-enrollment.

    When you change the Okta org URL, the underlying user identities (like their UPNs, emails, and ImmutableIDs) remain intact. You do not have to delete and recreate users in Microsoft 365, Raiser's Edge, or Okta. However, because the URL acts as the "Issuer" for your authentication tokens, the existing federations will break until you point them to the new URL.

     

    1. Application Updates (The "Broken" Federations)

    You must update the configuration in both applications to trust the new Okta URL. This is a configuration swap, not a tear-down-and-rebuild:

    • Microsoft 365 (WS-Federation): You will need to use PowerShell (via MS Graph or the MSOnline module) to update your domain's federation settings. Specifically, you will update the IssuerUri, PassiveLogOnUri, and LogOffUri to point to the new newcompanyname.okta.com endpoints.
    • Raiser's Edge (OpenID Connect): You will need to log into the Raiser's Edge SSO configuration and update the OIDC Issuer URL and the well-known discovery endpoint (/.well-known/openid-configuration) to the new Okta domain.

     

    NOTE : You will also have to update all other SSO configurations (SAML) that you might have not only WS-FED and OIDC applications.

     

    2. The User Impact: MFA Re-enrollment

    While you don't have to re-onboard users into their applications, you will have to re-onboard their devices.

    Okta's official documentation states that Okta Verify enrollments are directly associated with your specific Okta subdomain. If Okta Support renames your subdomain, you must reset all active Okta Verify enrollments. Every single user will be forced to re-register their authenticator app on their phone. Additionally, if you use FIDO2/WebAuthn (Passkeys, YubiKeys, Windows Hello), those are strictly bound to the domain name and will also require total re-enrollment.

     

    I would recommend to also review our article on this matter:

    https://support.okta.com/help/s/article/how-to-rename-or-change-an-okta-subdomain?language=en_US

     

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

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best

Loading
Rename Okta domain after company rebrand
Okta Support Agent (Beta)

Terms of Service

Hello! I'm the Okta Support Agent (Beta), your go-to resource for questions about Okta products. Please remember for your security and privacy, do not share any Personally Identifiable Information (PII) such as passwords, IP addresses, or other details with me.

Okta Privacy Policy and Terms of Service apply