Service

Microsoft 365 backup

Microsoft is not your backup. We make independent copies of mail, OneDrive, SharePoint and Teams, so after deletion, an attack or a mistake the data can be recovered at any time.

  • ISO/IEC 27001
  • 3000+ workstations
  • Since 2017

Many business owners assume that because mail and files are in the Microsoft cloud, they are safe forever. That is a dangerous misunderstanding. Microsoft is responsible for the availability of the service, not for recovering data that someone deleted or encrypted. That backup is on us.

What the Microsoft 365 backup covers

An independent copy of the whole environment, from which you can recover a single email or the mailbox of a departing employee.

  • Exchange mail copy

    A daily copy of mailboxes. You recover a deleted message or a whole mailbox, even long after it was removed.

  • OneDrive and SharePoint

    Full copies of files and team sites. An overwritten document or a deleted folder come back without asking Microsoft for help.

  • Teams data

    Conversations, files and Teams channels covered by the copy. Team knowledge does not vanish with a deleted team or account.

  • Fast recovery

    We restore a single item or a whole account. You do not have to restore everything to recover one file.

  • Copy outside Microsoft

    Data kept independently of the Microsoft cloud. A failed or blocked account does not cut you off from the copy.

  • 3-2-1 rule to zones outside Microsoft

    We replicate copies to independent zones, including object storage (blob) outside the Microsoft ecosystem. Three copies, two zones, at least one away from the original.

  • Immutable copies

    We keep backups immutable (WORM), with their own retention. Ransomware or a deleted account neither removes the copy nor overwrites it.

Why Microsoft is not your backup

The agreement with Microsoft is based on a shared responsibility model. Microsoft guarantees that the service works and that the infrastructure is sound. Responsibility for the data in that service lies with the customer. If an employee deletes files, ransomware encrypts OneDrive, or a former colleague wipes a mailbox before leaving, that is not a Microsoft failure but your problem to solve.

The trash and version history give only a few dozen days, after which the data disappears for good. A deleted employee account takes their mail and files with it. An independent backup removes this risk: the copy lives separately, with its own retention period, and lets you recover data even months later, regardless of what happened to the account in Microsoft 365.

The 3-2-1 rule and copies managed in blob storage

Keeping the only copy in the same ecosystem you are protecting is a single point of failure. That is why we apply the 3-2-1 rule: at least three copies of the data, on two independent media or in two zones, and at least one copy outside the Microsoft ecosystem. We manage the copies at the object storage level, that is in blobs, split across zones and cost tiers, so protection is tight and the cost stays reasonable.

Immutability is key. We keep copies unmodifiable, in WORM mode, with their own retention period, so neither ransomware nor a deleted account can remove or overwrite the backup. Replication to zones outside Microsoft means that an account lock, a provider side incident or a region outage does not cut you off from the data. It is a backup that survives even the scenario where Microsoft 365 itself is temporarily unavailable.

How we protect data

We start the copies within a few days and immediately verify that recovery actually works.

  • dailyautomatic data copy
  • a few daysservice launch
  • 3-2-1copies in zones outside Microsoft
  • immutablecopies resistant to deletion
  1. Choosing the copy scope. We agree what we cover: mail, files, Teams, and how long we keep the data. The scope is matched to needs and requirements.
  2. Launch and first copy. We connect the backup to Microsoft 365 and run the first full copies. Without interfering with the team day to day work.
  3. Recovery test. We check a trial restore of data before it is needed for real. A backup without a test is only an assumption.
  4. Monitoring and restoring. We watch whether the copies run and recover data at your request. A failed backup is an alert, not silence.

Model rozliczeń

We bill the Microsoft 365 backup as a fee depending on the number of protected accounts. The cost is fixed and predictable, and data recovery is not charged extra.

Included

  • Daily copies of mail, files and Teams
  • 3-2-1 copies in zones outside Microsoft
  • Immutable copies (WORM) with their own retention
  • Monitoring of backup completion
  • Data recovery on request
  • Backup status report

Beyond the plan

  • Extended copy retention period
  • Backup of additional services and large volumes
  • Data migration to another environment

We propose the same copy model for Google Workspace if the company uses both environments.

Frequently asked questions

If the data is in the Microsoft cloud, why a separate backup?

Microsoft guarantees the service works, but responsibility for the data lies with the customer. Deleted files, OneDrive encrypted by ransomware or a mailbox wiped after an employee leaves are not a Microsoft failure but your problem. The trash and version history keep data only a few dozen days. An independent backup removes that limit.

What exactly does the copy cover?

Exchange mail, files in OneDrive, SharePoint sites and conversations and files in Teams. You can restore a single email, one document or a whole account, without having to restore the entire environment at once.

Will I recover data after an employee account is deleted?

Yes. This is one of the more common reasons companies deploy this backup. The copy lives independently of accounts in Microsoft 365, so a former employee mail and files stay available for recovery even after their account is deleted.

How quickly can data be recovered?

A single item, such as a message or document, we usually restore within about fifteen minutes of the request. Restoring a larger scope depends on its size, but we always work on verified, tested copies.

Where do the copies go, and are they outside Microsoft?

We apply the 3-2-1 rule: at least three copies, in two independent zones, and at least one outside the Microsoft ecosystem. We manage the copies in object storage (blobs) as immutable (WORM), with their own retention. So an account lock, a ransomware attack or a region outage does not cut you off from the data, and we can keep the copies within the European Union if needed.

See what peace of mind with IT costs

Answer 2 questions about your company. You will see a simple estimate right away, and we will prepare a full proposal within 24 business hours.

  • 2 minutes, no commitment
  • You talk to an engineer, not a salesperson
  • No spam, one contact about your quote