Note: the RDP settings you implemented in the previous lab provide the optimal user experience (via support for single sign-on), however, this requires additional changes described in Configure single sign-on for Azure Virtual Desktop using Microsoft Entra ID authentication. Without these changes, by default, authentication is supported only if the client computer is Microsoft Entra joined, hybrid joined, or registered to the same Microsoft Entra tenant as the session host. Since none of these criteria apply to the lab computer, it is necessary to add targetisaadjoined:i:1 as a custom RDP property to the host pool.

1. If needed, from your local computer, start a web browser, navigate to the Azure portal and sign in by providing your Odl_user credentials.
2. On the <sName>-cpoF67-hp1 Azure Virtual Desktop host pool page, in the vertical menu bar, in the Settings section, select the RDP Properties entry.
3. On the <sName>-cpoF67-hp1 | RDP Properties page, select the Advanced tab.
4. On the Advanced tab, in the RDP Properties text box, append the following string to the existing content (make sure to add a leading semicolon character (;) if needed to separate this string from the one which precedes it):
   targetisaadjoined:i:1
5. In the RDP Properties text box, remove the following string (if present) from the existing content (with its trailing semicolon character):
   enablerdsaadauth:i:value (for example: enablerdsaadauth:i:1;)
6. On the <sName>-cpoF67-hp1 | RDP Properties page, select Save. Screenshot must show your Odl_user account, the RDP Properties Advanced tab with targetisaadjoined:i:1 appended and the enablerdsaadauth string removed

1. Note: if you don’t have a Windows 10/11 on your local computer, you can create a Virtual Machine (i.e. Client-VM) in a separate resource group (i.e. clientDemo-RG) and a separate Virtual Network (i.e. clientDemo-Vnet) and follow the instructions on the newly created Client-VM.
2. From your local computer, start a web browser, navigate to the Connect to Azure Virtual Desktop with the Remote Desktop client for Windows page, scroll down to the section Download and install the Remote Desktop client (MSI), and select the Windows 64-bit link.
3. Note: if you’re using a macOS device, then use Windows App.
4. Open File Explorer, navigate to the Downloads folder, and launch the installation of the newly downloaded MSI file.
5. In the Remote Desktop Setup window, when prompted, accept the terms of the licensing agreement and choose the option to Install for all users of this machine. If prompted, accept the User Account Control prompt to proceed with the installation.
6. Once the installation completes, ensure that the Launch Remote Desktop when setup exits checkbox is selected and select Finish to start the Microsoft Remote Desktop client.
7. Note: the Remote Desktop Store app for Windows doesn't support connecting to Microsoft Entra-joined session hosts. Screenshot must show your Odl_user account, the installed Microsoft Remote Desktop client window

