Skip to main content
Question

Apple seed for IT beta testing with out blueprints?

  • February 6, 2026
  • 1 reply
  • 33 views

BCPeteo
Forum|alt.badge.img+11

I would like to enable the apple seed for IT beta program using the Beta token from Apple school manager to allow a device to get betas with out needing to login with an Apple ID on the device.

Reading documentation we are able to get the token using a script. But at that point Jamf is requiring you to use blueprints with this token. Since we are on prem we do not have access to bleuprints.

Any way to deploy the token a device using a config profile? How are other MDM’s enabling this?

1 reply

h1431532403240
Forum|alt.badge.img+6

No, the AppleSeed for IT beta token cannot be deployed via a traditional configuration profile. The beta token must be delivered through a DDM declaration (com.apple.configuration.softwareupdate.settings with the Beta dictionary) — this is not a payload that can be wrapped in a .mobileconfig file.

Since you're on-prem, Blueprints is not available to you. Blueprints requires Jamf Standard or Premium Cloud hosting with Jamf Account SSO integration.

How other MDMs handle this: Other MDMs that support custom DDM declarations (e.g., Kandji, Mosyle, SimpleMDM, Fleet) can deploy the softwareupdate.settings declaration directly — but they are all cloud-hosted solutions. DDM is fundamentally a server-side capability that requires the MDM server to support the DDM protocol exchange with devices.

Your options as an on-prem Jamf Pro customer with ASM:

  1. Migrate to Jamf Cloud — this would give you access to Blueprints and the Software Update Settings component for deploying beta tokens.
  2. Use a second cloud-based MDM alongside your on-prem Jamf Pro specifically for DDM-based workflows (not ideal, but some orgs do this during transition).
  3. Request this as a feature — ask Jamf to support DDM declaration deployment for on-prem instances, or at minimum provide an API endpoint to push custom declarations.

Unfortunately, there is no workaround to deploy DDM declarations via config profiles — they are fundamentally different delivery mechanisms.

References: