Key Points
- The Microsoft 365 shared responsibility model delineates data-protection obligations between Microsoft and the customer, specifying backup, retention, and governance ownership.
- Assign clear RACI (Responsible, Accountable, Consulted, Informed) roles for key operational controls like MFA, retention, and DLP to enhance accountability.
- Implement Zero Trust with MFA, Conditional Access, and Privileged Access Management (PIM) to mitigate accidental or malicious data loss.
- Standardize backup scope, frequency, retention, and restore testing across OneDrive, SharePoint, and other tools.
- Enforce Role-Based Access Control (RBAC), remove unused admin rights, and use Privileged Identity Management for JIT access.
After the widespread adoption of cloud computing, data management has become more important than ever. Microsoft 365 provides native data protection and backup capabilities, but organizations still need to define appropriate backup and recovery strategies for workloads such as OneDrive, SharePoint, and Teams. MSPs can help operationalize the customer’s responsibilities under the Microsoft 365 shared responsibility model and standardize work data preservation across Microsoft 365 workloads.
This helps identify which data is covered by Microsoft 365’s native protection and recovery capabilities and establishes additional workflows based on the organization’s backup requirements. This guide explains how to operationalize internal data backups with concrete steps.
How to build a Microsoft 365 shared responsibility model
This guide builds upon Microsoft’s own shared responsibility model while incorporating client-specific context to elevate your backup and recovery standards with a Remote Monitoring and Management (RMM) platform.
Prerequisites:
- Agreed Recovery Time Objective (RTO) and Recovery Point Objective (RPO) per workload and a named business owner for each
- Admin access to Microsoft 365, Microsoft Entra ID roles, and backup tooling
- A document workspace for policies, RACIs, and monthly evidence packs
- A change window and ticketing process for configuration updates
Step 1: Build the tenant RACI and control map
Start by listing operational controls you need to monitor in each workspace and mapping roles and responsibilities. This enhances governance from the start and improves incident response. For each control (e.g., MFA, Data loss prevention, retention policies), set someone:
- Responsible: Individuals or a team tasked with overseeing operational controls
- Accountable: An entity that deals with risk and outcome
- Consulted: Sources of expert advice and vital input
- Informed: Persons who should receive updates and final results
For example, your backup and recovery control map should look something like this:
| Activity | Responsible | Accountable | Consulted | Informed |
| Select a backup solution | IT operations team | IT Manager | Microsoft partner | Executive leadership |
| Schedule backups | IT operations team | IT Manager | Vendor support line | Relevant business units |
| Test restore workflows | IT operations team | IT Manager | Data security team | Executive leadership |
Step 2: Protect identity and access first
Apply Zero Trust principles with privileged access controls and Conditional Access to restrict access and administrative privileges in Microsoft 365. This helps reduce unauthorized access, excessive privileges, and related data-loss risks.
Use Cases: Taking precautions (e.g., time-bound admin rights and additional approvals) to reduce privileged-access risks.
Prerequisites: Microsoft 365 Business Premium, administrative privileges in Microsoft Entra.
- Sign in to Microsoft Entra Admin Center.
- To configure authentication methods for MFA, go to Entra ID > Authentication methods > Policies.
- Enable the appropriate authentication methods for the required users and groups.
- To require MFA, go to Entra ID > Conditional Access > Policies > New policy.
- Select the appropriate users and target resources, then configure the policy to require MFA.
- To configure privileged access, go to ID Governance > Privileged Identity Management > Microsoft Entra roles > Roles.
- Select the appropriate role, assign users as eligible, and configure time-bound activation requirements and approvals as needed.
Step 3: Define workload backup coverage
Set backup and restore goals based on technical constraints and tools you and your clients rely on. Define and document the following:
- Backup scope
- Backup frequency
- Data retention
- Encryption protocols
- Storage locations
- Scheduled restore tests per workload
- Backup gaps (e.g., unsupported file types, workarounds done, etc.)
Step 4: Separate retention, archiving, and backup
Microsoft 365 retention capabilities can handle the bulk of retention and SLA adherence, but they are not a substitute for backup and may not provide the point-in-time recovery required for every recovery scenario. Strengthen your storage management and backup with an all-in-one backup tool that shows clear ROI.
Step 5: Apply least privilege with Microsoft Entra roles
Role-based access control (RBAC) helps specify user permissions across your enterprise, enhancing your Microsoft 365 shared responsibility model. To enforce this, your IT team needs to do the following:
Assign role-based tasks
- Assign read-only permissions to security staff who need to review reports.
- Give compliance admin rights to your SLA team for retention policies.
- Assign the minimum required Exchange permissions to email managers for mailbox visibility.
- Provide Helpdesk admin rights for password resets, not global admin privileges.
Remove unused global admin rights
- Run monthly audits on global admin users.
- Remove Global Administrator rights from former contractors.
- Maintain 2-3 emergency accounts with global rights.
Implement approvals and time-based rights
- Managers must approve elevated roles.
- Enforce Privileged Identity Management (PIM) to manage short-term user access.
- Configure real-time alerts for permission changes.
- Use MFA to create secure approval workflows.
Audit new role assignments regularly
- Audit responsibility shifts every week.
- Review new admin role assignments every month.
- Compare current permissions with your control map to detect permission drift.
Step 6: Monitor, test, and ship evidence
Regular audits help maintain operational standards in between major stakeholder meetings. When you include your Microsoft 365 shared responsibility model in your monthly newsletter:
- Keep track of backup tests with a centralized platform.
- Create scorecards for backup success rates.
- Coordinate license tracking with asset managers.
- Include snapshots to demonstrate the success of your shared responsibility model.
Step 7: Package your Microsoft 365 shared responsibility model as a managed service
Your Microsoft 365 backup policies can not only protect your data, but also attract new business while keeping existing ones.
Market your shared responsibility model in your latest offerings to gain new clients, increase retention, and maintain your competitive edge over other MSPs without an operationalized Microsoft 365 responsibility model.
NinjaOne integration streamlines Microsoft 365 shared responsibility model backup plans
The NinjaOne dashboard provides meaningful insight into Microsoft 365 backup and recovery operations. Here’s how NinjaOne simplifies the process:
Step | Without NinjaOne | With NinjaOne |
| Build the tenant RACI (Responsible, Accountable, Consulted, Informed) and control map. | Spreadsheets tracked and updated manually; no version control | Centralized operational data and reporting to support RACI and control reviews |
| Protect identity and access first. | Multiple tools for authentication, conditional access, identity management, etc. | Backup and recovery of Microsoft Entra objects and configurations |
| Define workload backup coverage. | Separate backup schedules across workloads and manual restores | Automated backup scheduling, restore capabilities, and reports all in one platform |
| Separate retention, archiving, and backup. | Reliance on Microsoft’s native retention and recovery capabilities | Granular restore options, built-in recovery features, and configurable backup retention |
| Monitor, test, and ship evidence | Manual data collection and inconsistent report templates | Built-in data visualization, scorecards, and client-friendly reports |
| Package your Microsoft 365 shared responsibility model | Limited insights and difficulty in demonstrating ROI | Branded dashboards showcasing backup success and SLA performance metrics |
Systematize your shared responsibility model
Creating data-backed workflows to safeguard data on and off the cloud reassures your current clientele while attracting new business. To operationalize your Microsoft 365 shared responsibility model, establish tenant RACI, enforce MFA, create backups per workload, test regularly, archive results, and publish them monthly.
Related topics:
- How to Explain the Microsoft 365 Shared Responsibility Model to Clients
- How to Explain the Microsoft 365 Shared Responsibility Model to Clients (Video)
- Cloud Incident Response: Best Practices in 2026
- Why SaaS Backup Matters for MSPs
- How to Explain the Difference Between Archiving and Backup in Microsoft 365

