Skip to content

Commit 87626f0

Browse files
committed
freshness review
1 parent 600c573 commit 87626f0

File tree

1 file changed

+11
-13
lines changed

1 file changed

+11
-13
lines changed

articles/cdn/cdn-resource-health.md

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -3,17 +3,15 @@ title: Monitor the health of Azure CDN resources| Microsoft Docs
33
description: Learn how to monitor the health of your Azure CDN resources using Azure Resource Health.
44
services: cdn
55
documentationcenter: .net
6-
author: zhangmanling
7-
manager: zhangmanling
8-
editor: ''
9-
6+
author: duongau
7+
manager: kumudd
108
ms.assetid: bf23bd89-35b2-4aca-ac7f-68ee02953f31
119
ms.service: azure-cdn
1210
ms.topic: how-to
1311
ms.tgt_pltfrm: na
1412
ms.workload: integration
15-
ms.date: 01/23/2017
16-
ms.author: mazha
13+
ms.date: 02/27/2023
14+
ms.author: duau
1715

1816
---
1917

@@ -30,11 +28,11 @@ Azure CDN Resource health is a subset of [Azure resource health](../service-heal
3028

3129
1. In the [Azure portal](https://portal.azure.com), browse to your CDN profile.
3230

33-
2. Click the **Settings** button.
31+
2. Select the **Settings** button.
3432

3533
![Settings button](./media/cdn-resource-health/cdn-profile-settings.png)
3634

37-
3. Under *Support + troubleshooting*, click **Resource health**.
35+
3. Under *Support + troubleshooting*, select **Resource health**.
3836

3937
![CDN resource health](./media/cdn-resource-health/cdn-resource-health3.png)
4038

@@ -45,16 +43,16 @@ Azure CDN Resource health is a subset of [Azure resource health](../service-heal
4543
4644
## Azure CDN-specific messages
4745

48-
Statuses related to Azure CDN resource health can be found below.
46+
Statuses related to Azure CDN resource health can be found in the following table:
4947

5048
|Message | Recommended Action |
5149
|---|---|
5250
|You may have stopped, removed, or misconfigured one or more of your CDN endpoints | You may have stopped, removed, or misconfigured one or more of your CDN endpoints.|
53-
|We are sorry, the CDN management service is currently unavailable | Check back here for status updates; If your problem persists after the expected resolution time, contact support.|
51+
|We're sorry, the CDN management service is currently unavailable | Check back here for status updates; If your problem persists after the expected resolution time, contact support.|
5452
|We're sorry, your CDN endpoints may be impacted by ongoing issues with some of our CDN providers | Check back here for status updates; Use the Troubleshoot tool to learn how to test your origin and CDN endpoint; If your problem persists after the expected resolution time, contact support. |
55-
|We're sorry, CDN endpoint configuration changes are experiencing propagation delays | Check back here for status updates; If your configuration changes are not fully propagated in the expected time, contact support.|
56-
|We're sorry, we are experiencing issues loading the supplemental portal | Check back here for status updates; If your problem persists after the expected resolution time, contact support.|
57-
We are sorry, we are experiencing issues with some of our CDN providers | Check back here for status updates; If your problem persists after the expected resolution time, contact support. |
53+
|We're sorry, CDN endpoint configuration changes are experiencing propagation delays | Check back here for status updates; If your configuration changes aren't fully propagated in the expected time, contact support.|
54+
|We're sorry, we're experiencing issues loading the supplemental portal | Check back here for status updates; If your problem persists after the expected resolution time, contact support.|
55+
We're sorry, we're experiencing issues with some of our CDN providers | Check back here for status updates; If your problem persists after the expected resolution time, contact support. |
5856

5957
## Next steps
6058

0 commit comments

Comments
 (0)