Note: Azure Virtual Desktop Insights relies on the Microsoft.Insights resource provider, so you need to first register it within the Azure subscription you are using for this lab. In Lab 01, you performed this task by using Azure PowerShell. In this lab, you will accomplish it by using the Azure portal (either method is supported and available).

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. In the web browser displaying the Azure portal, search for and select Subscriptions. On the Subscriptions page, select your Azure subscription. In the Settings section, select Resource providers.
3. On the Resource providers tab, in the search text box, enter Microsoft.Insights. In the list of results, select the Microsoft.Insights entry, and then select Register or Re-register.
4. Wait for the registration process to complete. Use the Refresh toolbar button to display the up-to-date value of the registration status.

Note: Azure Virtual Desktop Insights is a dashboard built on Azure Monitor Workbooks that facilitates monitoring of Azure Virtual Desktop environments. You can only monitor Autoscale operations with Insights with pooled host pools.

1. From your local computer, in the web browser displaying the Azure portal, search for and select Log Analytics workspaces, then select + Create.
2. On the Basics tab of the Create Log Analytics workspace page, specify the following settings and select Review + create:

   Setting	Value
   Subscription	The name of the Azure subscription you are using in this lab
   Resource group	<sName>-cpoF67-411e-RG (new resource group)
   Name	cpoF67-LAworkspace
   Region	The name of the Azure region where you deployed the Azure Virtual Desktop environment

3. On the Review + Create page, select Create. Screenshot must show your Odl_user account, the cpoF67-LAworkspace on the Review + create page in the <sName>-cpoF67-411e-RG resource group
4. Wait for the provisioning process to complete. This typically takes about 1 minute.

Note: Next, you need to enable data collection in the newly provisioned Log Analytics workspace of diagnostics from the Azure Virtual Desktop environment, performance counters from the session hosts, and Windows Event Logs from the Azure Virtual Desktop session hosts.

Note: When opening Azure Virtual Desktop Insights for the first time, you need to set up Azure Virtual Desktop Insights to target your Azure Virtual Desktop environment.

1. In the web browser displaying the Azure portal, search for and select Azure Virtual Desktop. On the Azure Virtual Desktop page, in the vertical navigation menu, in the Monitoring section, select Workbooks.
2. In the list of Windows Virtual Desktop workbooks, in the Windows Virtual Desktop section, select the Insights workbook.
3. On the Azure Virtual Desktop | Workbooks | Insights page, review the warning messages indicating that the workspace and session hosts are not sending data to the workspace, and then select the Configuration workbook link to repair the issue.
4. On the CheckAMAConfiguration page, on the Resource diagnostics settings tab, in the Log Analytics workspace drop-down list, select cpoF67-LAworkspace.
5. On the Resource diagnostics settings tab, in the Host pool <sName>-cpoF67-hp1 section, review the warning message indicating that no existing diagnostic configuration was found for the selected host pool, and then select Configure host pool.
6. In the Deploy Template pane, select Deploy.
7. Wait for the deployment to complete. This typically takes less than 1 minute.

   Note: This effectively enables the following diagnostics tables in the target Log Analytics workspace: Management Activities, Feed, Connections, Errors, Checkpoints, HostRegistration, AgentHealthStatus.

8. On the CheckAMAConfiguration page, on the Resource diagnostics settings tab, select the Refresh icon (a circular arrow) in the toolbar.
9. Review the Host pool <sName>-cpoF67-hp1 section and verify that the diagnostic settings are enabled for allLogs.
10. While on the Resource diagnostics settings tab, scroll down to the Workspace <sName>-cpoF67-21-ws1 section and then select Configure workspace.
11. In the Deploy Template pane, select Deploy.

    Note: This effectively configures the workspace for allLogs.

