Our Thinking / Field Notes / The Guide

STEP-BY-STEP GUIDANCE / MICROSOFT INTUNE

Intune production pilot checklist: what to verify and document

A pilot acceptance checklist for Intune-managed Windows devices: what to verify, what evidence to keep, a read-only PowerShell report, a policy register, rollback and a handover record.

Start here

A pilot is ready for real users when you can show five things: who is in it and that each person has a licensed, recently synced device; what every policy, app and script does and who it is assigned to; evidence that each one applied correctly; a rehearsed way back for every change; and at least two tested emergency admin accounts. Keep that evidence in a policy register, a read-only device and policy report and a handover record. Passing this earns a small supervised pilot. It is not approval to roll out to the whole organisation.

What pilot-ready means and what you need first

A pilot is ready when someone else could pick up your notes and answer five questions without ringing you: who is in it, what each policy does to them, how you know it is working, how to undo each change and who to call when it is not. This checklist turns a working Intune lab into that evidence. Passing it earns a small, supervised pilot. Production approval is a separate decision for whoever owns the risk, made after the pilot has run.

Microsoft's planning guidance says pilot users should know they are going first, be willing to give feedback and should not be executives or VIPs. Its rollout tables use 50 and 200 users as illustrations, not as a target. For a small organisation we would size the pilot by coverage instead: at least one person for each role, device model and working pattern you intend to support, plus someone from whoever answers the phone when things break.

  • Access: an account that can read Intune and Microsoft Entra data. A read-only Intune role is enough for the report in this article. Keep the privileged Intune Administrator role for the moments you actually change something.
  • Licences: every pilot user needs an Intune licence, because Microsoft requires one for any user or device that benefits from the service. Conditional Access and dynamic groups also need Microsoft Entra ID P1 or P2. Confirm the tenant under Tenant administration > Tenant status in the Microsoft Intune admin centre, then check the licence actually assigned to each pilot user.
  • Recent licence changes: Microsoft states that from July 2026 Microsoft 365 E3 includes Intune Plan 2, Remote Help and Advanced Analytics, and E5 and E7 add Endpoint Privilege Management, Microsoft Cloud PKI and Enterprise Application Management. Other plans can buy Suite separately. Use that as a reason to check what your tenant shows, not as an assumption.
  • Remediations: these script packages need a qualifying Windows licence for the device users, namely Windows Enterprise E3 or E5, Windows Education A3 or A5, or Windows VDA per user. If your plan is not on that list, leave Remediations out of the pilot.
  • A pilot group in Microsoft Entra ID with named members, and a written list of the pilot devices.

Check the people, devices and enrolment

Every later check is only meaningful if you know exactly who should receive what, so start here.

  • Each pilot user has an Intune licence and one pilot device that shows as enrolled to them with company ownership. In the admin centre, look under Devices > By platform > Windows.
  • Each device has checked in recently. A laptop that enrolled and then sat in a bag proves nothing. Newly enrolled Windows devices sync every 3 minutes for the first 15 minutes, then every 15 minutes for 2 hours, then roughly every 8 hours, so a device that has gone quiet will start to look stale quickly.
  • Assignments go to the pilot groups only. Look at every policy, app and script for All users or All devices targets. The report later in this article flags them for you.
  • If you target dynamic device groups, note that Microsoft says apps and policies assigned to them are not delivered until group membership has been processed after enrolment. User groups or assignment filters avoid that delay.
  • The enrolment route a pilot user follows is written down, whether self-service or helped by IT, along with who they contact if it fails. Microsoft suggests involving the help desk early. Making them pilot users is a cheap way to do it.
  • Personal phones are optional. If you include app protection for personal devices, give them their own group and their own line in the register, because they follow different rules from enrolled PCs.

Verify configuration, apps, security, compliance and updates

