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/security/fundamentals/shared-responsibility.md
+44-6Lines changed: 44 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: msmbaldwin
6
6
ms.service: security
7
7
ms.subservice: security-fundamentals
8
8
ms.topic: article
9
-
ms.date: 12/03/2025
9
+
ms.date: 01/06/2026
10
10
ms.author: mbaldwin
11
11
#customer intent: As a cloud security administrator, I want to understand the shared responsibility model in Azure so that I can clearly identify which security tasks are mine and which are handled by Microsoft.
12
12
---
@@ -15,18 +15,56 @@ ms.author: mbaldwin
15
15
As you consider and evaluate public cloud services, it's critical to understand the shared responsibility model and which security tasks the cloud provider handles and which tasks you handle. The workload responsibilities vary depending on whether the workload is hosted on Software as a Service (SaaS), Platform as a Service (PaaS), Infrastructure as a Service (IaaS), or in an on-premises datacenter.
16
16
17
17
## Division of responsibility
18
-
In an on-premises datacenter, you own the whole stack. As you move to the cloud some responsibilities transfer to Microsoft. The following diagram illustrates the areas of responsibility between you and Microsoft, according to the type of deployment of your stack.
18
+
19
+
In an on-premises datacenter, you own the whole stack. As you move to the cloud, some responsibilities transfer to Microsoft. The following diagram illustrates the areas of responsibility between you and Microsoft, according to the type of deployment of your stack.
For all cloud deployment types, you own your data and identities. You're responsible for protecting the security of your data and identities, on-premises resources, and the cloud components you control. Cloud components you control vary by service type.
23
24
25
+
### Responsibility matrix
26
+
27
+
The following table details the division of responsibility between you and Microsoft for each area of your stack:
| Operating system | Customer | Customer | Microsoft | Microsoft |
38
+
| Physical hosts | Customer | Microsoft | Microsoft | Microsoft |
39
+
| Physical network | Customer | Microsoft | Microsoft | Microsoft |
40
+
| Physical datacenter | Customer | Microsoft | Microsoft | Microsoft |
41
+
42
+
### Responsibilities you always retain
43
+
24
44
Regardless of the type of deployment, you always retain the following responsibilities:
25
45
26
-
- Data
27
-
- Endpoints
28
-
- Account
29
-
- Access management
46
+
-**Data** - You're responsible for your data, including data classification, data protection, encryption decisions, and compliance with data governance requirements.
47
+
-**Endpoints** - You're responsible for protecting client devices and endpoints that access your cloud services, including mobile devices, laptops, and desktops.
48
+
-**Accounts** - You're responsible for managing user accounts, including creating, managing, and removing user access.
49
+
-**Access management** - You're responsible for implementing and managing access controls, including role-based access control (RBAC), multifactor authentication, and conditional access policies.
50
+
51
+
### Shared responsibilities explained
52
+
53
+
Some responsibilities are shared between you and Microsoft, with the division varying by service model:
54
+
55
+
-**Applications** - In IaaS, you're fully responsible for deployed applications. In PaaS and SaaS, Microsoft manages parts of the application stack, but you're responsible for application configuration, code security, and access controls.
56
+
-**Network controls** - In IaaS, you configure all network security including firewalls and network segmentation. In PaaS, Microsoft provides baseline network security, but you configure application-level network controls. In SaaS, Microsoft manages network security.
57
+
-**Client devices** - In SaaS scenarios, Microsoft may provide some device management capabilities, but you're responsible for endpoint protection and compliance.
58
+
59
+
### Microsoft responsibilities
60
+
61
+
Microsoft is responsible for the underlying cloud infrastructure, which includes:
62
+
63
+
-**Physical security** - Securing datacenters, including facilities, physical access controls, and environmental controls.
64
+
-**Physical network** - Managing network infrastructure, including routers, switches, and cables within datacenters.
65
+
-**Physical hosts** - Managing and maintaining the physical servers that host cloud services.
66
+
-**Hypervisor** - Managing the virtualization layer that enables virtual machines in IaaS and PaaS.
67
+
-**Platform services** - In PaaS and SaaS, Microsoft manages operating systems, runtime environments, and middleware.
0 commit comments