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
+14-5Lines changed: 14 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,12 @@ description: This article shows you where Azure customers receive Azure security
4
4
ms.topic: conceptual
5
5
ms.date: 10/27/2022
6
6
---
7
+
---
8
+
title: Stay informed about Azure security issues
9
+
description: This article shows you where Azure customers receive Azure security notifications and three steps you can follow to ensure security alerts reach the right people in your organization.
10
+
ms.topic: conceptual
11
+
ms.date: 10/27/2022
12
+
---
7
13
# Stay informed about Azure security issues
8
14
9
15
With the increased adoption of cloud computing, customers rely increasingly on Azure to run their workload for critical and non-critical business applications. It is important for you as Azure customers to stay informed about Azure security issues or privacy breaches and take the right action to protect your environment.
@@ -32,14 +38,16 @@ If a security issue requires direct action taken by subscription admins/owners,
32
38
>[!Note]
33
39
>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.
34
40
35
-
### Security issues affecting your Azure tenant workloads
41
+
### Security issues affecting your Azure workloads
36
42
37
-
We typically communicate security-related information affecting your Azure **tenant**workloads via **Email Notification**. We send an email notification to Global admin and Technical Contacts
43
+
We typically communicate security-related information affecting your Azure workloads via **Email Notification**. We send an email notification to Global Admin(s) and Technical Contact(s).
38
44
39
-
>[!Note]
40
-
>You should ensure that there is a **contactable email address** entered for your organization's [Global Admin](../active-directory/roles/permissions-reference.md) and [Technical contact](../active-directory/fundamentals/active-directory-properties-area.md) on your tenant. This email address is used for security issues that would have impact at the tenant level.
45
+
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.
41
46
42
-
## Three steps to help you stay informed about Azure security issues
47
+
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.
48
+
49
+
> [!Note]
50
+
> You should ensure that there is a **contactable email address** entered for your organization's [Global Admin](../active-directory/roles/permissions-reference.md) and [Technical contact](../active-directory/fundamentals/active-directory-properties-area.md) on your tenant. This email address is used for security issues that would have impact at the tenant level. ## Three steps to help you stay informed about Azure security issues
43
51
44
52
**1. Check Contact on Subscription Admin Owner Role**
45
53
@@ -58,3 +66,4 @@ Depending on your requirements, you can configure various alerts to use the same
58
66
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.
59
67
60
68
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