For each area, ask four questions: what does it do, who gets it, how did you see it arrive and what happens if it fails? 'The policy is assigned' answers only the second one.

  • Configuration: each settings catalog policy has a stated purpose, an owner and a pilot-only assignment. Intune has no policy hierarchy, so two policies that set the same setting differently show as a conflict that you must resolve by hand. Check the per-policy device status for Succeeded and zero Conflict results before you call it done.
  • Apps: each required app installs on a clean pilot device, its detection rule reports it as installed and the removal route has been tried on a spare test device.
  • Security: the report below shows whether each device reports as encrypted. Record that recovery key escrow was verified, but never paste recovery keys into the evidence pack.
  • Compliance, part one: compare what each policy says with what the device reports. A compliant tick on a policy you cannot explain is not evidence.
  • Compliance, part two: the tenant-wide setting 'Mark devices with no compliance policy assigned as' defaults to Compliant. If you use Conditional Access with device compliance, Microsoft advises changing it to Not compliant, but only once every pilot device has a compliance policy, or you will lock out the people you are trying to help. You find it under Endpoint security > Device compliance > Compliance policy settings.
  • Compliance, part three: the compliance status validity period defaults to 30 days. A pilot laptop that is off for a month will turn noncompliant simply because it has not reported.
  • Conditional Access: run each new policy in report-only mode first and read the results in the Conditional Access and Report-only tabs of the Microsoft Entra sign-in log details. Microsoft warns that report-only policies requiring a compliant device can still prompt users on macOS, iOS and Android to pick a device certificate, so exclude those platforms from such policies. Move the pilot group to enforcement only when the report-only results match what you expected.
  • Updates: the update ring targets the pilot group only and you have written down how to pause it. Judging update behaviour on one afternoon is optimistic. Our advice is to run the pilot through at least one full monthly update cycle before you form a view.
  • Scripts and Remediations: scripts are UTF-8 encoded with no passwords or personal data and no reboot commands. A remediation runs only when its detection script exits with code 1, so check the detection logic first. Unassigning a remediation stops future runs but does not undo what it already changed.

Keep a policy register

Intune will tell you what exists. It will not tell you why. A policy register is a simple table with one row for every policy, app, script and access rule in the pilot. It combines the facts from the report in the next section with the judgement only your team can add: purpose, owner and the way back. A spreadsheet is fine, provided people actually update it.

The two rows below show the level of detail to aim for. Save the header and rows as a CSV file and replace the example values with your own.

text
Name,Type,Purpose,Assigned to,Excluded,Owner,Last reviewed,Rollback action,Evidence location
EXAMPLE Pilot device settings,Settings catalog policy,Apply the agreed lock screen and firewall settings,Pilot-Windows-Devices,Admin-Test-Devices,YOUR_TECHNICAL_OWNER,YYYY-MM-DD,Unassign from the pilot group then sync a test device and confirm each setting has returned,YOUR_EVIDENCE_FOLDER
EXAMPLE Pilot compliant device check,Conditional Access policy (report-only),See what requiring a compliant device would block before enforcing it,Pilot-Users,Emergency-Access-Accounts,YOUR_ACCESS_OWNER,YYYY-MM-DD,Set the policy state to Off and confirm sign-in for an emergency account,YOUR_EVIDENCE_FOLDER

Produce the evidence with a read-only PowerShell report

Screenshots go stale and nobody wants to take fifty of them. This script reads device and policy data from Microsoft Graph and writes it to CSV files, giving you dated evidence you can repeat weekly. It changes nothing in your tenant. On your workstation it installs one module for your user account and creates a folder called IntunePilotEvidence in your profile.

It needs two delegated read-only permissions, DeviceManagementManagedDevices.Read.All and DeviceManagementConfiguration.Read.All. The first sign-in may ask for administrator consent, and if your account cannot grant it, someone with a suitable role will need to. The output contains device names and user principal names, which are personal data, so restrict the folder, keep it to pilot users and delete superseded copies.

