Do I Need Cloud-to-Cloud Backup for Microsoft 365 Business Continuity?
Many small businesses assume that storing data in Microsoft 365 means it is automatically backed up and recoverable in the event of accidental deletion, corruption, or ransomware. Under the Microsoft Shared Responsibility Model, Microsoft guarantees service availability, but the protection of customer data from human error or malicious activity remains the responsibility of the business owner. This article explains why a third-party cloud-to-cloud backup solution is essential for SharePoint, OneDrive, Teams, and Exchange Online, and how 220 Internet Services can implement automated, immutable backups to ensure rapid data restoration and minimal downtime.
Understanding the Shared Responsibility Model
Microsoft 365 is designed for high availability. This means Microsoft ensures that the servers are running and that you can access your email, files, and collaboration tools. However, availability is not the same as backup.
Microsoft’s responsibility is to maintain the infrastructure. Your responsibility is to protect the data within that infrastructure. If a user accidentally deletes a critical email in Exchange Online or a folder of documents in SharePoint, Microsoft does not provide a guaranteed long-term recovery point for every scenario.
Why cloud-to-cloud backup is essential for small business
For a small business, data loss can be catastrophic. Whether it is a client contract in OneDrive, a project discussion in Teams, or a calendar entry in Exchange Online, losing this information can lead to operational downtime and lost revenue.
Common data loss scenarios
- Accidental deletion: An employee deletes a file or email and empties the recycle bin before realising it was still needed.
- Malicious activity: A disgruntled employee or compromised account deletes critical business data.
- Ransomware: Malware encrypts files stored in OneDrive or SharePoint, syncing the encrypted versions across all devices.
- Retention gaps: Microsoft 365 has default retention policies, but these are not designed as a comprehensive backup strategy and can be complex to configure for long-term recovery.
Applications covered
A cloud-to-cloud backup solution protects the core pillars of Microsoft 365:
- Exchange Online: Emails, contacts, calendars, and tasks.
- OneDrive for Business: Individual user files and folders.
- SharePoint Online: Team sites, document libraries, and intranet content.
- Microsoft Teams: Chat messages, channel files, and configuration settings.
Recommended backup vendors
220 Internet Services works with several industry-leading vendors to provide cloud-to-cloud protection. Depending on your business size and requirements, we typically recommend:
- Veeam Backup for Microsoft 365: Ideal for businesses wanting granular control over backup repositories and flexible restore options.
- Datto SaaS Protection: A user-friendly solution with automated daily backups and simple point-and-click restoration.
- AvePoint Cloud Backup: Suitable for organisations with complex SharePoint and Teams environments requiring detailed governance and compliance reporting.
Implementation steps
220 Internet Services can help small businesses implement a robust Microsoft 365 backup strategy. We handle the deployment, configuration, and ongoing monitoring of your cloud-to-cloud backups to ensure your business continuity is never left to chance.
Step 1: Assessment
We review your current Microsoft 365 tenant and identify critical data sets across Exchange Online, OneDrive, SharePoint, and Teams.
Step 2: Vendor selection and deployment
For example, when deploying Veeam Backup for Microsoft 365, the process includes:
- Log in to the Veeam Backup for Microsoft 365 console.
- Navigate to
Organisationsand clickAdd Microsoft 365 Organisation. - Enter your Microsoft 365 tenant credentials and authenticate via Azure AD.
- Select the services to protect: Exchange Online, OneDrive for Business, SharePoint Online, and Microsoft Teams.
- Create a backup job and configure the schedule (default is typically once per day).
- Select the backup repository (local storage, object storage, or cloud repository).
- Enable
Immutable Backupsin the job settings to prevent ransomware from altering or deleting backup data. - Click
Applyand thenRun Job Nowto perform the initial backup.
Step 3: Configure retention and recovery objectives
We configure retention policies based on your business requirements. Typical small business settings include:
- Retention period: 1 to 7 years, depending on industry compliance needs.
- Recovery Point Objective (RPO): Usually 24 hours, meaning you can restore data to within one day of loss.
- Recovery Time Objective (RTO): Typically under 4 hours for critical data, allowing minimal downtime.
Licensing is typically charged per user per month. For small businesses, expect to pay between $3 and $6 AUD per user per month, depending on the vendor and features selected.
Step 4: Verification and testing
We test restoration processes to ensure data can be recovered quickly. This includes performing a test restore of a sample email, document, and SharePoint site to verify the backup is working correctly.
Step 5: Ongoing monitoring
We monitor backup health daily and alert you to any failures. Regular restore tests are scheduled quarterly to confirm that data remains recoverable.
Testing restores and monitoring backup health
Backing up data is only half the strategy. You must verify that you can actually restore it when needed.
Regular restore tests
We recommend performing a test restore at least once per quarter. Restore a random selection of emails, files, and SharePoint documents to a test location to confirm integrity.
Monitoring backup failures
Backup jobs can fail due to authentication issues, connectivity problems, or licensing changes. 220 Internet Services monitors backup consoles for failed jobs and addresses errors immediately. Do not assume your data is protected simply because a backup job was created.
Troubleshooting common backup issues
Failed backups
If a backup job fails, check the following:
- Verify that the service account used for backup has the required permissions (Global Administrator or delegated access).
- Check for changes to multi-factor authentication or conditional access policies that may block the backup service.
- Review the backup console error logs for specific failure codes.
Authentication errors
Authentication errors often occur after a password change or when Azure AD conditional access policies are updated. Re-authenticate the Microsoft 365 connection in the backup console by navigating to Organisations, selecting your tenant, and clicking Reconnect or Refresh Credentials.
Slow restore times
Slow restores are usually caused by network bandwidth limitations or large data volumes. To improve restore speed:
- Restore during off-peak hours to reduce network congestion.
- Restore granular items (single emails or files) rather than entire mailboxes or sites where possible.
- Ensure your internet connection is stable and not saturated by other cloud services.
Frequently asked questions
Isn't the Recycle Bin enough?
The Recycle Bin provides short-term recovery, but items are permanently deleted after a set period. Once that window closes, the data is gone unless you have a third-party backup.
Does this protect against ransomware?
Yes. Because cloud-to-cloud backups are immutable and stored separately from your production environment, you can restore clean versions of your files without paying a ransom.
Is this expensive for a small business?
Cloud-to-cloud backup is typically priced per user per month, making it a scalable and affordable insurance policy for small businesses.