Skip to content

Commit e0d008d

Browse files
authored
Merge pull request #2 from duongau/afdtroubleshooting
AFD troubleshooting (metadata and links)
2 parents b3a0512 + ad608cb commit e0d008d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/frontdoor/troubleshoot-performance-issues.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: 'General Performance Troubleshooting of Azure Front Door'
3+
titleSuffix: Azure Front Door
34
description: In this article, investigate, diagnose and resolve potential latency or bandwidth issues associated with an Azure Front Door related site performance
45
services: frontdoor
56
author: stdoroff
@@ -8,6 +9,7 @@ ms.topic: how-to
89
ms.workload: infrastructure-services
910
ms.date: 08/30/2023
1011
ms.author: stdoroff
12+
#Customer intent: As a <type of user>, I want <some goal> so that <some reason>.
1113
---
1214

1315
# Azure Front Door Performance
@@ -117,7 +119,7 @@ This could be because of an ISP issue, the customer is using a VPN or they are a
117119
- Requesting Client Information
118120
- Requesting Client IP
119121
- Requesting Client Location
120-
- Requesting Client Path to Azure Environment (Usually identified with [TraceRoute](https://learn.microsoft.com/windows-server/administration/windows-commands/tracert), [PathPing](https://learn.microsoft.com/windows-server/administration/windows-commands/pathping) or a similar tool)
122+
- Requesting Client Path to Azure Environment (Usually identified with [TraceRoute](/windows-server/administration/windows-commands/tracert), [PathPing](/windows-server/administration/windows-commands/pathping) or a similar tool).
121123
122124
### Scenario 2 | Troubleshooting Steps
123125

0 commit comments

Comments
 (0)