Scenario A: Software Developers & Engineers

Who this fits

Developers and engineers who need a Windows environment to build and test against, and who manage their own local toolchains once the VM is up.

Architecture at a glance

Same architecture as described in Overview & Decision Matrix: the Management Portal sources Windows declaratively, Jamf Pro installs and configures Parallels Desktop, and the resulting VM enrolls in Intune.

Deployment method and why

Declarative. Developers get a stock Windows image and add their own toolchains after first launch — there's no need to pre-build and maintain a custom .pvmp.

Management Portal policy settings

Create a policy for the developers' user group with a Golden Image set to Declarative / Windows Enterprise. Recommended settings for this group:

• Security Controls: Do not allow removing provisioned VMs.

• VM Settings: Clipboard/Drag-and-drop: Bidirectional · VM startup: Ready in background · Show Developer Tools: enabled.

See Stage 3: Management Portal & Remote Policy Setup for how to create the policy, and the full comparison across scenarios.

Role handoffs

• Portal Admin — creates the policy and Golden Image, assigns the developer group.

• Mac Admin — confirms Parallels Desktop is deployed via the Jamf app profile.

• Windows-Identity Admin — confirms the provisioning package enrolls the VM in Intune correctly for this group.

Verification

In the Management Portal, open the Golden Image card and confirm the developer's VM shows as provisioned. Ask the developer to confirm Windows completes first boot and signs in with their corporate account without manual setup.

Where to go next

Continue to Stage 1: Account, SSO & Licensing Configuration to set up the developer group's sublicense and activation.