12. Wait for the deployment to complete. This typically takes less than 1 minute.
13. On the Resource diagnostics settings tab, select the Refresh icon (a circular arrow) in the toolbar.
14. Review the Workspace <sName>-cpoF67-21-ws1 section and verify that the diagnostic settings are enabled for allLogs and that there are no remaining warning messages. Screenshot must show your Odl_user account, the Workspace <sName>-cpoF67-21-ws1 section with diagnostic settings enabled for allLogs and no remaining warning messages
15. Navigate to the top of the CheckAMAConfiguration page and switch to the Session host data settings tab.
16. On the Session host data settings tab, in the Create DCR section, in the Workspace destination drop-down list, select cpoF67-LAworkspace, and then select Create data collection rule.
17. In the Deploy Template pane, select Deploy.
18. Wait for the deployment to complete. This typically takes less than 1 minute.
19. On the Session host data settings tab, select the Refresh icon (a circular arrow) in the toolbar.
20. Before you proceed, make sure that the newly created DCR is listed in the Available DCRs subsection of the Create DCR section. If that is not the case, wait for another minute and refresh the page again.
21. On the Session host data settings tab, in the Selected DCR drop-down list, select the entry starting with the microsoft-avdi- prefix.
22. If needed, on the Session host data settings tab, in the DCR associations section, select Deploy Association and, in the Deploy Template pane, select Deploy.

    Note: This effectively associates the newly created DCR with the session hosts in the <sName>-cpoF67-hp1 host pool.

23. Wait for the deployment to complete. This typically takes less than 1 minute.
24. On the Session host data settings tab, select the Refresh icon (a circular arrow) in the toolbar.
25. On the Session host data settings tab, in the Session hosts missing Azure Monitor extension section, select Add extension.
26. In the Deploy Template pane, select Deploy.

    Note: This effectively installs the Azure Monitor extension on the session hosts in the <sName>-cpoF67-hp1 host pool.

27. Wait for the deployment to complete. This might take about 1 minute.
28. On the Session host data settings tab, select the Refresh icon (a circular arrow) in the toolbar.
29. Verify that there are no error or warning messages displayed. Screenshot must show your Odl_user account, the CheckAMAConfiguration page with no error or warning messages after adding the Azure Monitor extension
30. Navigate to the top of the CheckAMAConfiguration page, select the Data generated tab, and then select the Refresh icon (a circular arrow) in the toolbar.
31. Review the sections displaying graphs representing collected data, including Billed data over last 24hrs, Performance Counters, and Events. Screenshot must show your Odl_user account, the Data generated tab with the Billed data over last 24hrs, Performance Counters, and Events graphs

    Note: Use the Billed data over last 24hrs section to monitor data ingestion. You are responsible for Log Analytics charges for data storage and ingestion.

32. In the web browser displaying the Azure portal, navigate back to the Azure Virtual Desktop page and, in the Monitoring section of the vertical navigation menu, select Insights.
33. On the Azure Virtual Desktop | Insights page, review the content of the Overview tab, including the Capacity section, Connection diagnostics: % of users able to connect, Connection performance: Time to connect (new sessions), and Utilization telemetry.
34. Next, review all the remaining tabs on the Azure Virtual Desktop | Insights page, including Connection Reliability, Connection Diagnostics, Connection Performance, Users, Utilization, Clients, and Alerts. Screenshot must show your Odl_user account, the Azure Virtual Desktop | Insights page with the Connection Reliability, Connection Diagnostics, Connection Performance, Users, Utilization, Clients, and Alerts tabs

Note: Now we need to stop collecting monitoring data to stop charges on our account. Go through the following steps to stop data collection while keeping the workspace intact for future use.

1. On the AVD | host pools page, select <sName>-cpoF67-hp1. From the Monitoring section, select Diagnostic settings, select edit settings, select delete and click Yes.
2. From the AVD | Workspaces, select <sName>-cpoF67-21e-ws1, then from Monitoring select Diagnostic settings. On the Diagnostic settings, select edit settings, select delete and click Yes. Screenshot must show your Odl_user account, the deleted diagnostic settings on the <sName>-cpoF67-21e-ws1 workspace
3. Verify that new data collection has stopped while the Log Analytics workspace and its current data are kept for future use. Screenshot must show your Odl_user account, the cpoF67-LAworkspace kept intact with diagnostic settings removed (data collection stopped)

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

1. Explain the role of the Log Analytics workspace in the Azure Virtual Desktop monitoring architecture. What types of data does it collect and store, and why is it important to select the same Azure region as your AVD environment when creating the workspace?
2. The lab instructs you to install the Azure Monitor extension on session hosts. What is the function of this extension, and what would be the consequence of not installing it on some or all of your session hosts?
3. The lab concludes by disabling diagnostic settings while keeping the Log Analytics workspace intact. Explain the cost implications of this decision. What are the two main sources of Azure Monitor costs, and why might an organization choose to disable data collection temporarily rather than deleting the entire workspace?
4. Reflect: what have you learned from completing this lab? Describe any challenges you encountered during the setup of Azure Virtual Desktop Insights and how you solved them.

Screenshots you attach above and your Task 5 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.