Merge pull request #223977 from ShawnJackson/impacted-resources-outage

[AQ] edit pass: impacted-resources-outage

Author: ktoliver

articles/service-health/impacted-resources-outage.md

@@ -1,88 +1,68 @@
 ---
-title: Impacted resources support for outages
-description: This article details what is communicated to users and where they can view information about their impacted resources.
+title: Resource impact from Azure outages
+description: This article details where to find information from Azure Service Health about how Azure outages might affect your resources.
 ms.topic: conceptual
 ms.date: 12/16/2022
 ---
 
-# Impacted Resources for Azure Outages
+# Resource impact from Azure outages
 
-[Azure Service Health](https://azure.microsoft.com/get-started/azure-portal/service-health/) helps customers view any health events that impact their Subscriptions and Tenants. The Service Issues blade on Service Health shows any ongoing problems in Azure services that are impacting your resources. You can understand when the issue began, and what services and regions are impacted. Previously, the Potential Impact tab on the Service Issues blade was within the details of an incident. It showed any resources under a customer's Subscriptions that may be impacted by an outage, and their resource health signal to help customers evaluate impact.
+[Azure Service Health](https://azure.microsoft.com/get-started/azure-portal/service-health/) helps customers view any health events that affect their subscriptions and tenants. In the Azure portal, the **Service Issues** pane in **Service Health** shows any ongoing problems in Azure services that are affecting your resources. You can understand when each problem began, and what services and regions are affected. 
 
-**In support of the impacted resource experience, Service Health has enabled a new feature to:**
+Previously, the **Potential Impact** tab on the **Service Issues** pane appeared in the incident details section. It showed any resources under a subscription that an outage might affect, along with a signal from [Azure Resource Health](../service-health/resource-health-overview.md) to help you evaluate impact.
 
-- Replace “Potential Impact” tab with “Impacted Resources” tab on Service Issues.
-- Display resources that are confirmed to be impacted by an outage.
-- Display resources that are not confirmed to be impacted by an outage but could be impacted because they fall under a service or region that is confirmed to be impacted by an outage.
-- Resource Health status of both confirmed and potential impacted resources showing the availability of the resource.
+In support of the experience of viewing affected resources, Service Health has enabled a new feature to:
 
-This article details what is communicated to users and where they can view information about their impacted resources.
+- Replace the **Potential Impact** tab with an **Impacted Resources** tab on the **Service Issues** pane.
+- Display resources that are confirmed to be affected by an outage.
+- Display resources that are not confirmed to be affected by an outage but could be affected because they fall under a service or region that's confirmed to be affected.
+- Provide the status of both confirmed and potential affected resources to show their availability.
+
+This article details what Service Health communicates and where you can view information about your affected resources.
 
 >[!Note]
->This feature will be enabled to users in phases. Only selected subscription-level customers will start seeing the experience initially and gradually expand to 100% of subscription customers. In future this capability will be live for tenant level customers.
+>This feature will be rolled out in phases. Initially, only selected subscription-level customers will get the experience. The rollout will gradually expand to 100 percent of subscription customers. It will go live for tenant-level customers in the future.
 
-## Impacted Resources for Outages on the Service Health Portal
+## View affected resources
 
-The impacted resources tab under Azure portal-> Service Health ->Service Issues will display resources that are Confirmed to be impacted by an outage and resources that could Potentially be impacted by an outage. Below is an example of impacted resources tab for an incident on Service Issues with Confirmed and Potential impact resources.
+In the Azure portal, the **Impacted Resources** tab under **Service Health** > **Service Issues** displays resources that are or might be affected by an outage. The following example of the **Impacted Resources** tab shows an incident with confirmed and potentially affected resources.
 
-:::image type="content" source="./media/impacted-resource-outage/ir-portal-crop.PNG" alt-text="Screenshot of Azure Service Health impacted resources information.":::
+:::image type="content" source="./media/impacted-resource-outage/ir-portal-crop.PNG" alt-text="Screenshot of information about affected resources in Azure Service Health.":::
 
-##### Service Health provides the below information to users whose resources are impacted by an outage:
+Service Health provides the following information:
 
 |Column  |Description |
 |---------|---------|
-|Resource Name|Name of resource|
-|Resource Health|Health status of a resource at that point in time|
-|Impact Type|Tells customers if their resource is confirmed to be impacted or potentially impacted|
-|Resource Type|Type of resource impacted (.ie Virtual Machines)|
-|Resource Group|Resource group which contains the impacted resource|
-|Location|Location which contains the impacted resource|
-|Subscription ID|Unique ID for the subscription that contains the impacted resource|
-|Subscription Name|Subscription name for the subscription which contains the impacted resource|
-|Tenant ID|Unique ID for the tenant that contains the impacted resource|
-
-## Resource Name
-
-This will be the resource name of the resource. The resource name will be a clickable link that links to Resource Health page for this resource.
-
-It will be text only if there is no Resource Health signal available for this resource.
-
-## Impact Type
-
-This column will display values “Confirmed vs Potential”
-
-- *Confirmed*: Resource that was confirmed to be impacted by an outage. Customers should check the Summary section to make sure customer action items (if any) are taken to remediate the issue.
-- *Potential*: Resource that is not confirmed to be impacted by an outage but could potentially be impacted as it is under a service or region which is impacted by an outage. Customers are advised to look at the resource health and make sure everything is working as planned.
-
-## Resource Health
-
-The health status listed under **[Resource Health](../service-health/resource-health-overview.md)** refers to the status of a given resource at that point in time.
-
-- A health status of available means your resource is healthy but it may have been affected by the service event at a previous point in time.
-- A health status of degraded or unavailable (caused by a customer-initiated action or platform-initiated action) means your resource is impacted but could be now healthy and pending a status update.
-
-:::image type="content" source="./media/impacted-resource-outage/rh-cropped.PNG" alt-text="Screenshot of Impacted Resources health status icons and impact type":::
-
+|**Resource Name**|Name of the resource. This name is a clickable link that goes to the Resource Health page for the resource. If no Resource Health signal is available for the resource, this name is text only.|
+|**Resource Health**|Health status of the resource: <br><br>**Available**: Your resource is healthy, but a service event might have affected it at a previous point in time. <br><br>**Degraded** or **Unavailable**: A customer-initiated action or a platform-initiated action might have caused this status. It means your resource was affected but might now be healthy, pending a status update. <br><br>:::image type="content" source="./media/impacted-resource-outage/rh-cropped.PNG" alt-text="Screenshot of health statuses for a resource.":::|
+|**Impact Type**|Indication of whether the resource is or might be affected: <br><br>**Confirmed**: The resource is confirmed to be affected by an outage. Check the **Summary** section for any action items that you can take to remediate the problem. <br><br>**Potential**: The resource is not confirmed to be affected, but it could potentially be affected because it's under a service or region that an outage is affecting. Check the **Resource Health** column to make sure that everything is working as planned.|
+|**Resource Type**|Type of affected resource (for example, virtual machine).|
+|**Resource Group**|Resource group that contains the affected resource.|
+|**Location**|Location that contains the affected resource.|
+|**Subscription ID**|Unique ID for the subscription that contains the affected resource.|
+|**Subscription Name**|Subscription name for the subscription that contains the affected resource.|
+|**Tenant ID**|Unique ID for the tenant that contains the affected resource.|
 
 >[!Note]
->Not all resources will show resource health status. This will be shown on resources for which we have a resource health signal available only. The status of resources where the health signal is not available is shown as **“N/A”** and corresponding Resource name value will be text only not a clickable link.
+>Not all resources show a Resource Health status. The status appears only on resources for which a Resource Health signal is available. The status of resources for which a Resource Health signal is not available appears as **N/A**, and the corresponding **Resource Name** value is text instead of a clickable link.
 
-## Filters
+## Filter results
 
-Customers can filter on the results using the below filters:
+You can adjust the results by using these filters:
 
-- Impact type: Confirmed or Potential
-- Subscription ID: All Subscription IDs the user has access to
-- Status: Resource Health status column that shows Available, Unavailable, Degraded, Unknown, N/A
+- **Impact type**: Select **Confirmed** or **Potential**.
+- **Subscription ID**: Show all subscription IDs that the user can access.
+- **Status**: Focus on Resource Health status by selecting **Available**, **Unavailable**, **Degraded**, **Unknown**, or **N/A**.
 
 ## Export to CSV
 
-The list of impacted resources can be exported to an excel file by clicking on this option.
+To export the list of affected resources to an Excel file, select the **Export to CSV** option.
 
-## Accessing Impacted Resources programmatically via an API
+## Access affected resources programmatically via an API
 
-Outage impacted resource information can be retrieved programmatically using the Events API. The API documentation [here](https://learn.microsoft.com/rest/api/resourcehealth/2022-05-01/impacted-resources/list-by-subscription-id-and-event-id?tabs=HTTP) provides the details around how customers can access this data. 
+You can get information about outage-affected resources programmatically by using the Events API. For details on how to access this data, see the [API documentation](/rest/api/resourcehealth/2022-05-01/impacted-resources/list-by-subscription-id-and-event-id?tabs=HTTP). 
 
-## Next Steps
--  See [Introduction to Azure Service Health dashboard](service-health-overview.md) and [Introduction to Azure Resource Health](resource-health-overview.md) to understand more about them.
--  [Frequently asked questions about Azure Resource Health](resource-health-faq.yml)
+## Next steps
+-  [Introduction to the Azure Service Health dashboard](service-health-overview.md)
+- [Introduction to Azure Resource Health](resource-health-overview.md)
+- [Frequently asked questions about Azure Resource Health](resource-health-faq.yml)