The device and compliance policy calls use the v1.0 Graph endpoints. The settings catalog list is documented only for the beta endpoint at the time of writing, and Microsoft says beta APIs change more often. If that part fails, export the same list from the portal instead.

  1. Open PowerShell on your admin workstation and install the module that handles sign-in and Graph requests. This may take a minute or two.
    powershell
    Install-Module Microsoft.Graph.Authentication -Scope CurrentUser
  2. Replace the two example addresses with your pilot users' real addresses, then sign in and define a small helper that follows Graph's paging links so you receive every record, not just the first page.
    powershell
    $pilotUsers = @('pilot.user01@YOUR_DOMAIN', 'pilot.user02@YOUR_DOMAIN')
    $outDir = Join-Path $HOME 'IntunePilotEvidence'
    New-Item -ItemType Directory -Path $outDir -Force | Out-Null
    
    Connect-MgGraph -Scopes 'DeviceManagementManagedDevices.Read.All', 'DeviceManagementConfiguration.Read.All' -NoWelcome
    
    function Get-GraphPages {
        param([string]$Uri)
        while ($Uri) {
            $page = Invoke-MgGraphRequest -Method GET -Uri $Uri
            $page.value
            $Uri = $page.'@odata.nextLink'
        }
    }
  3. Collect the device evidence for pilot users only. The script flags any device that has not synced for seven days and prints any pilot user who has no enrolled Windows device.
    powershell
    $deviceUri = "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices?`$filter=operatingSystem%20eq%20'Windows'&`$select=deviceName,userPrincipalName,osVersion,complianceState,managementState,managedDeviceOwnerType,isEncrypted,enrolledDateTime,lastSyncDateTime"
    $cutoff = (Get-Date).ToUniversalTime().AddDays(-7)
    
    $devices = Get-GraphPages -Uri $deviceUri |
        Where-Object { $pilotUsers -contains $_.userPrincipalName } |
        ForEach-Object {
            [pscustomobject]@{
                DeviceName      = $_.deviceName
                User            = $_.userPrincipalName
                OsVersion       = $_.osVersion
                Compliance      = $_.complianceState
                Management      = $_.managementState
                Ownership       = $_.managedDeviceOwnerType
                Encrypted       = $_.isEncrypted
                Enrolled        = $_.enrolledDateTime
                LastSync        = $_.lastSyncDateTime
                NotSeenFor7Days = ([datetime]$_.lastSyncDateTime).ToUniversalTime() -lt $cutoff
            }
        }
    
    $devices | Export-Csv -Path (Join-Path $outDir 'pilot-devices.csv') -NoTypeInformation -Encoding UTF8
    $devices | Format-Table -AutoSize
    
    $missing = $pilotUsers | Where-Object { $_ -notin $devices.User }
    if ($missing) { "No enrolled Windows device found for: $($missing -join ', ')" }
  4. Collect the policy evidence. The BroadTargets column shows any All devices or All licensed users assignment on a policy.
    powershell
    function Get-BroadTargets {
        param([string]$PolicyUri)
        $types = Get-GraphPages -Uri "$PolicyUri/assignments" | ForEach-Object { $_.target.'@odata.type' }
        (@($types) | Where-Object { $_ -match 'allDevices|allLicensedUsers' }) -join ';'
    }
    
    $base = 'https://graph.microsoft.com'
    
    $compliance = Get-GraphPages -Uri "$base/v1.0/deviceManagement/deviceCompliancePolicies" |
        ForEach-Object {
            [pscustomobject]@{
                Name         = $_.displayName
                Type         = $_.'@odata.type'
                Version      = $_.version
                LastModified = $_.lastModifiedDateTime
                BroadTargets = Get-BroadTargets -PolicyUri "$base/v1.0/deviceManagement/deviceCompliancePolicies/$($_.id)"
            }
        }
    $compliance | Export-Csv -Path (Join-Path $outDir 'compliance-policies.csv') -NoTypeInformation -Encoding UTF8
    $compliance | Format-Table -AutoSize
    
    $catalog = Get-GraphPages -Uri "$base/beta/deviceManagement/configurationPolicies" |
        ForEach-Object {
            [pscustomobject]@{
                Name         = $_.name
                Platforms    = $_.platforms
                SettingCount = $_.settingCount
                IsAssigned   = $_.isAssigned
                LastModified = $_.lastModifiedDateTime
                BroadTargets = Get-BroadTargets -PolicyUri "$base/beta/deviceManagement/configurationPolicies/$($_.id)"
            }
        }
    $catalog | Export-Csv -Path (Join-Path $outDir 'settings-catalog-policies.csv') -NoTypeInformation -Encoding UTF8
    $catalog | Format-Table -AutoSize
  5. Open the CSV files and compare them with your register, then sign out. Success looks like this: every pilot user has a device, each device is compliant, NotSeenFor7Days is False and BroadTargets is empty for every policy that belongs to the pilot. Anything else is a finding to fix or document, not a script fault.
    powershell
    Disconnect-MgGraph

