AHV

Frame supports Entra joined devices Early Access on AHV for Windows 10/11 operating systems in persistent desktop Frame Accounts.

Prerequisites

• Bring Your Own (BYO) Azure subscription
• Entra ID Tenant
• New or existing Windows 10/11 persistent desktop Frame Account

Setup

1. Navigate to the persistent desktop Frame Account Dashboard within your AHV cluster in Frame Console.

2. Go to the Settings page, click on Domain Settings and select Entra ID. Then, click the Save button.

   

   note

   The Entra joined device feature requires users to login with their Entra ID user account.

3. Navigate to the Sandbox page, and Publish the Sandbox.

   

   note

   Only test and production pool VMs will be Entra device joined. Sandbox and Utility server(s) will not be Entra device joined. If you wish to join your Utility server(s) to your Entra ID tenant, they must be joined manually.

   danger

   Do not join the Sandbox to Entra ID as this action can lead to sysprep failures during the publish process.

4. After a successful publish, navigate to the Status page to check the status of your VMs. You will notice that Entra joined devices have a prefix in their hostnames.

   

5. When end users log into their assigned VM, they will be asked to enter their Entra ID credentials as shown below:

   

Windows Hostname Prefix

The Windows hostnames for Entra joined devices on AHV will be generated once the VMs are provisioned, by concatenating a prefix of 4 characters, a string "AAD-", and a 7 alphanumeric string, following the procedure described in Microsoft's official documentation.

The prefix will be the first 4 characters of the filename of the master image used to create the Frame Account Sandbox.

Windows 10/11 OOBE

The first time a user accesses their Entra joined persistent desktop on AHV, the user will go through the Microsoft Windows Out of the Box Experience (OOBE). The experience will depend on whether the persistent desktop is Windows 10 or 11 Enterprise Edition or Professional Edition.

note

If you have a use case where you need to reassign an Entra joined persistent desktop to another user, confirm that your Entra ID policies will grant the new user local Windows administrator privileges (if this is required).

Enterprise Edition

1. Upon accessing their persistent desktop for the first time, the user will be prompted to choose a region.

   

2. Next, select a keyboard layout.

   

3. Optionally add a second keyboard layout.

   

4. Review and accept the OS license agreement. By accepting the agreement, the user agrees to comply with its terms.

   

5. Next, the user will need to set up their user account by entering their Entra ID username.

   

6. On the next page, they'll be prompted to enter their Entra ID password.

   

7. Choose their privacy settings.

   

8. Once OOBE process is completed, the user will be logged into their Entra joined virtual machine.

Professional Edition

1. Upon accessing their persistent desktop for the first time, the user will be prompted to choose a region.

   

2. Next, select a keyboard layout.

   

3. Optionally add a second keyboard layout.

   

4. Review and accept the OS license agreement. By accepting the agreement, the user agrees to comply with its terms.

   

5. Set up their user account by selecting "Set up for Work or School".

   

6. Next, the user will need to set up their user account by entering their Entra ID username.

   

7. On the next page, they'll be prompted to enter their Entra ID password.

   

8. Lastly, the user will be asked to select their desired privacy settings.

   

9. After saving their privacy settings, the user may be logged out of their Frame session. If this happens, they simply need to start a new session.

   

10. Once the OOBE process is complete, the user will be logged into their Entra joined virtual machine.