Import Intune policies

Identify the file before choosing an importer

A native Windows Settings Catalog export represents selected policy configuration. Use the matching native import workflow for that format. A TenuVault ZIP holds a dated set of saved objects, metadata and a source-tenant manifest. Importing that archive makes a backup available locally; a separate restore operation writes policies.

Do not rename a JSON file, combine unrelated exports or create a manifest by hand and expect a backup importer to understand it. Files with similar-looking settings can still belong to different policy types. Keep the original export and its source information while deciding how it should enter the destination tenant.

Use the native route for a native export

For Windows Settings Catalog JSON, follow the import procedure documented for Settings Catalog in the Intune admin center. Inspect the created policy before assigning it. Keep a record of which tenant supplied the export so that a familiar policy name does not substitute for checking the actual settings.

A successful native import is not proof that the same file can populate scripts, enrollment profiles or other policy types. If you have several formats, handle them with their corresponding workflows. TenuVault's restore wizard is for saved backup objects and does not convert arbitrary exports into its backup format.

• Microsoft: Settings Catalog JSON import
• Export Intune configuration before a change

Import a TenuVault backup ZIP locally

Open Settings, then Storage and recovery. In Backups on this device, choose Import backup ZIP and select the archive. TenuVault checks it before showing Review backup archive. Read the policy snapshot count, source tenant ID, backup ID and SHA-256 hash, then choose Import locally.

The import stores the backup on this device and never changes Intune. To see and restore it, the source tenant must use This device as its selected storage location. Open Backup & Restore afterwards and find the imported backup. Changing the tenant's storage selection does not move older backups from another location.

• Use an archive from a source you trust; the source-tenant declaration is not a signature.
• Check that you selected the intended source tenant before attempting a restore.
• Keep the archive unchanged so its inventory still matches its saved files.

Understand the checks that can refuse an archive

The archive must be smaller than 32 MiB and contain the TenuVault manifest with its source tenant. It must describe a complete backup that finished without warnings, and every file must match the recorded inventory. Missing, changed or extra files cause refusal. The same backup cannot already be present on this device.

Your license must cover the source tenant. An archive that records another tenant is not a way around tenant licensing or cross-tenant restore requirements. If validation fails, obtain an intact export or use the original stored backup. Editing files to make the check pass would remove the evidence that the saved version is complete.

An incomplete stored backup may still contain individual snapshots the restore wizard can use, but the ZIP import has stricter completeness requirements. Keep these two cases separate when investigating a failed import; the fact that a backup appears in history does not guarantee its exported archive qualifies for re-import.

Review the restore separately

In Backup & Restore, choose Restore from this backup or open the Restore tab. Select the items, choose the method and read Review before confirming. Community restores one item at a time as an unassigned copy. Pro and MSP add multi-item restore, replacement in place and assignment restore.

Cross-tenant copying requires MSP for the participating tenants and produces unassigned copies. It does not turn an archive into a device migration. Where a restore needs an installer, a missing dependency or a target-specific reference reconciled, complete that work before assigning the restored configuration.

• Review an Intune restore plan
• Copy a standard set between tenants

Check the result before wider use

After restoring, inspect the resulting policy in Intune and compare it with the saved snapshot. A recreated object has a new identity even if the display name is familiar. Confirm its settings, intended assignments and any external artifacts rather than judging success from the name alone.

• Keep an untouched copy of the imported archive and record the restore result.
• Pilot restored configuration before assigning it more broadly.
• Retain the previous destination backup until the restored policy has been checked.