Track whether your policies have been successfully deployed to devices using the Policy Status column — available in both the Device Details and Policy Details views.
Overview
Policy Deployment Reporting lets you monitor the installation status of policies across your device fleet at a glance. For each device-policy pair, you can see:
Whether the device is running the latest version of the policy
Whether a policy update is still pending
The specific version installed versus the latest version available
This helps you quickly identify devices that haven't received the latest policy configuration and take action accordingly.
Where to Find Policy Status
Policy deployment status is visible in two places:
Device Details → Policies tab
Navigate to Inventory → Devices, select a device, then open the Policies tab. Each assigned policy shows its deployment status and version information.
Policy Details → Devices tab
Navigate to Policies, select a policy, then open the Devices tab. Each assigned device shows its deployment status for that policy.
Both views display the same data — if a device-policy pair shows "Pending" on one page, it will also show "Pending" on the other.
Reading the Policy Status Column
The Policy Status column displays a status badge with the version number shown below it as supporting detail.
Status Values
Status | Meaning | Version Example |
Up to date | The device is running the latest version of the policy. |
|
Pending | A newer policy version is available, but the device has not installed it yet. |
|
Pending | The policy has been assigned but has never been installed on the device. |
|
Version Format
The version is displayed as:
[device policy version] / [latest policy version]
Left side — the version currently installed on the device
Right side — the latest available version of the policy
Dash (–) — indicates no version has ever been installed on this device
Examples:
3 / 3→ The device has the latest version. Status: Up to date2 / 3→ The device is one version behind. Status: Pending– / 1→ The policy was assigned but never installed. Status: Pending
Policy Status vs. Compliance Status
These are two different indicators:
Compliance Status reflects whether the device meets the compliance rules defined in the policy (e.g., disk encryption enabled, OS version requirement met).
Policy Status reflects whether the latest policy configuration has been delivered to the device.
A device can be compliant even if its policy status shows Pending — this means the device still satisfies the rules from the older policy version, but hasn't received the latest configuration update yet.
How Policy Deployment Works
When you create or update a policy, the policy version increments.
The updated policy is pushed to all assigned devices via MDM.
Once the device confirms successful installation, its status updates to Up to date.
Until that confirmation is received, the device shows Pending.
Note: A policy appearing under a device's Policies tab means the "assign policy" action was initiated. The MDM must send a callback to confirm whether the policy was successfully installed — this is what the Policy Status field reflects.
Troubleshooting
Symptom | Possible Cause | Resolution |
Status shows Pending for an extended period | Device may be offline or unreachable by MDM | Verify the device is powered on and connected to the internet |
Version shows | Policy was recently assigned but hasn't been installed yet | Allow time for MDM to deliver the policy; check device connectivity |
All policies show Pending on a device | Device may have recently enrolled or reconnected | Wait for the MDM sync cycle to complete |
Device is compliant but policies show Pending | Compliance is evaluated separately from deployment | This is expected — compliance checks older policy rules until the new version is installed |
FAQ
Q: A policy shows "Pending" but my device is compliant. Is something wrong?
No. Compliance status evaluates the device against the policy rules it currently has installed. If a newer policy version exists but hasn't been delivered yet, the device can still be compliant with the previous version's rules.
Q: How long should I wait before a policy status changes from Pending to Up to date?
This depends on the MDM sync interval and device connectivity. Most devices should update within a few minutes of being online. If a device remains Pending for more than 24 hours, check that it is online and reachable.
Q: Can I filter or search by policy status?
Yes. Both the Device Details → Policies tab and Policy Details → Devices tab support filtering and searching, including by status values.
Q: What does a dash (–) mean in the version field?
A dash indicates that no version of the policy has ever been installed on the device. The policy has been assigned but the device has not yet received it.
For the changelog, visit feedback.swif.ai/changelog/policy-deployment-reporting.