MDM deployment guide
Deploy Punch List with Microsoft Intune
Microsoft Intune deploys the Punch List app and its enterprise license to your managed iPhones, iPads, and Android devices using an App Configuration Policy. You push one license key, and Pro unlocks automatically the first time each device opens the app. No per-user accounts, no app store billing.
Covers iOS, iPadOS, and Android.
Who this is for
Is this guide for you?
IT administrators who manage a construction fleet with Microsoft Intune and need to unlock Punch List Pro across every managed device from one console.
Before you start
Prerequisites
- An active Microsoft Intune tenant that can push managed app configuration to enrolled devices.
- For iOS and iPadOS: an Apple Business Manager account, linked to your MDM, with the free Punch List app licenses acquired under Apps and Books.
- For Android: Managed Google Play access, with Punch List approved for your organization.
- Your Punch List license key, org ID, and org name from the setup email we send after purchase.
- Network access from devices to https://api.mypunchlistapp.com, the only domain Punch List needs to reach.
Deployment
Push the license key with Microsoft Intune
You set three key/value pairs on the Punch List app. Your MDM delivers them to every managed device silently, and the app reads them on launch.
- 1
Add Punch List to your app library
Sign in to the Microsoft Intune admin center and go to Apps. Add Punch List as an iOS store app (search the App Store) for iPhone and iPad, or as a Managed Google Play app for Android. Assign it to the device group that should receive it.
- 2
Create an App Configuration Policy
Go to Apps, then App configuration policies, and add a policy under Managed devices. Choose Managed devices, not Managed apps: a Managed apps (app-protection) policy uses a different delivery channel that Punch List does not read, so activation will silently fail. Set the platform (iOS/iPadOS or Android Enterprise) and target the Punch List app.
- 3
Set the three configuration values
Use the configuration designer (or enter the key/value pairs manually) and add the three keys below, each as a String value.
- 4
Assign and save
Assign the policy to the same device group that receives the app, then create it. Devices pick up the app and configuration on their next Intune check-in, usually within a few minutes to an hour.
The three configuration keys
Set these exactly. Key names are case-sensitive, lowercase, with underscores. The example values below use a fictional organization for illustration.
| Key | Type | What to enter | Example |
|---|---|---|---|
license_key | String | Your license key from the setup email | pl_ent_acme_construction_a1b2c3d4e5f6 |
org_id | String | Your org ID from the setup email | acme_construction |
org_name | String | Your org name from the setup email | Acme Construction |
Important notes
- Key names are case-sensitive. Use exactly license_key, org_id, and org_name (lowercase, with underscores). Leading or trailing whitespace in a value will cause activation to fail.
- On Android, Intune builds the configuration screen from the schema the app publishes to Managed Google Play, so the three keys appear only once the Punch List Android build declares them. If no Punch List keys appear, email support@mypunchlistapp.com to confirm the current Android build status.
Verify
Confirm Pro unlocked on a test device
Before rolling out to your full fleet, test activation on a single device.
- 1Open Punch List on a test device that has received the app and configuration from your MDM.
- 2On first launch the app briefly shows "Activating..." while it validates the license, usually 1 to 2 seconds on a normal connection.
- 3After validation the app opens straight to the main screen. No sign-in, no purchase prompt, no license code to type.
- 4To confirm Pro is active, open Settings and check that it shows "Licensed by [your organization name]" with Pro features unlocked and no upgrade prompts.
If the app does not activate within 30 seconds of first launch, check that the device received the configuration and that the three keys have no typos or extra whitespace, then email support@mypunchlistapp.com with your org ID.
Troubleshooting
Microsoft Intune FAQ
- My App Configuration Policy has no effect. What is wrong?
- The most common cause is creating the policy under Managed apps instead of Managed devices. Managed apps is the app-protection (MAM) channel, which Punch List does not read. Delete the policy and recreate it under Apps, App configuration policies, Add, Managed devices.
- The Android configuration keys do not appear in Intune.
- Intune reads the available keys from the schema the Android app publishes to Managed Google Play. If the Punch List keys are not listed yet, the Android build has not declared them. Email support@mypunchlistapp.com to check the current build status.
- How long until devices activate after I save the policy?
- Devices receive the app and configuration on their next Intune check-in, typically a few minutes to an hour. To speed it up, select the device in Intune and choose Sync.
- Do I still need Apple Business Manager with Intune?
- Yes, for iOS and iPadOS. Link Apple Business Manager to Intune and acquire the free Punch List app licenses under Apps and Books so Intune can install the app silently. Android uses Managed Google Play instead.
Ready to roll out Punch List?
Buy seats and get your license key, or talk to our team about your deployment.
enterprise@mypunchlistapp.comUsing a different MDM? See all deployment guides.