Why this matters
Changing the public destination before content is ready can expose an unfinished site.
Step by step
- Confirm the destination hosting is provisioned and identify the application and website root through its technical owner.
- Arrange an authorised preview method and test pages, forms and required integrations before scheduling the DNS change.
- Record successful tests and unresolved issues so the domain is switched only when the agreed destination is ready.
Keep the result of the final check and any unresolved question with your project records.
Availability depends on the product, permissions and management agreement. Use the existing support conversation for the same issue.
