Migrate Auth0 Custom Domains Without Downtime
Last Updated:
Overview
Migrating an Auth0 custom domain for rebranding previously required deleting the existing domain, resulting in unavoidable downtime. The Multiple Custom Domains (MCD) feature resolves this issue by supporting the configuration of a secondary custom domain before the removal of the original one. This approach ensures a seamless transition without service interruption.
Applies To
- Auth0
- Custom Domains
- Domain Migration
- Multiple Custom Domains
Cause
Previously, downtime was unavoidable during migrations to a new custom domain because a tenant could have only a single custom domain. The old, existing custom domain had to be deleted before configuring the new one.
With the new Multiple Custom Domains (MCD) feature, this migration without downtime is much easier to achieve.
Solution
How do Multiple Custom Domains prevent downtime during migration?
Enable the MCD feature and configure a secondary domain to facilitate a seamless migration.
- Acquire a secondary custom domain using the MCD feature to prevent downtime during migration or rebranding.
- Fulfill the prerequisites to enable the MCD feature by reviewing the MCD documentation.
- Set up a secondary domain, as Auth0 does not support migrating from a self-managed custom domain to the same Auth0-managed custom domain.
