In this post I would like to present an integration between Desktop Analytics and SCCM using Azure components. DA integration with Intune is not yet possible, but According to MSFT, it will be released in the future.


We have an SCCM environment and we are using Desktop Analytics. Using a predefined query on DA logs, we want to add devices to a collection to deploy a remediation or a software on those devices


We will create a SCCM lab in Azure and deploy Desktop Analytics. Once we have data collected in the DA workspace we can create an alert using a predefined query. The alert will call an automation runbook to add the device in a table. From SCCM environment we periodically query the table and add devices to a collection.

To create the automation, we will do the following

  • Create a SCCM test lab in Azure
  • Deploy Desktop Analytics
  • Create the storage account and table
  • Create the automation account and runbook
  • Create the alert
  • On SCCM side, create a script to query the table and add device to an appropriate collection.


To perform action listed in this post, you will need an Azure subscription

Create SCCM Test Lab

This task is very simple. We will use an ARM template provided by MSFT. However, the domain name is set to contoso and we would need to change this to match our domain. The template will create a fully functional SCCM environment with one domain controller, one management point, one primary server and a client. There is no reporting server, but we don’t need that anyways.

  • Edit the parameters file to provide your admin username and password
  • Open an azure portal, and click the cloud shell icon at the top right of you screen near to you account
  • Click create if asked for a storage account for your shell session and select a bash session
  • Click upload and upload the 2 template files you downloaded
  • Run the following commands to deploy the template. Feel free to change the resource group name and location to your discretion

az group  create –name SCCM-AnalyticsCB-RG –location centralus

az deployment group create –resource-group SCCM-AnalyticsCB-RG –template-file azuredeploy.json –parameters @azuredeploy.parameters.json –no-wait

Now we wait… and… wait and come back in at least 6 hours. The deployment will create the machines in 20-30 minutes, but there are some scripts running on the machines that actually create the domain, joins machines to domain and install the SCCM. If you interrupt this, the installation will probably fail

I usually come back the next day to connect to the environment

Deploy Desktop Analytics

Next day, we see the deployment has been completed

Let’s deploy Desktop Analytics:

  • Go to endpoint manager portal –
  • Click All services and select Desktop Analytics
  • Click Start to begin the configuration process
  • Accept the service agreement
  • Confirm you have subscription and click Next
  • Make sure your user is listed under Workspace owners and click Next
  • In Setup your workspace pane, select a valid azure subscription
  • Add workspace
  • In add workspace window enter a workspace name, select your subscription and click create use existing under resource group  
  • Select the same resource group with your SCCM environment
  • Select a region close to your SCCM resource group
  • Select the newly created workspace from the list and click Set as Desktop Analytics workspace
  • In Confirm and grant access click continue
  • You will be redirected to confirm the permission
  • Click Next

Connect to SCCM console on management point server

  • Go to Administration
  • Expand Cloud services
  • Right click on Azure Services and Click configure azure services
  • In the new panel , enter a name for the service
  • Select Desktop Analytics
  • Click Next

In the next window we will configure an application registration for Azure

  • Leave the selected Azure Environment
  • Click Browse to create an application registration
  • In the new Server app window click create
  • In the new window enter an application name
  • Select the validity period
  • Click sign in for Azure Admin Account
  • Sign in with your global administrator account to create the app registration
  • Click Ok
  • Click Ok to select the newly created application
  • Back to App Properties window, click next to continue
  • In Configure Windows Diagnostic data set data level to full
  • Change Allow Device Name in diagnostic data to Enable
  • Click Summary and then Next to confirm the settings
  • Wait for wizard to complete the configuration and click close

Going back to the Desktop Analytic Dashboard, we are informed that we need to wait 72 hours for the data to be processed

We will continue in a separate post