Configuration Backup & Restore

Know exactly how your tenant was configured, on any date

Conditional Access, Intune, Exchange and Purview policies have no version history in Microsoft 365. One mistaken change, a compromised administrator account or a script run against the wrong tenant can undo years of hardening, and nothing records what it was before. T365 keeps that record, item by item, and lets you put it back.

Configuration backup — captured, versioned, compared, restored
Scheduled · 02:00 (default)
1Capture every item
  • Entra ID412
  • Intune638
  • Exchange291
  • Purview143
  • SharePoint104
  • Defender96
  • Teams87
  • Power Platform71
Items captured1,842

Each policy, setting and object is its own item, from 200+ supported types.

2Keep every version

Conditional Access policy

Require MFA for admins

  1. v14Today 02:00
  2. v133 Nov 02:00
  3. v1218 Oct 02:00
Encrypted at restHash recordedReadable JSON
3Compare and spot change
Production ⇄ Test tenant2 differences
state
enabled → disabled
includeRoles
2 roles → 1 role
grantControls
mfa · unchanged

Compare two tenants, or one tenant on two dates.

4Preview, then restore
Dry run — 2 changes previewed, nothing written

Restore target

ProductionTest tenant

Restore into the same tenant, or copy to another tenant you manage.

The target tenant must grant restore consent first.

Restore is available for selected types, including Conditional Access, named locations, authentication methods and strengths, administrative units, app registrations and Intune policies. Every other type is kept for compare, drift and evidence.

Illustrative — sample data

What you get

Why teams choose Configuration Backup & Restore

01

Undo a bad change

When a policy is changed, deleted or overwritten, see what it was before and put it back, after previewing exactly what the restore will change.

02

Rebuild after an incident

If an administrator account is compromised or a script runs against the wrong tenant, you have a dated, item-by-item record of the configuration to recover from.

03

Show auditors what was in place

Encrypted, hashed versions of each policy give a dated record of how the tenant was configured, for an audit, an incident review or a change board.

04

Find drift before it matters

Scheduled scans compare configuration with your chosen baseline and report what has moved, so hardening that has quietly slipped is found and fixed.

05

Promote tested configuration

Compare a test tenant with production, then copy the supported policy types across once they have been checked.

How it works

From connection to evidence

  1. 1

    Connect a tenant

    An administrator grants T365 consent to read the tenant through Microsoft Graph and PowerShell.

  2. 2

    Set a schedule

    Backups run on the schedule you set for each tenant, or on demand.

  3. 3

    Capture and encrypt

    Each policy, setting and object is stored as its own encrypted, hashed item with version history.

  4. 4

    Compare and review

    Compare backups between dates or tenants, and review drift against your baseline.

  5. 5

    Preview, then restore

    Run a dry run to see the changes, then restore supported types to the same tenant or another.

In detail

How Configuration Backup & Restore works

Capture: every item, not a summary

T365 reads tenant configuration through Microsoft Graph and PowerShell, across more than 200 Microsoft 365 configuration types. Each policy, rule, setting and object is stored as its own item, so a backup of a tenant is thousands of individual records rather than one export file.

Backups run on a schedule you set for each tenant, or on demand. What is captured depends on the tenant’s licences and the permissions granted to T365, and every run reports what it read and stored.

Store: encrypted, hashed and readable

Every item is encrypted at rest with AES-256-GCM, with keys held in Azure Key Vault, and a hash of its content is recorded when it is written so later alteration can be detected.

Items are kept as structured JSON. An administrator can open any policy as it was captured and read it, rather than downloading and unpacking an archive.

Detect change: version history and drift

Each item keeps its version history. T365 shows which properties changed between versions, so you can see that a Conditional Access policy was switched from enabled to disabled, when it happened, and what it looked like before.

Configuration can also be measured against a baseline for the Essential Eight, the ASD Blueprint, the ISM, the PSPF or your own standard, with drift reported at each scheduled scan.

Configuration driftIllustrative — sample data

Property Differences2 differences

PropertyExpectedActual
stateenableddisabled
includeRoles[Global Administrator, Security Administrator][Global Administrator]

Compare: dates and environments

Compare any two backups in your organisation. Put one tenant’s configuration today beside last month’s, or put production beside test or a second agency tenant, and see every item that is added, removed or different, down to the property.

Restore: preview first, then the same tenant or another

Every restore can run as a dry run first, showing the changes it would make without writing anything. When it runs for real, you choose the target: the tenant the backup came from, or another tenant your organisation manages, for example to promote a tested configuration from a test tenant to production or to rebuild a tenant after an incident.

