365 Backup · Microsoft Intune

A deleted policydoes not come backin Intune.

For deleted or altered policies, Intune offers no recycle bin and no earlier versions. Anyone rebuilding them works from memory. Conbool backs up the Intune configuration on a schedule, shows every state in readable form and restores policies as a new policy, only with approval from a second person.

Why Intune belongs in the backup

Four cases that cost days without a backup.

One click too many in the admin center

A compliance policy or a configuration profile is quickly deleted. After that it is gone, along with all the settings that grew over the years.

Changed, but what was it before?

Changing a setting in the settings catalog overwrites the old value. If devices then stop being compliant, there is nothing to compare against.

Hundreds of settings by hand

A baseline for Windows devices quickly reaches several hundred settings. Rebuilding it from screenshots and memory takes days and stays uncertain.

The tools are scripts

Microsoft provides no backup tool of its own for Intune. The usual route is community scripts that someone has to maintain, run and check.

Intune change planagainst today
2missing
5changed
11additional
Windows compliance standardmissing
Settings catalog Edgechanged

The figures are an example. Nothing is deleted: policies that exist only today stay in place.

Next to the current one, never over it

Back as a new policy.

The plan shows which policy is missing and which settings differ. Restoring creates a new policy, without assignments by default.

Current policies are never changed

Assignments only if explicitly chosen

Approval by a second person

Secret values are named, not invented

How the Intune backup works

Part of the directory backup, one unit per Microsoft tenant.

1. Back up

Every run reads compliance policies, device configuration profiles, the settings catalog, endpoint security, administrative templates, Autopilot profiles, enrollment settings, app protection and app configuration policies, platform scripts and remediation scripts, and the managed devices.

2. Compare

A change plan shows against today's state, in plain text, which policy is missing and which settings differ.

3. Restore

Selected policies come back as a new policy, after approval by a second person. A current policy is never changed.

What defines the Intune backup

Six points that make the difference.

What comes back

Compliance policies (old and new), device configuration, settings catalog, enrollment settings, Autopilot profiles, app protection for iOS and Android, app configuration, and platform, shell and remediation scripts. Endpoint security and administrative templates are backed up and readable, but not written back.

Always as a new policy

The backed up policy is placed next to the current one. If the name is taken, it is called “Name (restored)”. That way both states can be compared directly.

Without assignments by default

A restored policy initially applies to no device. The backed up assignments are included only if you explicitly choose that.

Never to more devices than before

If an excluded group is missing today, the whole assignment is left out. Without that exclusion, the policy would apply to more devices than were backed up. Assignments to all devices or all users are highlighted in the approval.

Four eyes, dedicated application

Writing happens only through the dedicated application “Conbool 365 Backup Directory Admin” and only with approval from a second person for exactly this selection.

Honest about secret values

Microsoft does not release passwords, pre-shared keys and encrypted OMA-URI values. A policy with such values is not half created but listed in the result.

With and without a separate backup

What is possible in each case.

 
With Conbool
Microsoft Intune without an add-on service
Restore a deleted policy
yes, as a new policy
no, only a rebuild
Read an earlier state of a policy
yes
no
Differences from today's state as a list
yes
not by default
Scheduled backup without your own scripts
yes
no
Approval by a second person before writing
yes
via multi admin approval for certain actions

Statements about Intune follow the publicly documented features. The audit log shows who deleted a policy but does not restore it.

Frequently asked questions

What is backed up from Intune?
Compliance policies, device configuration profiles, the settings catalog, endpoint security, administrative templates, Autopilot profiles, enrollment settings, app protection and app configuration policies, platform, shell and remediation scripts, and the list of managed devices.
Is an existing policy overwritten?
No. Restoring always creates a new policy. If the name is taken, the new one gets the suffix “(restored)”. You decide which one stays active.
What happens to the assignments?
The default is a policy without assignments. If you select the backed up assignments, an included group that is missing today is dropped. If an excluded group is missing, the whole assignment is left out so that the policy never applies to more devices than before.
What about passwords in profiles?
Microsoft does not release secret values such as Wi-Fi passwords, pre-shared keys or encrypted OMA-URI values. Such policies are not created without these values but listed in the result so someone can add them by hand.
Who approves a restore?
A second person from your account. Writing happens through a dedicated admin application with write permissions, which you consent to separately from the backup. Without that consent, the backup stays read-only.
Does Intune use an additional seat?
No. Intune is part of the directory backup and runs as one unit per Microsoft tenant, without its own license seat.

See your own Intune configuration backed up

We connect a test tenant and show a policy compared between the backed up state and today's state.