Emergency access and change control

Check emergency access before anything that can block sign-in is enforced, because you discover you needed it at the worst possible moment. Microsoft's guidance for emergency access accounts is specific, and each point belongs in the pilot pack with a date against it.

  • Two or more emergency access accounts exist. They are cloud-only accounts on the onmicrosoft.com domain with the Global Administrator role, not synchronised or federated.
  • They use a passwordless, phishing-resistant method that differs from your everyday admins' method. Microsoft recommends a passkey (FIDO2). The credentials are stored securely, are not tied to one person's phone and can be reached by more than one authorised person.
  • They are excluded from every Conditional Access policy that blocks or restricts sign-in. Report-only policies do not need an exclusion.
  • Sign-ins are monitored with an alert, and the accounts are tested at least every 90 days. Record the date of the last test and who ran it.
  • At least two people can administer Intune. This also matters for Multi Admin Approval, which needs two administrator accounts to work.
  • Multi Admin Approval is optional for a pilot but worth understanding. It can require a second administrator's approval for changes to apps, compliance policies, configuration policies, scripts, roles, tenant configuration and the wipe, retire and delete device actions. A requester cannot approve their own change, the requester must select Complete after approval, requests expire after 3 days and Intune sends no notifications, so agree how approvers get told. Do not protect the Role type until every other access policy and the approver group's role assignment are in place, or you can deadlock yourself.
  • Whether or not you use Multi Admin Approval, keep a plain change log with what changed, who changed it, when, why and how to reverse it. Intune audit logs record the actions, and the log records the reasons.
text
Change log entry
Date and time: YYYY-MM-DD HH:MM
Changed by: YOUR_ADMIN_NAME
What changed: YOUR_POLICY_OR_APP_NAME and the setting or assignment altered
Reason: YOUR_REASON
Affected group: YOUR_PILOT_GROUP
How to reverse: YOUR_ROLLBACK_ACTION
Verified by: YOUR_SECOND_PERSON

Document and rehearse the way back

A pilot without a way back is just a production rollout with a smaller audience. For each row in your register, write the reversal, then perform it once on a spare test device and record what you saw. Unassigning something is only half of rolling it back.

Intune also has a Deployments feature for ring-based rollouts of Win32 apps and settings catalog and endpoint security policies on Windows. Microsoft labels it public preview, apps must use the Required intent and a deployment's payload and rings cannot be edited after creation. For a small pilot, plain assignments to a pilot group are easier to explain and to reverse.

  • Configuration profiles: remove the assignment and sync the device. On Windows, Microsoft notes that what happens next depends on the configuration service provider behind each setting, because some remove the value and some leave it in place. Check that the setting itself went back, not just that the profile disappeared from the portal. For users removed from a group, Microsoft says allow up to 7 hours or more.
  • Apps: removing a required assignment does not uninstall the app. If the app has to go, plan an uninstall assignment, which Deployments does not support.
  • Conditional Access and compliance: put the policy back to report-only or off, then confirm that an emergency access account and a pilot user can both sign in. Also review actions for noncompliance and grace periods, so a short-lived fault does not lock someone out.
  • Updates: document where to pause the update ring and who may do it.
  • Remediations: the written rollback must say how to reverse what the remediation script changed, because unassigning it will not.
  • Devices: retire removes company data and management, and wipe is a factory reset that removes all personal and organisational data. Windows offers options to keep the enrolment state and user account or to continue the wipe if power is lost. Microsoft warns that the power-loss option can leave some devices unable to start. Treat both as last resorts and never rehearse them on a device someone is using for work.

Monitoring, support and handover

Reports lag. Microsoft says it can take longer for Intune reports to show the latest policy status than for the device to apply it, so give each check time before raising an alarm. During the pilot, look in these places at least weekly and file what you see with the evidence.

