|
| 1 | +--- |
| 2 | +title: Impacted resources support for outages |
| 3 | +description: This article details what is communicated to users and where they can view information about their impacted resources. |
| 4 | +ms.topic: conceptual |
| 5 | +ms.date: 11/9/2022 |
| 6 | +--- |
| 7 | + |
| 8 | +# Impacted Resources for Azure Outages |
| 9 | + |
| 10 | +[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 or Tenants that may be impacted by an outage, and their resource health signal to help customers evaluate impact. |
| 11 | + |
| 12 | +**In support of the impacted resource experience, Service Health has enabled a new feature to:** |
| 13 | + |
| 14 | +- Replace “Potential Impact” tab with “Impacted Resources” tab on Service Issues. |
| 15 | +- Display resources that are confirmed to be impacted by an outage. |
| 16 | +- 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. |
| 17 | +- Resource Health status of both confirmed and potential impacted resources showing the availability of the resource. |
| 18 | + |
| 19 | +This article details what is communicated to users and where they can view information about their impacted resources. |
| 20 | + |
| 21 | +>[!Note] |
| 22 | +>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. |
| 23 | +
|
| 24 | +## Impacted Resources for Outages on the Service Health Portal |
| 25 | + |
| 26 | +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. |
| 27 | + |
| 28 | +:::image type="content" source="./media/impacted-resource-outage/ir-portal.PNG" alt-text="Screenshot of Azure Service Health impacted resources information."::: |
| 29 | + |
| 30 | +##### Service Health provides the below information to users whose resources are impacted by an outage: |
| 31 | + |
| 32 | +|Column |Description | |
| 33 | +|---------|---------| |
| 34 | +|Resource Name|Name of resource| |
| 35 | +|Resource Health|Health status of a resource at that point in time| |
| 36 | +|Impact Type|Tells customers if their resource is confirmed to be impacted or potentially impacted| |
| 37 | +|Resource Type|Type of resource impacted (.ie Virtual Machines)| |
| 38 | +|Resource Group|Resource group which contains the impacted resource| |
| 39 | +|Location|Location which contains the impacted resource| |
| 40 | +|Subscription ID|Unique ID for the subscription that contains the impacted resource| |
| 41 | +|Subscription Name|Subscription name for the subscription which contains the impacted resource| |
| 42 | +|Tenant ID|Unique ID for the tenant that contains the impacted resource| |
| 43 | + |
| 44 | +## Resource Name |
| 45 | + |
| 46 | +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. |
| 47 | + |
| 48 | +It will be text only if there is no Resource Health signal available for this resource. |
| 49 | + |
| 50 | +## Impact Type |
| 51 | + |
| 52 | +This column will display values “Confirmed vs Potential” |
| 53 | + |
| 54 | +- *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. |
| 55 | +- *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. |
| 56 | + |
| 57 | +## Resource Health |
| 58 | + |
| 59 | +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. |
| 60 | + |
| 61 | +- 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. |
| 62 | +- 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. |
| 63 | + |
| 64 | +:::image type="content" source="./media/impacted-resource-outage/icons.PNG" alt-text="Screenshot of Impacted Resources health status icons and impact type"::: |
| 65 | + |
| 66 | + |
| 67 | +>[!Note] |
| 68 | +>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. |
| 69 | +
|
| 70 | +## Filters |
| 71 | + |
| 72 | +Customers can filter on the results using the below filters: |
| 73 | + |
| 74 | +- Impact type: Confirmed or Potential |
| 75 | +- Subscription ID: All Subscription IDs the user has access to |
| 76 | +- Status: Resource Health status column that shows Available, Unavailable, Degraded, Unknown, N/A |
| 77 | + |
| 78 | +## Export to CSV |
| 79 | + |
| 80 | +The list of impacted resources can be exported to an excel file by clicking on this option. |
0 commit comments