Microsoft 365 backup helps your business recover email and files when deletion, corruption or a security incident disrupts work. The right approach depends on what you need to recover, how far back you need to go and who will get your team working again.
This guide is for Australian business owners, operations managers and IT leaders comparing Microsoft 365 backup options. It explains coverage, costs and the questions to ask before choosing a solution. For help reviewing your environment, explore Stanfield IT’s Microsoft 365 consulting and support.
Product information and published pricing checked: 19 September 2026.
Does your business need Microsoft 365 backup?
Start by asking for evidence of what you can recover today. If important client files disappeared, could someone restore the right version, within an acceptable time, without rolling back healthy work?
Microsoft 365 includes resilience, version history, recycle bins and retention capabilities. These have different purposes and limits. Microsoft’s separate, paid Microsoft 365 Backup product adds backup and recovery functionality; it is not automatically enabled merely because you have Microsoft 365 licences. Microsoft explains the distinctions in its backup FAQ.
Our recommendation is to compare your existing recovery arrangements against actual business scenarios:
- An accidental deletion: a staff member removes a client folder and nobody notices immediately.
- A compromised account: an attacker changes or deletes information across shared locations.
- A departing employee: the business needs information from an account after its owner leaves.
- A major recovery: several teams need their email and documents restored together.
For each scenario, record the available history, the recovery process and the person responsible. A backup purchase should close an identified gap. Avoid paying for overlapping tools without knowing what each one contributes.
Which Microsoft 365 backup approach should you choose?
Make two decisions: which technology fits your recovery requirements, and who will operate it. Managed backup is a service that can use Microsoft’s platform or another product.
| Approach | What you are choosing | Questions to resolve |
|---|---|---|
| Microsoft 365 Backup | Microsoft’s paid backup product for supported Microsoft 365 workloads. | Does its scope, recovery history and restore workflow meet your requirements? |
| Third-party backup product | Another vendor’s product, with its own features, storage architecture and commercial terms. | Where is the copy stored? Which workloads and restore destinations are supported? What are the exclusions? |
| Managed backup service | A provider operates an agreed backup solution and recovery process. | Who checks coverage, handles failures, tests restores and responds when you need help? |
A third-party product does not necessarily store its backup outside Microsoft. Some partner applications use Microsoft 365 Backup Storage. Ask the supplier to describe the architecture and administration boundaries rather than assuming that another brand means an independent copy. Microsoft lists this partner model in its backup overview.
A business with capable internal IT may prefer to operate the platform itself. A business with limited internal capacity may place greater value on clear ownership, tested recovery and support. Compare both the technology and the operating arrangement.
What does Microsoft 365 Backup protect?
The native product protects supported Exchange Online mailboxes, SharePoint sites and OneDrive accounts included in backup policies. Do not treat the phrase “Microsoft 365 backup” as proof that every application and data type is covered.
| Business information | Native product scope | Your check |
|---|---|---|
| Supported Exchange Online user and shared mailboxes. | Include shared mailboxes such as accounts and enquiries in the scope. | |
| Shared documents | Supported SharePoint sites included in protection. | Check every important team and client site. |
| Individual work files | Protected OneDrive accounts. | Check joiner, leaver and account-change procedures. |
| Teams channel files | Files held in a protected SharePoint site. | Confirm the underlying site is protected. |
| Teams chats and other application data | Teams chats are outside this native product’s coverage; assess other applications separately. | Ask for an explicit list of included data types and gaps. |
Sources: Microsoft’s backup policy documentation and Microsoft’s product FAQ.
Request a coverage register listing the protected accounts, sites and information types. Review it when your business adds staff, creates new shared locations or changes applications. An old list of protected users is not evidence that the current environment is fully covered.
How far back can you recover, and how long will it take?
Microsoft’s current policy documentation allows recovery windows of three months, six months, one year or two years. Existing policies default to one year. Check the setting in your environment; a longer available option does not mean it is already configured. Removing an item from protection stops new backups, while retained copies remain subject to their recovery window and charges. See Microsoft’s recovery-window guidance.
Keep three measures separate:
- Recovery history: how far back a usable copy is available.
- Recovery point objective (RPO): how much recent work your business can afford to lose.
- Recovery time objective (RTO): how quickly the information must be usable again.
Microsoft documents both full SharePoint/OneDrive recovery and granular file or folder restores. Recovery-point frequency differs by workload, restore method and age of the data. A frequent backup interval is not a promise that every restore finishes within that interval. Full in-place site recovery can overwrite later changes, so the destination and scope matter. See Microsoft’s restore documentation.
For a useful test, choose information that staff actually rely on. Restore it, check that the right people can use it and record the elapsed time. Compare that result with the business requirement. Our guide to RTO and RPO explains how to set recovery objectives.
How much does Microsoft 365 backup cost?
Microsoft publishes a native-backup list price of US$0.15 per GB per month. These examples use billable protected data and exclude tax, currency conversion and separately quoted implementation or support.
| Billable protected data | Monthly calculation | Monthly storage cost |
|---|---|---|
| 500 GB | 500 × US$0.15 | US$75 |
| 1,000 GB | 1,000 × US$0.15 | US$150 |
| 5,000 GB | 5,000 × US$0.15 | US$750 |
Billable data can include retained deleted or versioned content and mailbox archives. It can exceed the currently visible files. These are illustrative calculations, not Stanfield IT quotes. Confirm current billing terms using Microsoft’s pricing model; its Australian product FAQ identifies the published currency as USD.
Microsoft does not charge separately for restores in its native product. Any provider labour or managed recovery fee should be stated separately in your proposal. See the Microsoft 365 Backup overview.
For an Australian-dollar proposal, ask for the storage or licence allowance, implementation, monitoring, restore testing, support hours, GST treatment and any additional recovery charges. Compare the same scope and term across suppliers.
Our budgeting recommendation is to separate the platform fee from the work needed to operate it. A low software price is difficult to assess without knowing who responds to failures, who performs restores and what happens as your data grows.
Eight questions to ask a Microsoft 365 backup provider
- What is protected? Request a written scope, including shared mailboxes, SharePoint, OneDrive and relevant Teams content.
- What is excluded? Identify applications, information types and account categories requiring a separate approach.
- Where are the copies stored? Confirm storage location, architecture, administration and access arrangements.
- How much history is available? Check the configured recovery window and how policy changes affect older copies.
- How will we recover? Ask about single-item and larger restores, recovery destinations and access during an incident.
- What has been tested? Request a dated example showing the scope, result, elapsed time and unresolved issues.
- Who is accountable? Agree who checks failures, updates coverage and authorises recovery, including after hours.
- What happens if we leave? Understand access, export options, retained-data charges and the handover process.
Give each answer an owner. Your internal team and provider should share a clear view of the boundary between included support and separately quoted work.
What should a growing business review first?
Consider an illustrative 40-person professional services firm. Important information may sit in client SharePoint sites, individual OneDrive accounts, shared finance mailboxes and Teams conversations. Counting 40 user licences does not describe that recovery scope.
We would start with a simple business exercise: identify the information needed to keep serving clients tomorrow, then ask the current provider to demonstrate recovery of representative items. Record any missing locations, unclear responsibilities and untested assumptions before requesting replacement-product quotes.
A sensible first review should produce:
- A list of critical information and its current protection.
- A prioritised gap list, with an owner for each action.
- Agreed recovery objectives and a practical test plan.
- A costed proposal covering both the platform and ongoing operation.
This is an example planning approach, not a client case study or a promise of a particular recovery time.
How Stanfield IT can help
Stanfield IT helps businesses in Sydney and the Northern Beaches review Microsoft 365 protection alongside their wider IT environment. Our backup and disaster recovery services can support the planning, implementation and ongoing management of an agreed recovery solution.
The starting conversation should establish your current product, protected information, data volumes, required history and recovery expectations. From there, we can help identify gaps and scope the work needed. Platform selection, testing frequency, support coverage and charges should be confirmed in your proposal.
Unsure what your business could recover today? Talk to Stanfield IT about your Microsoft 365 backup. Bring your current backup details and any recent restore-test results so we can discuss a practical next step.
Microsoft 365 backup FAQs
Is Microsoft 365 Backup included in our existing licences?
The separate Microsoft 365 Backup product uses pay-as-you-go billing. Check your current agreement: your IT provider may already supply another backup product or service. The Microsoft 365 subscription alone does not confirm that a backup policy is active.
Is Office 365 backup the same topic?
Businesses still use “Office 365 backup” when discussing protection for Microsoft-hosted email and files. Ask which product, workloads and recovery features the supplier means; the label alone does not establish coverage.
Can Microsoft 365 Backup restore individual files?
Yes. Current Microsoft documentation includes granular SharePoint and OneDrive file or folder restore, alongside broader recovery options. Confirm the available recovery points and destination for the information you need.
Does it back up everything in Microsoft Teams?
No. Channel files can be covered through protected SharePoint sites, but the native product does not protect Teams chats. Ask for a content-by-content coverage explanation before relying on a claim that “Teams is backed up”.
Should we use a third-party product?
Choose it where its verified coverage, architecture, history or recovery process better fits your requirements. Another vendor’s name does not automatically mean separate storage or broader protection. Compare the written scope and test the recovery workflow.
How often should our business test restores?
Agree a schedule based on the importance of the information and how often the environment changes. Include representative restores and retest after significant changes. Record the result, elapsed time and follow-up actions rather than relying only on backup completion reports.
Can Stanfield IT manage backup for us?
We can review your requirements and scope a suitable managed backup arrangement. The proposal should identify the product, included workloads, monitoring, recovery responsibilities, test schedule, support hours and fees.
