Follow the instructions below to add a new software policy.

Prerequisites

Required permissions: Owner, Super Admin, or IT Admin (L2 and above)
Supported platforms: Android, iOS, iPadOS, macOS, Windows, Ubuntu, tvOS
Time estimate: 5–10 minutes
Additional requirements: Devices enrolled via AutoPilot; software added in Software Management

Before You Start

Software policies help you enforce app-level restrictions across managed devices. You can create allowlists to specify approved apps or blocklists to restrict the use of unauthorized software. This ensures productivity, security, and compliance, especially on corporate-owned endpoints.

Misconfigured software policies may block essential tools or allow unvetted apps. Always double-check assignments and policy types before saving.

Before proceeding, please ensure that:

Your device fleet is properly enrolled
The required apps are available in the Software Management section
You have clear grouping via AutoPilot assignments

Step 1: Open Software Policy

Go to Fleet > Software Policy
Click + Add new in the top-right corner

Step 2: Configure Policy Details

Enter a Policy Name (e.g., "Marketing Android Apps")
Select the Policy type:
- ✅ Allowlist: Only selected apps will be allowed
- 🚫 Blocklist: Selected apps will be blocked
Choose a Platform from the dropdown (e.g., Android)
(Optional) Add a Description

If you see a disabled “Next” button: ensure all required fields are completed.

Step 3: Select Apps

Use the search bar or filters to locate apps by Name, Category, Publisher, or Source
Check the box next to each app you want to allow/block
Click Next

Troubleshooting:

Issue: Can’t find app → Solution: Confirm it's been added in Software Management
Common mistake: Selecting the wrong app version → Prevention: Verify version and publisher

Step 4: Assign to AutoPilot

Search and select one or more AutoPilot groups to assign this policy to
Review the Status and Type of each group (e.g., Published, Paused)
Click Save Software Policy

Expected result: A success message confirms that the new policy was created.

Next Steps

Immediately after creation:

Navigate to Software Policy to confirm that the policy appears in the table
Validate that it is assigned to the correct AutoPilot groups

Recommended follow-ups:

Test on a sample device
Monitor app behavior via Activity Logs
Adjust the policy if unintended app blocks occur

Advanced Options

Kiosk Mode Integration:

Combine with Kiosk Mode for fully locked-down devices

Mixed Platform Enforcement:

Create separate allow/block lists per OS (e.g., Android vs. macOS)

Policy Prioritization:

If multiple policies are assigned to a device, allowlists override blocklists

Troubleshooting

Apps not applying to the device:

Symptoms: Apps are still accessible despite the policy
Cause: Policy not yet synced or assigned, AutoPilot inactive
Solution: Ensure AutoPilot is Published, and the device is in the assigned group

Policy not saving: