...
If you have no custom domains, you no longer need to worry as this removal of Azure Front Door will not impact you. However, if you have identified the custom domains, migrating them to Cloudeflare should be easyCloudflare should be a relatively straightforward process. However, you will need enlist the assistance of your IT, DevOps team, or a colleague with technical expertise who has access to update your DNS records.
| Info |
|---|
Please note that you As long as you migrate before Dec 1st, there is not risk of downtime doing any of the steps in this process. You also don't need to complete all these steps at the same time. For example, you can finish steps 1-5 on the same day and schedule step 6 for a later date. This allows you to work at your own pace and plan accordingly. |
...
Create a TXT record in your DNS settings.
Use the hostname and value provided by the Custom Hostname Migration tool.
| Expand | ||
|---|---|---|
| ||
On my DNS zone manger for my host, I add a new TXT record.  Then I input the values as found on the Custom Hostname Migration tool page.  |
...
Create a CNAME record in your DNS settings.
Use the hostname and value provided by the Custom Hostname Migration tool.
| Expand | ||
|---|---|---|
| ||
On my DNS zone manger for my host, I add a new CNAME record.  Then I input the values as found on the Custom Hostname Migration tool page.  |
...
Use the new value provided by the Custom Hostname Migration tool to update your original CNAME record. Change the CNAME from the current Azure Front Door value to the new Cloudflare value.
| Expand | ||
|---|---|---|
| ||
I find my old CNAME record that has a  I then update the value as found on the Custom Hostname Migration tool page.  |
...