1. On the lab computer, from the Remote Desktop client window, select Subscribe and, when prompted, sign in with your cpoF67-User1@senecalabswa credentials.
2. Note: alternatively, in the Remote Desktop client window, select Subscribe with URL, in the Subscribe to a Workspace pane, in the Email or Workspace URL, type https://client.wvd.microsoft.com/api/arm/feeddiscovery, select Next, and, once prompted, sign in with the Microsoft Entra credentials.
3. Ensure that the Remote Desktop page displays only the SessionDesktop icon.
4. Note: this is expected, because the Microsoft Entra user account you selected was assigned in the first lab Deploy host pools and session hosts by using the Azure portal to the auto-generated <sName>-cpoF67-hp1-DAG desktop application group.
5. On the Remote Desktop page, right-click the SessionDesktop icon and, in the pop-up menu, select Settings.
6. In the SessionDesktop pane, turn off the Use default settings switch.
7. In the Display settings section, in the drop-down menu, select the entry Select displays and choose the displays you want to use for the session.
8. In the SessionDesktop pane, review the remaining options, including Maximize to current displays, Single display when in windowed mode and Fit session to window, without making any changes.
9. Close the SessionDesktop pane.
10. On the Remote Desktop page, double-click the SessionDesktop icon.
11. When prompted to sign in, in the Windows Security dialog box, enter the password of the first Microsoft Entra user account, which you used in this task to connect to the target Azure Virtual Desktop environment.
12. Note: Azure Virtual Desktop doesn't support signing in to Microsoft Entra ID with one user account, then signing in to Windows with a separate user account. Signing in with two different accounts at the same time can lead to users reconnecting to the wrong session host, incorrect or missing information in the Azure portal, and error messages appearing while using app attach or MSIX app attach.
13. Note: you will be automatically presented with the SessionDesktop window.
14. In the Remote Desktop session window, verify that you have full administrative access within the session (for example, select the Windows logo icon in the taskbar and then select the Windows PowerShell(Admin) item from the pop-up menu). Screenshot must show your Odl_user account, the SessionDesktop remote session with full administrative access
15. In the Command Prompt window, type whoami /upn and press the enter key. Then, type ipconfig /all and press the enter key.
16. Within the Remote Desktop session window, select the Windows logo icon in the taskbar, select the avatar icon representing the Microsoft Entra user account you used to sign in and, in the pop-up menu, select Sign out.
17. Note: this will automatically terminate the Remote Desktop session.
18. Back in the Remote Desktop window, select the ellipsis (...) icon to the right of Title, select Subscribe when prompted, and sign in with the credentials of the cpoF67-User2@senecalabswa account.
19. Ensure that the Remote Desktop page displays four icons, including Command Prompt, Microsoft Word, Microsoft Excel, Microsoft PowerPoint.
20. Note: this is expected, because the Microsoft Entra user account you selected was assigned in the first lab Deploy host pools and session hosts by using the Azure portal (Entra ID) to the <sName>-cpoF67-hp1-Office365-RAG and <sName>-cpoF67-hp1-Utilities-RAG application groups.
21. Double-click the Command Prompt icon.
22. When prompted to sign in, in the Windows Security dialog box, enter the password of the second Microsoft Entra user account you used to connect to the target Azure Virtual Desktop environment.
23. Verify that a Command Prompt window appears shortly afterwards.
24. In the Command Prompt window, type whoami /upn and press the enter key. Then, type ipconfig /all and press the enter key. Screenshot must show your Odl_user account, the Command Prompt output of whoami /upn and ipconfig /all in the Remote App session
25. At the Command Prompt, type logoff and press the Enter key to log off from the current Remote App session.
26. Double-click the remaining icons on the Remote Desktop page to launch Microsoft Word, Microsoft Excel, and Microsoft PowerPoint making sure they all work properly.
27. Close each session window.
28. Back in the Remote Desktop window, select the ellipsis (...) icon to the right of each user (user1 & user2) workspace entry, select Unsubscribe and, when prompted to confirm, select Continue.

Minimum 2-3 sentences each — original thinking, your own words!

1. Why is it important for an administrator to be able to validate access to Microsoft Entra joined session hosts from a client that is not Entra-joined, hybrid-joined, or registered? Describe at least two real-world scenarios where this capability matters.
2. During the lab, you connected with two different Entra user accounts and saw different published resources (full desktop vs. specific apps). What does this teach you about how application group assignments can be used to design secure and flexible user experiences in Azure Virtual Desktop?
3. In Task 3 you connected as two different Entra users and ran whoami /upn and ipconfig /all inside the session. Describe what information these commands reveal and why both users were connected to the same session host.
4. Describe one moment in this lab where you felt your understanding of Azure Virtual Desktop “clicked” (for example, around RDP properties, workspace subscriptions, or app/desktop assignments), and explain how this insight would change the way you design or troubleshoot a real AVD deployment in the future.

Screenshots you attach above and your Task 4 answers appear here. This is exactly what prints/exports as your PDF.

1. All attached screenshots must be high quality, with your Odl_user account clearly visible.
2. A brief explanation added for each screenshot.
3. Export with Print / Save as PDF and upload it to the Blackboard lab submission page.