A target tenant must grant T365 restore consent before anything is written to it. Restore is available today for selected types, including Conditional Access policies, named locations, authentication methods and strengths, administrative units, app registrations and Intune compliance, configuration, settings catalog and Autopilot policies. Every other type is kept for compare, drift and evidence, and further types are added as each restore is tested.

Who it is for

Built for the people accountable for it

CISOs and security teams

A dated, tamper-evident record of how identity, device and data protection policies were set, and how they changed.

Microsoft 365 administrators

A way back from a mistaken change, with a dry run before anything is written.

Managed service providers

Compare the tenants you manage side by side, and copy tested configuration from one to another.

Audit and risk teams

Version history and baseline drift reports to support audits and incident reviews.

Frameworks

The frameworks it helps you evidence

Australian Signals Directorate

Essential Eight

Scheduled backups of tenant settings relate to the regular backups strategy, which covers settings as well as data. The captured configuration is also what T365 reads when it measures Essential Eight posture.

Read the source (opens Australian Signals Directorate in a new tab)

Australian Signals Directorate

Blueprint for Secure Cloud

Configuration can be measured against a Blueprint for Secure Cloud baseline, with drift from it reported at each scheduled scan.

Read the source (opens Australian Signals Directorate in a new tab)

Australian Signals Directorate

Information Security Manual (ISM)

Baseline rules can reference the Information Security Manual controls they relate to, so drift on a setting is reported alongside that control.

Read the source (opens Australian Signals Directorate in a new tab)

Attorney-General’s Department

Protective Security Policy Framework (PSPF)

A PSPF baseline can be measured in the same way, giving a dated record of how the configuration compared with it.

Read the source (opens Attorney-General’s Department in a new tab)

T365 measures, maps and records evidence against these frameworks. Your organisation remains responsible for its own assessment and authorisation decisions.

Questions

What buyers ask us

What does configuration backup cover?

More than 200 Microsoft 365 configuration types, across Entra ID, Intune, Exchange, SharePoint, Teams, Purview, Defender, Power Platform, Power BI and more. It backs up policies and settings, not mail or files; those are covered by Data Backup & Recovery.

What can be restored?

Restore is available for selected types: Conditional Access policies, named locations, authentication methods and strengths, administrative units, app registrations and Intune compliance, configuration, settings catalog and Autopilot policies. Every other type is kept as a record for version history, compare, drift and evidence.

Can I restore to another tenant?

Yes, for the supported types. The target must be a tenant your organisation manages in T365, and it must grant T365 restore consent before anything is written. A dry run shows the changes first.

Where is backed-up configuration stored?

The T365 SaaS service runs in Azure Australia East. Each item is encrypted at rest with AES-256-GCM, with keys held in Azure Key Vault, and a content hash is recorded so later alteration can be detected.

How long are backups kept?

Retention is set for each workload. The newest backups of each workload are kept whatever their age, a legal hold on the tenant suspends deletion, and a retention lock can set a minimum period.

Does it need AI?

No. Backup, compare, drift and restore work without AI. AI features in T365 are optional and off by default.

Evidence: where each claim on this page comes from
  • Supported configuration types

    packages/config/src/backup-types.ts

  • Restore scope: selected types only, every other type record-only

    packages/config/src/restore-tiers.ts

  • Items encrypted at rest with AES-256-GCM under Key Vault custody

    packages/crypto/src/providers/azure.ts

  • Content hash recorded for each item

    packages/db/src/schema/backup-items.ts

  • Version history with property-level change summaries

    apps/web/app/api/configs/[configType]/[configId]/history/route.ts

  • Compare any two backups in the organisation

    apps/web/app/api/backups/compare/route.ts

  • Dry-run and cross-tenant restore with target consent check

    apps/web/app/api/restore/route.ts

  • Retention set per workload, legal holds and a kept minimum of recent backups

    packages/db/src/services/backup-retention.ts

  • Baselines for the Essential Eight, ASD Blueprint, ISM, PSPF or a custom standard

    apps/web/src/lib/compliance/rule-validation.ts

  • Essential Eight evaluators read the captured configuration

    apps/web/src/lib/compliance/e8-backup-items-helper.ts

Buying for government? We are on the DTA Digital Marketplace.

  • Software
  • Cloud
  • Professional services
  • Labour hire
  • Hardware
How to buy

Ready to Secure Your Microsoft 365?

Start your free 14-day trial or talk to our team about your needs.