Parallels Desktop Enterprise Edition Administrator's Guide
ProductsSupportDocumentation
  • Introduction
  • Upgrading from Business Edition
    • How to Trial Enterprise Edition with Existing Business Edition Per-user License
    • What Happens after a Trial Ends
    • Migrating from Business Edition to Enterprise Edition
    • Migrating from per-device to per-user licensing
  • Getting Started
    • Creating a Business Account and Registering Your License
    • Dividing Users into Groups with Sublicenses
    • Configuring Golden Images and Policies in the Management Portal
    • Installing and Activating Parallels Desktop
  • Configuring the Single Sign-On (SSO) integration with Parallels My Account
    • Prerequisites
    • Starting the Integration Process in Parallels My Account
      • Configuring SSO Integration with Azure/Entra ID
      • Configuring SSO Integration with Okta
      • Configuring SSO Integration with Ping Identity
      • Configuring SSO Integration with JumpCloud
      • Configuring SSO Integration with Google Workspace
    • [OPTIONAL] How to Divide Users into Groups and Assign Them Sublicenses
    • Troubleshooting the SSO Activation
  • Creating and Uploading Virtual Machine Images
  • Mass Deployment of Parallels Desktop and Virtual Machines
    • Deploying via an Invitation Email
    • Mass Deployment Using Mac Management Tools
      • [RECOMMENDED] Deploying Parallels Desktop via MDM App Catalogs Using Configuration Profiles
        • Creating and Editing a Configuration Profile in iMazing
        • Deploying Parallels Desktop via MDM App Catalog (as seen in Jamf Pro)
      • [ALTERNATIVE] Mass Deployment via Deployment Package
        • Prerequisites
        • Supported Mac Management Tools
        • Preparing the Autodeploy Package
          • Downloading the Autodeploy Package
          • Specifying a License Key
          • [OPTIONAL] Adding the Parallels Desktop Installation Image
          • [OPTIONAL] Adding a Virtual Machine
            • Installing Parallels Tools
            • Preparing Windows for Mass Deployment
            • Common Configuration Options
          • Adding Windows Application Stubs
          • Configuring Deployment Options
          • Single Application Mode
          • [MANDATORY] Creating a Flat Package
          • Testing the Autodeploy Package
        • Deploying the Package to Macs
          • Example: Jamf Pro
            • Automating Parallels Desktop Initial Setup with a Configuration Profile
          • Using a Script to Change VM Options
    • Enrolling Virtual Machines in Azure Active Directory
  • Parallels Management Portal
    • Golden Images
    • Policies
    • User Groups
    • Virtual Machines
    • Providing Feedback
  • Parallels Desktop for Mac Enterprise Edition Features
    • [DEPRECATED] Using Configuration Profiles
      • Creating a Configuration Profile
      • Applying a Configuration Profile to a License Key
      • Provisioning a Corporate VM Image
        • Creating a Configuration Profile
        • Installing a VM Image on a Mac
      • Enabling Major Version Upgrades
        • Creating a Configuration Profile
    • Participating in the Customer Experience Program
    • Locking a Virtual Machine on Suspend
    • Activating Using a Corporate Account
    • Restricting a Virtual Machine Configuration with a Custom Password
    • Restricting User Actions in Parallels Desktop
    • Setting an Asset Tag in the Virtual Machine BIOS
    • Using Custom Graphics and Links in the Control Center
    • Hiding Developer Tools in the Parallels Desktop GUI
    • Encrypting a Virtual Machine
    • Single Application Mode
    • Setting an Expiration Date on a Virtual Machine
    • Enforcing USB Device Policies
    • Resetting the Guest OS Password
    • Setting Up a Local Update Server
      • Setting Up a Local Web Server
      • Creating the Parallels Update XML File
      • Configuring Individual Macs
    • Configuring Parallels Desktop Update Branch
    • Customizing the Support Center Option
Powered by GitBook

Other Resources

  • Community Forum
  • Knowledge Base
  • Request Support

Social Media

  • Facebook
  • Twitter/X
  • YouTube
  • LinkedIn

© 2025 Parallels International GmbH. All rights reserved.

On this page
Export as PDF
  1. Mass Deployment of Parallels Desktop and Virtual Machines

Enrolling Virtual Machines in Azure Active Directory

PreviousUsing a Script to Change VM OptionsNextParallels Management Portal

Enrolling Parallels virtual machines in Azure Active Directory with Microsoft Intune enables managing and securing your virtual machine environment. To achieve that goal, you will have to create a provisioning package and deliver it to your end users. To learn more about provisioning packages for Windows, follow .

Warning: You will only be able to successfully enroll the machines deployed from an Autodeploy Package that includes a Windows virtual machine prepared for deployment, and with the vm_reset_hwid parameter in the deploy.cfg file set to "yes". For more information on configuring the Autodeploy Package, please refer to the respective of this guide.

Be advised that setting this parameter to "yes" may affect active software licenses on the deploying machines; however, without this step, your Azure infrastructure will not be able to detect all the VMs as separate entities.

Follow these steps:

1. Install Windows Configuration Designer from Microsoft Store or download it directly from the Microsoft website.

2. Once installed, launch it and create a new project following the Provision desktop devices template.

3. Once the project is created, you will see the following page:

At this point, you need to choose a name convention. Once done, click Next and switch to the Set up network tab. There, you need to switch off the setup network toggle and click Next, proceeding to the Account Management page.

Note: In Parallels Desktop for Mac, a virtual machine uses the host Mac's internet connection in a way specified by its settings. From Windows's point of view, the virtual network adapter is a standard Ethernet connection. Therefore, there is no need to separately connect the virtual machine to your company's corporate network.

4. The following step is important: You need to select the Enroll in Azure AD option and obtain a bulk token.

Here, you need to sign in with your Microsoft Azure credentials. Once you’ve successfully signed in, you’ll see the message confirming the successful receipt of the token.

5. Click Next. Feel free to skip the remaining steps by clicking Next on each one of them.

6. Finally, you need to double-check your configuration summary and ensure everything is correct.

Click Create and memorize the path to the package file.

From this point, you have three possible ways to proceed:

  1. Share the package with users who will need to launch it to enroll their virtual machines in Azure;

  2. Install the package manually on every machine;

Add the package to the installation process as part of the SetupComplete.cmd script, as described in section 5 of .

this KB article
this link
section