Desktop analytics is now available but only integrated with SCCM, so no Intune configuration for now, but let’s give it a test spin.
We will start by clicking Desktop Analytics in Microsoft 365 Device Management or by using this direct link https://aka.ms/desktopanalytics
Select Start.
Then we need to Accept service agreement, and note that data will leave EU!
This is taken from the FAQ (https://docs.microsoft.com/en-us/sccm/desktop-analytics/faq):
Can I choose the data center location?
For Azure Log Analytics: Yes, when you set up Desktop Analytics and create the Log Analytics workspace.
For the Microsoft Data Management Service and Analytics Azure Storage: No, these two services are hosted in the United States.
We need to confirm that we have the required qualifying licenses for Windows. Select Next to continue.
Next we will Allow Desktop Analytics to manage Directory roles on your behalf when we select this Desktop Analytics will automatically assign Workspace Owners the Desktop Analytics Administrator role.
The Workspace owner is preselected with the current user (global admin).
Select your Azure subscription and Add workspace, you can also select an existing workspace.
Enter a Workspace name.
Select the drop-down list to Select the Azure subscription name for this workspace.
We will create a new resource group but you can also use an existing.
Select the Region from the list, and then select Add.
If unsure about what region to choose, you can use the Azure Speed test to find the datacenter with the lowest latency (from your current location) http://azurespeedtest.azurewebsites.net/
Select the newly created workspace and select Set as Desktop Analytics workspace.
Select continue to grant access.
This will open a new browser tab, select an account to use for sign in. Select the option to Consent on behalf of your organization and Accept.
Go back to the Set up your workspace page, and select Next.
Select Go to Desktop Analytics.
We will then see the Desktop Analytics Home page. As stated it could take up to 72 hours before we have any data to view.
Now its time to setup Configuration Manager.
In the Configuration Manager console, go to Administration, expand Cloud Services, and select Azure Services, then select Configure Azure Services.
Name for the object in Configuration Manager, select Desktop Analytics and Next.
Select the appropriate Azure environment and click Browse.
Select Create to add an Azure AD app.
Name the application and enter HomePage URL and App ID URI, you can use the default values but the URI needs to be unique in your Azure AD tenant, It’s in the access token used by the Configuration Manager client to request access to the service.
Then select Secret Key validity period you can choose either 1 year or 2 years from the drop-down list.
Select Sign in.
After successfully sign-in to Azure you will see the Azure AD Tenant and the message Signed in successfully!
Use a Global Admin to sign in. The credentials will not be saved in Configuration Manager.
Select the new app and click OK.
Click Next.
Commercial ID will be automatically populated, select Windows 10 diagnostic data level and Allow Device Name in diagnostic data as preferred, but diagnostic data level must be at least Enhanced (Limited).
When changing diagnostic level expect users to be warned.
On the Office diagnostic data we can just click Next.
The Available functionality page shows the Desktop Analytics functionality that’s available with the diagnostic data settings from the previous page. Select Next.
Next we will configure the name shown for this SCCM in the Desktop Analytics portal, the collection that include all devices that SCCM will configure with our commercial ID and diagnostic data settings.
I was not able to add my specific collections to synchronize with desktop Analytics, even though the collection followed this rule:
The Select Collections window displays only the collections that are limited by the Target collection.
In the following example, you select CollectionA as your target collection. Then when you add additional collections, you see CollectionA, CollectionB, and CollectionC. You can’t add CollectionD.
- CollectionA: limited by the All Systems collection
- CollectionB: limited by CollectionA
- CollectionC: limited by CollectionB
- CollectionB: limited by CollectionA
- CollectionD: limited by All Systems collection
But we can add then later.
Select Next.
Select Close.
In the Configuration Manager console, go to Administration, expand Cloud Services, and select Azure Services, then select properties on our newly created Desktop Analytics service.
On the Desktop Analytics Connection tab select Add.
And this time I can see my collections, select the collections you want to be synchronized with desktop Analytics.
Select OK.
On the clients you will find configuration settings named M365ASettings.
When the client has evaluated and compliant the settings will be saved to these registry keys.
- HKLM:SOFTWAREMicrosoftWindowsCurrentVersionPoliciesDataCollection
- HKLM:SOFTWAREPoliciesMicrosoftWindowsDataCollection
From here we need to wait for the data to arrive in Azure.
In SCCM we we can follow the enrollment of devices into Desktop Analytics from Software Library – Desktop Analytics Servicing – Connection Health.
On the client we can follow the sending of data in the SCCM log M365AHandler.log.
With SCCM we have the following log files available to help troubleshoot issues with Desktop Analytics integrated with Configuration Manager.
| Log | Description | Available at |
| M365ADeploymentPlanWorker.log | Information about deployment plan sync from Desktop Analytics cloud service to on-premises Configuration Manager | Service connection point |
| M365ADeviceHealthWorker.log | Information about device health upload from Configuration Manager to Microsoft cloud | Service connection point |
| M365AUploadWorker.log | Information about collection and device upload from Configuration Manager to Microsoft cloud | Service connection point |
| SmsAdminUI.log | Information about Configuration Manager console activity, like configuring the Azure cloud services | Service connection point |
| M365AHandler.log | Information about the Desktop Analytics settings policy | Client |
In Azure it could take up to 72 hours before you start seeing data, but you can see if the client are transmitting data quicker by going to Connected services – Enroll Devices – View Recent data
Here you will see devices which have started to send data before they show up in the console.
Finally some examples from Desktop Analytics in Azure with data.
And SCCM dashboard.
