Blue Tree Technology®

Malware, ransomware, backup & recovery

Do You Need Separate Microsoft 365 Backup?

Published · Last reviewed · Next review due:

Blue Tree Technology® includes Microsoft 365 and Google Workspace backup in every Compass plan. Those backups run daily and use seven-year standard retention. Desktop, server and BCDR backups are paid add-ons with one-year default retention.

For our managed-services clients, the starting question is therefore not whether to buy the same backup protection again. It is whether the configured scope, recovery history, and restoration process match the business's needs.

Blue Tree Technology® includes Microsoft 365 and Google Workspace backup in every Compass plan. Those backups run daily and use seven-year standard retention. Desktop, server and BCDR backups are paid add-ons with one-year default retention. All of these backups are online and use third-party tooling. We verify that each backup we manage completes successfully, manage the backup alerts, and respond when they fire. We do not run restore tests. Disaster recovery planning is included.

Microsoft 365 availability is not the same as your recovery plan

Microsoft 365 includes native recovery and retention capabilities. Microsoft also offers a dedicated backup service for supported workloads. Understand which capabilities are enabled, what each is intended to do, and the recovery options you actually have. [1, 2]

Do not assume all native protection is inadequate, or that a service labeled "backup" covers everything. An accidental deletion, an overwritten file, a compromised account, and an application outage can require different responses.

What does seven-year retention mean?

Seven years is the default retention setting for the included Blue Tree Technology® backup service. It is not a claim that Microsoft sets all Microsoft 365 services to seven years.

Retention does not create copies from before backup coverage began. Nor should the setting be read as a promise that every version, every workload, or every historical moment is recoverable. Confirm the start of protection, the content in scope, available recovery points, and any documented changes to retention.

A retention period also does not establish how quickly the business can resume work. NIST distinguishes the recovery point objective, concerning the point in time to which data is recovered, from the recovery time objective. Long retention and fast restoration are different requirements. [3, 4]

Check coverage before an incident

Ask for an understandable view of what is protected and what remains outside the service. In particular, discuss the following rather than assuming coverage from a product name:

QuestionWhy it matters
Which accounts and content are in scope?Mailboxes, shared sites, individual files, and application-dependent content need explicit coverage checks.
How are new and departing users handled?Hiring, offboarding, licensing, and permission changes can affect protection or access.
What evidence shows backup is current?Failed jobs, authorization errors, gaps, and recent recovery points need an owner.
Who can authorize and perform recovery?A locked-out administrator or unavailable contact should not be an unplanned dependency.

At contract end: confirm access, export, continued retention, deletion, and any charges in the written terms. These questions do not imply that every workload or service arrangement is identical.

A completion check is not a restore test

A recovery test can answer a different question from a completion check: for example, whether a required file version opens for the authorized user, or whether a larger application recovery includes its dependencies. That kind of test is something a business may choose to discuss. It is not a Blue Tree Technology® service.

Blue Tree Technology® verifies that each backup it manages completes successfully, manages the backup alerts, and responds when they fire. It does not run restore tests.

A successful backup notification does not by itself demonstrate that restoration works. A successful small-file test does not establish how long a complete business recovery would take. Document what was tested, what succeeded, what was excluded, and who resolves remaining gaps.

If identities or devices may be compromised, coordinate restoration with the incident-response lead. Recovering data and removing an attacker are separate tasks.

Does retention satisfy compliance requirements?

Not automatically. Legal holds, records schedules, privacy obligations, search/export needs, and backup recovery have different purposes. Have the appropriate advisers determine the requirements for your information; do not treat a seven-year setting as proof that every compliance duty is met.

The included backup is a starting capability, not a substitute for a recovery discussion. Ask Blue Tree Technology® to show the configured coverage, retention, confirmation that backups completed successfully, and any exceptions relevant to your business.

Related reading: How Often Should Backups Be Tested, and How Fast Could You Recover?

Sources and further reading

[1] Microsoft: Microsoft 365 Backup overview

[2] Microsoft: Safeguarding your data in SharePoint

[3] NIST glossary: Recovery Point Objective

[4] NIST glossary: Recovery Time Objective

Back to the Knowledge Hub

More in this topic

Discuss your business technology needs

Review your priorities with Blue Tree Technology®.

Schedule a discovery call