If you manage Intune for more than one tenant, you already know the pain. A Settings Catalog policy that took an afternoon to get right in one tenant has to be rebuilt by hand in the next one. Someone changes a compliance policy and nobody notices until a device fails. A policy gets deleted and there is no way back.

Pckgr Policy Manager was built to take that pain away, and over the last few weeks we rebuilt large parts of it. The goal was simple. Make it safe and fast to copy, back up, restore, and watch Microsoft Intune policies across every tenant you manage. Here is what changed.

Cloning policies between tenants

Cloning has always been the most used part of Policy Manager, so it got the most attention. The old clone popup lived inside the row menu and did not tell you much. It is now a dedicated Clone Policy window that shows you exactly what will happen before you commit.

When you open it, you will see:

• The policy type in plain language. Settings Catalog, Device Configuration profile, Compliance policy, PowerShell script, or Administrative Template.
• A destination tenant picker. Every tenant connected to Pckgr is listed, and the one you are currently viewing is marked “(this tenant)”.
• A name field. You pick the name the copy gets in Intune. Clone into the same tenant and Pckgr adds ” – Copy” so you never end up with two identical names.
• An encrypted values warning. This one is important. Intune never hands back secrets like passwords or certificates in an export. They come back as ****. Pckgr now spots those settings, lists them by name, and tells you up front that you will need to re-enter them in Intune after the clone. No more silently broken copies.

On success you see which tenant the policy landed in and a confirmation that Pckgr is already syncing it. On failure the exact Intune error is shown in the window.

Clones run in the background

Clones are no longer tied to your browser tab. They run as a backend workflow, so you can close the window and the clone keeps going. Every result is written to Audit Logs.

Bulk clone

Every policy table now has a checkbox column and a select all control. Tick as many policies as you like, choose Clone, and the Bulk Clone window shows what is queued with a type badge for each one. Clones are spaced a few seconds apart so Intune is not flooded. My Templates got the same treatment.

Templates

Templates are how you keep a gold standard policy and stamp it out across tenants.

Save as Template now opens a proper window where you give the template a name and a description, instead of the policy name being reused silently. You can edit both later, and templates now have their own Clone button that opens the same Clone Policy window.

Deleting a template asks for confirmation and tells you how many policies in the selected company are linked to it. When you go ahead, Pckgr unlinks every linked policy in every tenant and clears their drift history, so you are never left with a policy pointing at a template that no longer exists.

Uploading a custom policy is easier too. Paste the JSON export and Pckgr detects the policy type and shows it as a badge, or tells you it was not recognised.

Policy Links and drift

The Policy Link feature has been cleaned up a lot. A Policy Link ties a live policy in a tenant to a template, and Pckgr checks for drift automatically during every sync.

The Policy Link window was redesigned around three questions. Is it linked? Is it in sync? What changed?

The What changed table replaces a raw text dump with a per-setting view. Each row shows the setting path as breadcrumbs, the template value, and the policy value. Intune’s internal prefixes are stripped so the values read the way they do in the Intune portal.

There was also a false positive bug to fix. Intune includes an @odata.context URL and a version counter in every payload, and both change without any real configuration change. Linked policies were showing drift for no reason. Both fields are now stripped before comparison, so when Pckgr says a policy has drifted, it has.

Note: Drift comparison does not yet cover Administrative Template settings, only the policy container. That is on the list.

Backups and restore

The Backups window is now a proper table. Each row shows the date, a note, and whether the backup was Automatic or Manual. Click a row, then restore or delete it. Creating a manual backup happens inline in the same window.

Two things changed under the surface that matter a lot:

• Administrative Template backups now include their settings. Previously a backup captured only the empty container, which is not much of a backup. Older backups taken before this change are clearly labelled so you know what a restore will give you.
• Restores sync immediately. After a restore, Pckgr triggers a sync for that policy type right away instead of waiting for the next scheduled run, so the recreated policy shows up in Pckgr straight after it shows up in Intune.

Pckgr also takes an automatic baseline backup the first time it captures an Administrative Template’s settings, so every template has something to restore from.

Deleting policies

The old Delete window removed the policy from Pckgr only, and it would quietly reappear on the next sync. That was confusing, so it has been reworked.

The window now tells you how many saved backups will be deleted with the policy, and offers an Also delete this policy in Intune checkbox with a clear warning that assigned devices stop receiving it and it cannot be recovered. Both successful and failed Intune deletes are logged to Audit Logs. The Delete action was also moved to the bottom of the row menu and coloured red, so it is harder to hit by accident.

Smaller things you will notice

• Sortable columns on every tab, with the active column highlighted.
• Result counts and helpful empty states that tell you what to do next, rather than a blank table.
• Tabs in the URL, so a refresh or a shared link lands on the same tab.
• Audit Logs can be searched by policy name, and sync-driven events are hidden by default so the log shows what people did. Tick Include automatic activity to see everything. Rows with no user show “Pckgr Automation”.
• Global Policy Settings has a description under each option (24-hour automatic sync, automatic backups during sync, 30-day cleanup of stale policies) and a plain sync status like “Next sync in 1 hour” or “Sync is overdue”.
• Dashboard gained a Backups Taken tile and clearer labels.

Try it out

If you already use Pckgr, open Policy Manager and have a look. Cloning a policy into a second tenant is a good place to start.

If you are not yet on Pckgr, you can start a free trial or book a demo and we will walk you through Policy Manager on your own tenants.