It's a common occurrence to see a full QR/NFC payload pasted into the DPC extras field of a zero-touch configuration, and while it may function, it's not best practice.
To assist in building better configurations, the below form has been created to allow organisations to create a custom payload, similar to that of the QR generators, but provide only the relevant details for zero-touch. Once generated, this can be pasted directly into the zero-touch configuration DPC extras field.
Do you have a JSON payload from your EMM already? Use the form at the bottom of this page to convert it!
No information is stored. If you refresh the page, everything will be reset. This is intentional as I have no interest in holding on to your JSON information, Wi-Fi details, or enrolment tokens. That said, as with all third-party applications you use this at your own risk. Check with your boss before you use this tool if you feel you need to.
When you click Generate JSON, all submitted information is processed locally, and the returned data is embedded ephemerally in this page. Edit the submitted text and click extract again to regenerate it, or refresh the page to clear it.
Where's the DPC input?! - There's no need for this. The DPC is selected from the zero-touch configuration.
DPC extras allow organisations to pre-configure the DPC with options during enrolment. These may include the EMM server address, staging credentials, enrolment tokens, and more.
Your EMM will have the most up-to-date support DPC extras, however I maintain a resource here which is occasionally also updated by the community.
The generator automatically adds brackets and spacing, so just enter the extras one-per-line, e.g.:
"serverurl":"your.server.com",
"gid":"yourGroupID",
"un":"staginguser",
"pw":"example"For AMAPI-based EMMs (Intune, NinjaOne, etc) if not using the AMAPI generator it would require:
"com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN": "YourEnrolmentToken" Remember: This field requires valid JSON, so don't forget those commas on all but the last line of extras, otherwise the QR code will error.
DPC extras should be closely guarded as they may grant access to the organisation's EMM platform and sensitive corporate resources. If details are compromised, they should be revoked immediately and new ones generated.
When setting up a new device or re-provisioning an existing one, the android.app.extra.PROVISIONING_LOCALE key can be configured to specify the locale. This key expects a string value in the format of language-country, where language is a two-letter ISO 639-1 language code and country is a two-letter ISO 3166-1 alpha-2 country code. See the example reference provided next to the input for guidance.
The android.app.extra.PROVISIONING_TIME_ZONE key is used during the provisioning of Android devices to set the device time zone. Modern Android devices can pick this up automatically and with Wi-Fi only, but for older Android versions (sub 12) it is far more rigid, and this setting avoids frustrating users down the line.
These settings are particularly useful in use cases where devices need to be configured with specific time and region parameters, and allows admins to configure these ahead of time when staging devices for global distribution.
Paste an existing QR JSON payload provided - presumably by an EMM - to convert it into a zero-touch-friendly DPC extras payload.
This conversion tool allows you to input a full QR JSON payload and retrieve only the relevant information for the zero-touch DPC extras field.
Usage:
If the JSON is not valid, an error will be shown. This form will not attempt to correct invalid keys or missing data.