Skip to content

Commit 373e638

Browse files
committed
Updates from PR review
1 parent 3b6fecd commit 373e638

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/frontdoor/migrate-tier.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Your old Azure Front Door (classic) instance uses a different fully qualified do
134134

135135
You don't need to update your DNS records before or during the migration process. Azure Front Door automatically sends traffic that it receives on the Azure Front Door (classic) endpoint to your Azure Front Door Standard or Premium profile without you making any configuration changes.
136136

137-
However, when your migration is finished, we strongly recommend that you update your DNS records to direct traffic to the new Azure Front Door Standard or Premium endpoint. Changing your DNS records helps to ensure that your profile continues to work in the future. You don't need to plan this update to happen at any specific time, and you can schedule it at your convenience.
137+
However, when your migration is finished, we strongly recommend that you update your DNS records to direct traffic to the new Azure Front Door Standard or Premium endpoint. Changing your DNS records helps to ensure that your profile continues to work in the future. The change in DNS record doesn't cause any downtime. You don't need to plan this update to happen at any specific time, and you can schedule it at your convenience.
138138

139139
## Next steps
140140

0 commit comments

Comments
 (0)