How to connect Configuration Manager with Desktop Analytics

Desktop Analytics is tightly integrated with Configuration Manager. Any supported version of Configuration Manager supports Desktop Analytics. When connecting to a cloud service, make sure the site and clients are up to date to support the latest features. To connect the on-premises site with the Desktop Analytics cloud service, create the Desktop Analytics connection in Configuration Manager. Then monitor the health of the connection.

Connect to the service


Prior to starting the wizard, create the target collection mentioned in step 8, as you cannot select outside of the wizard once you start it.

Use this procedure to connect Configuration Manager to Desktop Analytics, and configure device settings. This procedure is a one-time process to attach your hierarchy to the cloud service.

  1. In the Configuration Manager console, go to the Administration workspace, expand Cloud Services, and select the Azure Services node. Select Configure Azure Services in the ribbon.


    Connect to the service directly from the Desktop Analytics Servicing node. In the Configuration Manager console, go to the Software Library workspace, and select the Desktop Analytics Servicing node. In the New to Desktop Analytics? box, select the second link to Connect Configuration Manager to the Desktop Analytics service.

  2. On the Azure Services page of the Azure Services Wizard, configure the following settings:

    • Specify a Name for the object in Configuration Manager.

    • Specify an optional Description to help you identify the service.

    • Select Desktop Analytics from the list of available services.

    Select Next.

  3. On the App page, select the appropriate Azure environment. Then select Browse for the web app.

  4. If you have an existing app that you want to reuse for this service, choose it from the list, and select OK.

  5. In most cases, you can create an app for the Desktop Analytics connection with this wizard. Select Create.


    If you can't create the app from this wizard, you can manually create the app in Microsoft Entra ID, and then import into Configuration Manager. For more information, see Create and import app for Configuration Manager.

  6. Configure the following settings in the Create Server Application window:

    • Application Name: A friendly name for the app in Microsoft Entra ID.

    • HomePage URL: This value isn't used by Configuration Manager, but required by Microsoft Entra ID. By default this value is https://ConfigMgrService.

    • App ID URI: This value needs to be unique in your Microsoft Entra tenant. It's in the access token used by the Configuration Manager client to request access to the service. By default this value is https://ConfigMgrService. Change the default to one of the following recommended formats:

      • api://{tenantId}/{string}, for example, api://5e97358c-d99c-4558-af0c-de7774091dda/ConfigMgrService
      • https://{verifiedCustomerDomain}/{string}, for example,
    • Secret Key validity period: choose either 1 year or 2 years from the drop-down list. One year is the default value.


    Take note of the expiration date and make sure to Renew the secret key before its expiration to ensure uninterrupted access to the service.

    Select Sign in . After successfully authenticating to Azure, the page shows the Microsoft Entra tenant Name for reference.


    Complete this step as a Global administrator. These credentials aren't saved by Configuration Manager. This persona doesn't require permissions in Configuration Manager, and doesn't need to be the same account that runs the Azure Services Wizard.

    Select OK to create the web app in Microsoft Entra ID and close the Create Server Application dialog. On the Server App dialog, select OK. Then select Next on the App page of the Azure Services Wizard.

  7. On the Diagnostic Data page, configure the following settings:

    • Commercial ID: this value should automatically populate with your organization's ID. If it doesn't, make sure your proxy server is configured to allow all required endpoints before continuing. Alternatively, retrieve your Commercial ID manually from the Desktop Analytics portal.

    • Windows 10 diagnostic data level: select at least Required. For more information, see Diagnostic data levels.


      In Configuration Manager version 2002 and earlier, this value was called Basic.

    • Allow Device Name in diagnostic data: select Enable


      Starting with Windows 10 version 1803, the device name isn't sent to Microsoft by default. If you don't send the device name, it appears in Desktop Analytics as "Unknown". This behavior can make it difficult to identify and assess devices.

    Select Next. The Available functionality page shows the Desktop Analytics functionality that's available with the diagnostic data settings from the previous page. Select Next to continue or Previous to make changes.

    Example Available Functionality page in the Azure Services Wizard.

  1. On the Collections page, configure the following settings:

    • Display name: The Desktop Analytics portal displays this Configuration Manager connection using this name. Use it to differentiate between different hierarchies, and to identify collections from separate hierarchies. Use terms to easily distinguish multiple hierarchies in your environment, for example: test lab or production.

    • Target collection: This collection includes all devices that Configuration Manager configures with your commercial ID and diagnostic data settings. It's the full set of devices that Configuration Manager connects to the Desktop Analytics service.

    • Devices in the target collection use a user-authenticated proxy for outbound communication: By default, this value is No. If needed in your environment, set to Yes.

    • Select specific collections to synchronize with Desktop Analytics: Select Add to include additional collections from your Target collection hierarchy. These collections are available in the Desktop Analytics portal for grouping with deployment plans. Make sure to include pilot and pilot exclusion collections.


      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
      • CollectionD: limited by All Systems collection

      To manage the collections available in the Desktop Analytics portal for grouping with deployment plans, in the Configuration Manager console, go to the Administration workspace, expand Cloud Services, and select the Azure Services node. Select the entry associated with Desktop Analytics Azure Service and update your settings in the Desktop Analytics Collection page.


      These collections continue to sync as their membership changes. For example, your Target collection uses a collection with a Windows 7 membership rule. As those devices upgrade to Windows 10, and Configuration Manager evaluates the collection membership, those devices drop out of the collection and Desktop Analytics.

  2. Complete the wizard.

Configuration Manager creates a settings policy to configure devices in the Target Collection. This policy includes the diagnostic data settings to enable devices to send data to Microsoft. By default, clients update policy every hour. After receiving the new settings, it can be several hours more before the data is available in Desktop Analytics.

Monitor connection health

Monitor the configuration of your devices for Desktop Analytics. In the Configuration Manager console, go to the Software Library workspace, expand the Desktop Analytics Servicing node, and select the Connection Health dashboard.

For more information, see Monitor connection health.

Configuration Manager synchronizes your collections within 60 minutes of creating the connection. In the Desktop Analytics portal, go to Global Pilot, and see your Configuration Manager device collections.


The Configuration Manager connection to Desktop Analytics relies upon the service connection point. Any changes to this site system role may impact synchronization with the cloud service. For more information, see About the service connection point.

Next steps

Advance to the next article to enroll devices to Desktop Analytics.