Handover is where 'I know how this works' becomes 'the organisation can run this'. Name an accountable owner, a day-to-day technical owner and a deputy, and write down everything they would otherwise have to ask you.

  • Devices > Manage devices > Compliance, and Devices > Monitor > Setting compliance, for compliance state and the Is active validity check.
  • Each policy's device status for Succeeded, Error and Conflict results, and Devices > Manage devices > Scripts and remediations for script results where you use them.
  • The Report-only tab of the Entra sign-in log details for each report-only Conditional Access policy, and the Intune audit logs for who changed what.
  • Your weekly run of the PowerShell report, compared with the previous week's CSV files.
  • Support runbook: decide who answers first, who they escalate to and when. Microsoft's example uses three tiers with Microsoft support above them. Every pilot issue is logged with its fix, so patterns show up before the wider rollout. Users can open Company Portal and use Settings > Sync, and administrators can run a device sync from the admin centre. First-line staff should not retire or wipe devices without approval.
text
Intune pilot handover record
Pilot name: YOUR_PILOT_NAME
Record date: YYYY-MM-DD
Accountable owner: YOUR_NAME_AND_ROLE
Technical owner: YOUR_NAME_AND_CONTACT
Deputy: YOUR_NAME_AND_CONTACT
Pilot groups and members: YOUR_GROUP_NAMES_AND_WHERE_THE_MEMBER_LIST_LIVES
Licences in use: YOUR_PLAN_NAMES_AND_ENTITLEMENT_CHECK_DATE
Policy register location: YOUR_REGISTER_LOCATION
Evidence folder and retention: YOUR_FOLDER_AND_DELETE_DATE
Emergency access: ACCOUNT_COUNT, LAST_TEST_DATE, WHO_CAN_RETRIEVE_CREDENTIALS
Change approval method: YOUR_METHOD
Rollback rehearsed: YES_OR_NO, DATE, RESULT
Support route and escalation: YOUR_ROUTE
Open issues and accepted risks: YOUR_LIST
Next review date: YYYY-MM-DD

Sign off the pilot or hold it

The pilot passes when you can show all of the following with dated evidence: every pilot user has a licensed, recently synced and understood device; the register covers every policy, app and script with an owner and rollback; the weekly report shows no unexpected broad assignments; the way back has been rehearsed; emergency access has been tested; and handover names real people. Hand the pack and any open issues to whoever approves production. Scope, timing and user communications for that step are their own decision.

If something fails, hold the pilot at its current size. Do not add users to find out whether it fixes itself.

  • Graph returns an authorisation error: your account lacks an Intune read role, or consent for the two read-only permissions has not been granted. Fix the access. Do not switch to ReadWrite scopes to make the error go away.
  • The settings catalog section fails: it uses a beta endpoint, so export that list from the portal and record the date you did so.
  • A pilot policy shows a BroadTargets value: stop onboarding users and correct the assignment, because the pilot boundary is not holding.
  • A device has not synced: ask the user to use Company Portal > Settings > Sync, then run a device sync from the admin centre. If a Windows device shows sync error 0x80072f9a after its TPM was reset, Microsoft says it must re-enrol, because the device's Entra identity is stored in the TPM.
  • Reports disagree with the device: allow for report lag and the next sync cycle before treating it as a fault, then compare the policy status in the device view with the CSV.
Technical terms explained
compliance status validity period
The number of days, 30 by default, within which a device must report its compliance status before Intune treats it as noncompliant.
Conditional Access
A Microsoft Entra feature that decides whether a sign-in is allowed, blocked or asked for extra proof, based on conditions such as the user, the app and whether the device is compliant.
Microsoft Graph
Microsoft's programming interface for reading and managing Microsoft 365, Entra and Intune data, which PowerShell can call using the Microsoft Graph PowerShell SDK.
Multi Admin Approval
An Intune feature that requires a second administrator to approve a change to protected resources before Intune applies it.
Remediations
Intune script packages made of a detection script and a remediation script that find and fix a problem on Windows devices. They need a qualifying Windows licence.
report-only mode
A Conditional Access policy state that evaluates a policy at each sign-in and logs what would have happened, without enforcing it.
settings catalog
The Intune policy type that lists the available Windows settings individually so you can choose exactly which ones to configure.

Sources and further reading

KEEP THE CONVERSATION GOING

Planning an Intune pilot?

If you would like a second pair of eyes on your pilot plan, register and rollback notes before real users are involved, tell us about your devices and what you need to keep running.

Talk to us about your Intune pilot