In the cloud, responsibilities are shared between the provider (Azure) and the user.
Responsibility distribution depends on the cloud service type (IaaS, PaaS, SaaS), with users having varying control over OS, network, and applications.
Users always manage data, devices, and access control, while Azure always handles physical infrastructure like data centres, networks, and hardware.
In the world of cloud computing, how do you know what you're responsible for? How would you know which tasks Azure is already taking care of for you?
For example, we've learnt that we won't need to worry about the operating system for some services (e.g. Azure Functions), but this doesn't apply to all of them (e.g. Azure Virtual Machines).
No stress! The Shared Responsibility Model is here to help us understand it. It uses the different cloud service types (IaaS, PaaS, SaaS) to break down exactly what you vs Azure should take care of.
In a traditional corporate data centre, the company takes care of everything:
It's a lot to handle.
But when we enter the cloud, these responsibilities are shared between the cloud provider and the cloud user.
Now, there are some grey areas that depend on the situation. For example, if you're using a cloud database, the cloud provider takes care of the database maintenance, while you're responsible for the data you put into it.
But if you set up a virtual machine and installed your own database on it, you take charge of database maintenance and the data within it.
Here's the cool part: the Shared Responsibility Model is closely linked to the types of cloud service you're using:
This nifty diagram (kudos to Microsoft!) illustrates who's responsible for what, depending on the type of cloud service.
Feeling curious? Here are explanations for each tier in the Shared Responsibility Model: