Skip to content

Commit 18a3b30

Browse files
Heading capitalization
1 parent c82f95c commit 18a3b30

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/frontdoor/tier-migration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ Azure Front Door Standard/Premium uses a different resource provider namespace o
6161

6262
Azure Front Door Standard and Premium endpoints are generated to include a hash value to prevent your domain from being taken over. The format of the endpoint name is `<endpointname>-<hashvalue>.z01.azurefd.net`. The Classic Front Door endpoint name will continue to work after migration but we recommend replacing it with the newly created endpoint name from the Standard or Premium profile. For more information, see [Endpoint domain names](endpoint.md#endpoint-domain-names).
6363

64-
### Logs and Metrics
64+
### Logs and metrics
6565

6666
Diagnostic logs and metrics won't be migrated. Azure Front Door Standard/Premium log fields are different from Front Door (classic). The newer tier also has heath probe logs and is recommended you enable diagnostic logging after the migration complete. Standard and Premium tier also supports built-in reports that will start displaying data once the migration is done.
6767

@@ -115,4 +115,4 @@ The following table explains the various stages of the migration process and if
115115
## Next steps
116116

117117
* Understand the [mapping between Front Door tiers](tier-mapping.md) settings.
118-
* Learn how to [migrate from Classic to Standard/Premium tier](migrate-tier.md) using the Azure portal.
118+
* Learn how to [migrate from Classic to Standard/Premium tier](migrate-tier.md) using the Azure portal.

0 commit comments

Comments
 (0)