Microsoft Cloud
Microsoft 365 Is Highly Available. Your Data Still Needs Its Own Recovery Plan.
Microsoft operates the Microsoft 365 platform, but service availability is not the same thing as having an independent backup and recovery strategy. Mayer Networks protects supported Microsoft 365 data with independent backup, long-term retention, ongoing monitoring and restoration assistance, so organizations have another recovery path when email, files or SharePoint content are deleted, corrupted or intentionally removed.
The distinction
Microsoft Keeps the Service Running. Mayer Networks Protects the Data Independently.
Microsoft operates the platform and provides real recovery capabilities inside it: recycle bins, retention policies and holds. Those are worth configuring. They are not the same thing as an independent backup strategy maintained on your behalf, because they live inside the same tenant, under the same policies and the same credentials as the data they cover.
Microsoft 365 provides
Platform availability
- Cloud service availability
- Native retention and recycle capabilities inside the tenant
- Microsoft infrastructure and platform-level resiliency
- Service continuity for the Microsoft 365 platform itself
Mayer Networks Microsoft 365 Backup provides
Independent recoverability
- Independent backup copies held outside the tenant
- Long-term retention set for your obligations
- Multiple backup sessions per day
- Granular restore of supported data
- Backup monitoring and administration
- Restoration assistance from the team that runs your tenant
Availability and independent recoverability are different things.
Business risk
Microsoft 365 Data Can Be Lost in More Than One Way.
Very little of this involves a Microsoft outage. Most Microsoft 365 data loss is ordinary: someone deleted something, someone left, or an account was used by the wrong person.
Accidental deletion
- A user deletes email they later need
- A OneDrive folder is removed during a cleanup
- A mailbox is deleted at offboarding
- SharePoint content is removed from a library or site
Intentional deletion
- A departing employee removes mail or files
- An insider deletes data deliberately
- A compromised account clears cloud content
- An attacker destroys information after gaining access
Corruption, ransomware, compromise
- Ransomware affects files that then sync into OneDrive
- A compromised account makes malicious changes
- Files are overwritten and the damage is found later
- Content is needed as it existed before an incident
The problem is not only what was deleted. It is when you realize it is missing.
Retention
The Important Question Is: When Did You Notice?
Deletion is rarely discovered on the day it happens. Retention decides whether the discovery date still falls inside a window where recovery is possible at all.
Discovered
The next day
Easy. Almost any recovery option still has the data.
Discovered
Three months later
A finance question surfaces a folder nobody has opened since spring.
Discovered
After an employee left
The account is gone, and so is the content that went with it.
Discovered
During an audit
Someone asks for records from a period nobody was thinking about.
Discovered
Years later
A contract, claim or public-records request needs a document from long ago.
Up to 7 years
of retention
The current Mayer Networks Microsoft 365 backup service is designed around long-term retention of up to seven years for supported data. For organizations with records obligations, audit exposure or public-records considerations, that is a materially longer recovery window than recycle-bin and native tenant retention scenarios are intended to serve.
Retention length applies to supported workloads and data types rather than to every Microsoft 365 object without limitation. Retention is set with you during scoping, reviewed as obligations change, and documented in the client’s agreement and backup design.
Coverage
What Mayer Networks Protects in Microsoft 365.
Coverage follows what the backup platform supports for each workload. Supported data types are confirmed during scoping and documented rather than assumed, because platform support changes over time.
Exchange Online
- Mailbox content and email
- Folders and individual messages
- Accepted calendar events where supported
- Mailbox-level recovery
OneDrive
User files
- Supported user files and folders
- Content synced from laptops and desktops
- Granular recovery of individual items
- Restore from selected backup dates and sessions
SharePoint Online
Document libraries
- Supported document data in libraries
- Restore from selected backup dates and sessions
- Supported site and document recovery
- Content behind Teams files where supported
Recovery points
Protection Runs Throughout the Day.
A single nightly capture means a full day of work can sit outside the most recent recovery point.
Exchange Online
Up to
6
backup sessions per day
Across the working day
Mail activity is continuous, so recovery points are too.
OneDrive
Up to
4
backup sessions per day
Across the working day
File changes are captured through the day, not just once overnight.
SharePoint Online
Up to
4
backup sessions per day
Across the working day
Library and document activity is picked up across the day.
More recovery points during the day reduce the gap between production activity and the point you can recover to.
Independence
The Recovery Copy Cannot Live Inside the Thing It Protects.
If the tenant, its policies or its credentials are the problem, a copy held inside that same tenant is part of the problem. Independence is the point of the design.
Step 01
Microsoft 365 tenant
Exchange Online, OneDrive and SharePoint data, in production.
Step 02
Cove backup
Scheduled backup sessions run against supported tenant data.
Step 03
Independent recovery copy
Held outside the tenant, in storage separate from tenant credentials.
Step 04
Up to 7-year retention
A recovery window sized to obligations rather than inherited defaults.
Step 05
Granular restore
One message, one file, one library, one mailbox, one point in time.
Granular recovery
You Should Not Have to Restore Everything to Recover One Thing.
Almost nobody asks to recover a whole tenant. They ask for the message a client says they sent, the folder that vanished from a shared library, or the document as it existed before last Tuesday.
An individual email
A single message, with its attachments, back where it belongs.
Mailbox content
Folders or a full mailbox recovered after deletion or offboarding.
A OneDrive file or folder
One item rather than a user's entire drive.
A SharePoint document
Supported document data restored from a selected backup session.
A point in time
Recovery from a chosen backup date rather than only the latest copy.
Original or alternate location
Restored back into place, or beside it for review, where supported.
The goal is to restore only what is needed, whenever possible.
The service
Backup Software Is the Tool. Mayer Networks Operates the Protection.
Licensing a backup product takes minutes. Knowing that the right data is protected, that sessions are completing, that retention still matches the obligation, and that a restore request gets handled the same day is a service. Mayer Networks already administers the Microsoft 365 tenant being protected, so a recovery request does not start with an introduction.
- Backup configuration for the tenant and its supported workloads
- Monitoring of backup sessions rather than trusting a dashboard nobody opens
- Ongoing administration as users, mailboxes and sites change
- Retention management against business and records obligations
- Investigation and correction when protection fails or a session does not complete
- Restoration assistance, performed by the team that already administers the tenant
We do not just turn the backup on.
Part of the security posture
Microsoft 365 Backup Is Part of the Cybersecurity Posture.
Microsoft 365 holds email, documents and identity, which makes it a security boundary as much as a productivity platform. Backup is the last stage of that posture, not a separate purchase.
Prevent
MFA, conditional access, identity controls and email security reduce how often an account is taken.
MFA & IdentityDetect
Identity threat detection and security monitoring surface misuse of a legitimate account.
Security MonitoringRecover
Microsoft 365 backup returns the mail, files and documents an incident removed or changed.
You are here
Security reduces the chance of an incident. Backup reduces the impact when prevention fails.
The same standard is described across Cybersecurity, Email Security and Backup & Data Protection. Microsoft 365 is one of the environments that has to be recoverable, not a separate conversation.
Platform
Powered by Cove Data Protection by N-able.
Mayer Networks uses Cove Data Protection by N-able for Microsoft 365 backup and recovery. Cove writes the recovery copy into its own cloud storage, which keeps that copy independent of both the tenant and your local infrastructure.
%20--%3e%3csvg%20version='1.1'%20id='Artwork'%20xmlns='http://www.w3.org/2000/svg'%20xmlns:xlink='http://www.w3.org/1999/xlink'%20x='0px'%20y='0px'%20viewBox='0%200%20500%2091.68'%20style='enable-background:new%200%200%20500%2091.68;'%20xml:space='preserve'%3e%3cstyle%20type='text/css'%3e%20.st0{fill:%23C046FF;}%20%3c/style%3e%3cg%3e%3cpolygon%20class='st0'%20points='91.7,64.85%2059.26,32.43%20124.13,32.43%20124.13,64.85%20'/%3e%3cpath%20d='M0,0h26.83L91.7,64.85v26.83H64.87L32.43,59.25v32.43H0V0z%20M59.18,32.43h32.43V0H59.18V32.43z%20M168.2,37.34v38.8h-11.64%20V21.13h12.01l30.83,37.34l0.53,0.93V21.13h11.64v55.01h-11.56l-31.13-37.72L168.2,37.34z%20M253.65,54.89h-31.24v-12.5h31.24V54.89z%20M302.7,64.11h-28.22l-5.31,12.03h-13.05l25.87-55.01h12.82l26.25,55.01h-12.82L302.7,64.11z%20M288.36,32.86L278.95,54h19.12%20L288.36,32.86z%20M328.82,76.14V21.13h28.07c8.6,0,15,1.07,19.2,3.2c4.2,2.13,6.3,5.85,6.3,11.15v0.39c0,3.45-0.83,6.09-2.5,7.95%20c-1.67,1.85-4.25,3.16-7.74,3.93c3.95,0.72,6.85,2.01,8.72,3.86c1.87,1.85,2.81,4.66,2.81,8.41v0.23c0,5.81-2.23,9.91-6.68,12.3%20c-4.45,2.39-10.95,3.59-19.5,3.59H328.82z%20M340.66,30.93v12.19h17.3c3.74,0,6.75-0.36,9.03-1.08c2.28-0.72,3.41-2.34,3.41-4.86%20v-0.31c0-2.57-0.99-4.2-2.96-4.9c-1.97-0.69-5.26-1.04-9.86-1.04H340.66z%20M340.66,52.77V65.8h15.33c2.07,0,3.89-0.05,5.46-0.15%20c1.57-0.1,2.91-0.26,4.02-0.46c2.17-0.36,3.68-1.02,4.51-1.97c0.83-0.95,1.25-2.22,1.25-3.82v-0.23c0-0.87-0.11-1.65-0.34-2.31%20c-0.23-0.67-0.54-1.23-0.95-1.7c-0.91-0.93-2.42-1.55-4.51-1.89c-2.1-0.33-5-0.5-8.69-0.5H340.66z%20M393.67,76.14V21.13h12.29v43.36%20h33.91v11.65H393.67z%20M500,76.14h-50.3V21.13h48.71v10.41h-37.02v11.73h31.33v10.49h-31.33v11.57H500V76.14z'/%3e%3c/g%3e%3c/svg%3e)
The product matters less than who runs it. Backup sessions are configured, monitored and restored by the same team that administers the tenant. The same platform also protects servers, workstations and file data, where local recovery storage is commonly paired with protected offsite copies.
Scope, retention, supported data types and restore expectations are reviewed against your tenant during scoping and documented rather than left as assumptions. As people, mailboxes and sites change, the protection is administered to match, and restoration assistance is part of the service rather than a separate engagement.
Does Microsoft 365 Backup protect every type of Microsoft 365 data?
No. Coverage depends on the workload and the supported data types. Some Microsoft 365 object types are outside the current backup scope, including OneNote, certain SharePoint elements and some public folder, task and archived content. Previous file versions and some deleted or unlicensed account scenarios also carry limitations. Mayer Networks documents what is and is not protected in the client's agreement and backup design.
Doesn't Microsoft keep deleted items?
Yes. Recycle bins, retention policies and holds are real capabilities worth configuring. They serve a different requirement: they are bounded by the tenant and its own policies. An independent backup with separate retention covers the cases where the tenant, its policies or its credentials are the problem.
How long is data retained?
The current service is designed around retention of up to seven years for supported data. The right window comes from business needs, legal advice and records obligations, and public bodies often have specific requirements.
How often does the backup run?
Up to six backup sessions per day for Exchange Online and up to four per day for OneDrive and SharePoint, which reduces the gap between production activity and the most recent recovery point.
Can we restore a single email or file?
Yes. Supported restores can be granular down to an individual message, file, folder or document, from a selected backup date, to the original or an alternate location where supported.
What about Teams messages?
Teams content stored in SharePoint and Exchange is covered where supported. Chat coverage depends on what the platform supports at the time and is confirmed during scoping rather than assumed.
Which product do you use?
Cove Data Protection by N-able. Cove protects supported tenant data into Cove cloud storage, independent of the tenant itself. Mayer Networks configures, monitors, administers and restores it.
Mayer Networks participates in Microsoft's Services Provider License Agreement program for eligible hosted Microsoft workloads. Microsoft does not own, operate, or certify Mayer Networks infrastructure.
If Microsoft 365 Data Disappears Tomorrow, Where Will You Recover It From?
Mayer Networks can provide independent Microsoft 365 backup, long-term retention, ongoing monitoring and restoration assistance as part of the managed Microsoft 365 environment.