Skip to content

Commit 33a671b

Browse files
authored
Fix typo in Front Door FAQ and add migration note
Corrected a typo in the question about Azure Front Door POPs and added a note regarding updating DevOps pipeline scripts after migration.
1 parent e4532df commit 33a671b

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

articles/frontdoor/front-door-faq.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ sections:
5252
answer: |
5353
Azure Front Door isn't limited to any Azure region, but operates globally. The only location you have to choose when you create a Front Door is the location of the resource group, which determines where the resource group's metadata get stored. The Front Door profile is a global resource and its configuration is distributed to all edge locations worldwide.
5454
- question: |
55-
What are the locations of the Azure Front Door POPs (points-of-presence)?
55+
What are the locations of the Azure Front Door POPs (points-of-presfence)?
5656
answer: |
5757
For the complete list of points of presence (POPs) that provide global load balancing and content delivery for Azure Front Door, see [Azure Front Door POP locations](edge-locations-by-region.md). This list is updated regularly as new POPs are added or removed. You can also use the Azure Resource Manager API to query the current list of POPs programmatically.
5858
- question: |
@@ -346,6 +346,8 @@ sections:
346346
- Customers who didn't set the said Feature Flag before April 9, 2026, their profiles will be migrated to Azure Front Door Standard or Premium SKU on a "best effort" basis and should watch for an email related to their migration status. You can also check migration status by following steps in the following question.
347347
- Customers who set the said feature flag but are still consuming services with classic SKUs will have until April 14, 2026 to complete migration or move to BYOC.
348348
349+
After migration to Azure Front Door Standard/Premium, [update your DevOps pipeline scripts](https://learn.microsoft.com/en-us/azure/frontdoor/post-migration-dev-ops-experience) to deploy and manage the new Front Door Standard/Premium resources.
350+
349351
**Azure Front Door (classic)**
350352
351353
Before April 9, 2026:
@@ -357,6 +359,8 @@ sections:
357359
- For customers who do not set the feature flag by April 9, 2026, Microsoft will migrate their profiles to Azure Front Door Standard or Premium SKU on a "best effort" basis. Customers are advised to monitor their email for updates on migration status. You can also check migration status by following steps in the following question.
358360
- Customers who have set the said Feature Flag but are still consuming services with classic SKUs will have until April 14, 2026 to complete migration or move to BYOC.
359361

362+
After migration to Azure Front Door Standard/Premium, [update your DevOps pipeline scripts](https://learn.microsoft.com/en-us/azure/frontdoor/post-migration-dev-ops-experience) to deploy and manage the new Front Door Standard/Premium resources.
363+
360364
- question: |
361365
How to check the migration status?
362366
answer: |

0 commit comments

Comments
 (0)