Skip to content

Commit 59cca81

Browse files
committed
updating confirmed vs potential
1 parent bb4052e commit 59cca81

File tree

1 file changed

+14
-15
lines changed

1 file changed

+14
-15
lines changed

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

Lines changed: 14 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,21 @@
11
---
22
title: Resource impact from Azure security incidents
3-
description: This article details where to find information from Azure Service Health about how Azure security incidents might affect your resources.
3+
description: This article details where to find information from Azure Service Health about how Azure security incidents impact your resources.
44
ms.topic: conceptual
55
ms.date: 3/3/2023
66
---
77

88
# Resource impact from Azure security incidents
99

10-
In support of the experience of viewing affected resources, Service Health has enabled a new feature to:
10+
In support of the experience of viewing impacted resources, Service Health has enabled a new feature to:
1111

12-
- Display resources that are confirmed to be impacted by a security incident.
13-
- Resource Health status of both confirmed and potentially impacted resources showing the availability of the resource.
14-
- Enabling role-based access control (RBAC) for viewing security incident impacted resource information.
12+
- Display resources impacted by a security incident
13+
- Enabling role-based access control (RBAC) for viewing security incident impacted resource information
1514

1615
This article details what is communicated to users and where they can view information about their impacted resources.
1716

1817
>[!Note]
19-
>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.
18+
>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 and tenant customers.
2019
2120
## Role Based Access (RBAC) For Security Incident Resource Impact
2221

@@ -34,35 +33,35 @@ This article details what is communicated to users and where they can view infor
3433

3534
## Viewing Impacted Resources for Security Incidents on the Service Health Portal
3635

37-
In the Azure portal, the Impacted Resources tab under Service Health > Security Advisories displays resources that are affected by a security incident. The following example of the Impacted Resources tab shows a security incident with impacted resources.
36+
In the Azure portal, the **Impacted Resources** tab under **Service Health** > **Security Advisories** displays resources that are impacted by a security incident. The following example of the Impacted Resources tab shows a security incident with impacted resources.
3837

39-
:::image type="content" source="./media/impacted-resource-sec/impact-security.PNG" alt-text="Screenshot of information about affected resources in Azure Service Health.":::
38+
:::image type="content" source="./media/impacted-resource-sec/impact-security.PNG" alt-text="Screenshot of information about impacted resources in Azure Service Health.":::
4039

41-
Service Health provides the below information to users whose resources are impacted by a security incident:
40+
Along with resource information, Service Health provides the below information to users whose resources are impacted by a security incident:
4241

4342
|Column |Description |
4443
|---------|---------|
45-
|**Subscription ID**|Unique ID for the subscription that contains the affected resource|
46-
|**Subscription Name**|Subscription name for the subscription that contains the affected resource|
44+
|**Subscription ID**|Unique ID for the subscription that contains the impacted resource|
45+
|**Subscription Name**|Subscription name for the subscription that contains the impacted resource|
4746
|**Resource Name**|This will be the resource name of the resource. It will be text only for security impacted resources|
4847
|**Tenant Name**|Unique ID for the tenant that contains the impacted resource|
49-
|**Tenant ID**|Unique ID for the tenant that contains the affected resource|
48+
|**Tenant ID**|Unique ID for the tenant that contains the impacted resource|
5049
|**App ID**| description
5150

5251
## Accessing Impacted Resources programmatically via an API
5352

54-
Impacted resource information for security incidents can be retrieved programmatically using the Events API. To access the list of resources impacted by a Security incident, the following endpoints can be used by users authorized with the above-mentioned roles.
53+
Impacted resource information for security incidents can be retrieved programmatically using the Events API. To access the list of resources impacted by a security incident, users authorized with the above-mentioned roles can use the following endpoints.
5554

5655
**Subscription**
5756

5857
```HTTP
59-
https://management.azure.com/subscriptions/(“subscriptionID”)/providers/microsoft.resourcehealth/events/3N8Z-DD8/listSecurityAdvisoryImpactedResources?api-version=2022-10-01
58+
https://management.azure.com/subscriptions/(“Subscription ID”)/providers/microsoft.resourcehealth/events/("Tracking ID")/listSecurityAdvisoryImpactedResources?api-version=2022-10-01
6059
```
6160

6261
**Tenant**
6362

6463
```HTTP
65-
https://management.azure.com/providers/microsoft.resourcehealth/events/3N8Z-DD8/listSecurityAdvisoryImpactedResources?api-version=2022-10-01
64+
https://management.azure.com/providers/microsoft.resourcehealth/events/("Tracking ID")/listSecurityAdvisoryImpactedResources?api-version=2022-10-01
6665
```
6766

6867
## Next steps

0 commit comments

Comments
 (0)