You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-health/stay-informed-security.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,10 @@ Service Health notifications are published by Azure and contain information abou
27
27
28
28
**Email Notification**
29
29
30
-
If a security issue requires direct action taken by subscription admins/owners, or critical and sensitive resource information needs to be shared, we send an email notification to subscription admins/owners.
30
+
We send an email notification to subscription admins/owners when:
31
+
32
+
1. A security issue requires direct action by subscription admins/owners.
33
+
2. Critical and sensitive resource information needs to be shared.
31
34
32
35
>[!Note]
33
36
>You should ensure that there is a **contactable email address** as the [subscription administrator or subscription owner](../cost-management-billing/manage/add-change-subscription-administrator.md). This email address is used for security issues that would have impact at the subscription level.
@@ -38,9 +41,8 @@ We communicate security-related information affecting your Azure **tenant** work
38
41
39
42
> [!Note]
40
43
> You should ensure that there is a **contactable email address** entered for your organization's [Global Admin](../active-directory/roles/permissions-reference.md), [Technical contact](../active-directory/fundamentals/active-directory-properties-area.md), and [security admin](/azure/defender-for-cloud/permissions) on your tenant. This email address is used for security issues that would have impact at the tenant level.
41
-
As of June 2024, we're enhancing the visibility of our Azure Service Health security communications. Typically, notifications are issued at the corresponding level for which they are architected, i.e. if a service is architected at the subscription level, we will send communications at the subscription level. Conversely, if the service is architected at the tenant level (such as Entra) we will send communications at the tenant level.
42
44
43
-
However, when Microsoft determines a security event is particularly impactful AND architected at the subscription level, we will also proactively issue additional communications at the tenant level to guarantee the broadest possible awareness.
45
+
As of June 2024, we've enhanced the visibility of our Azure Service Health security communications. Typically, notifications are issued at the level for which they are architected. If a service is architected at the subscription level, we send communications at the subscription level. If the service is architected at the tenant level (such as Entra), we send communications at the tenant level. However, when Microsoft determines a security event is particularly impactful AND architected at the subscription level, we will also proactively issue additional communications at the tenant level to guarantee the broadest possible awareness.
44
46
45
47
## Three steps to help you stay informed about Azure security issues
46
48
@@ -58,6 +60,6 @@ Create **Azure Service Health** alerts for security events so that your organiza
58
60
59
61
Depending on your requirements, you can configure various alerts to use the same [action group](../azure-monitor/alerts/action-groups.md) or different action groups. Action group types include sending a voice call, SMS, or email. You can also trigger various types of automated actions.
60
62
61
-
There's an important difference between Service Health security advisories and [Microsoft Defender for Cloud](../defender-for-cloud/defender-for-cloud-introduction.md) security notifications. Security advisories in Service Health provide notifications dealing with platform vulnerabilities and security and privacy breaches at the subscription and tenant level, while security notifications in Microsoft Defender for Cloud communicate vulnerabilities that pertain to affected individual Azure resources.
63
+
There's an important difference between Service Health security advisories and [Microsoft Defender for Cloud](../defender-for-cloud/defender-for-cloud-introduction.md) security notifications. Security advisories in Service Health provide notifications dealing with platform vulnerabilities and security and privacy breaches at the subscription and tenant level. Security notifications in Microsoft Defender for Cloud communicate vulnerabilities that pertain to affected individual Azure resources.
62
64
63
65
More information about the Azure Service Health notifications can be found at: [What are Azure service health notifications? - Azure Service Health | Microsoft Learn](../service-health/service-health-notifications-properties.md)
0 commit comments