---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Configure policy to pull software data

# Configure a policy to pull software data of multiple VMs {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Configure an Azure policy to use a single workspace for pulling the software data of multiple virtual machines (VMs) in different subscriptions.

## Vorbereitungen

* Ensure that you've configured the Service Graph Connector for Microsoft Azure. For more information, see [Configure Service Graph Connector for Microsoft Azure using the guided setup](https://www.servicenow.com/docs/4lRvZbqFpdpEjNiHshe8AQ "Set up data sources and scheduled import jobs to pull in data from Azure into your CMDB.").
* Ensure that you have the Resource Policy Contributor and User Access Administrator roles. For more information, see, [What is Azure Policy?](https://learn.microsoft.com/en-us/azure/governance/policy/overview) on the Azure documentation site.

{#sgc-cmdb-set-azure-policies__ul_dfq_4hy_5xb}

Role required: Resource Policy Contributor and User Access Administrator of the Azure directory

## Warum und wann dieser Vorgang ausgeführt wird

Workspaces are associated with single subscriptions only. So, rather than configuring a subscription every time for pulling software data using the connector, you can add VMs from various subscriptions to a single workspace by using the following Azure policies:

* For Windows-based VMs: LogAnalyticsExtension_Windows_VM_Deploy.json
* For Linux-based VMs: LogAnalyticsExtension_Linux_VM_Deploy.json

{#sgc-cmdb-set-azure-policies__ul_bch_ql5_vxb}

For more information, see [Azure policy definitions](https://github.com/Azure/azure-policy/tree/master/built-in-policies/policyDefinitions/Monitoring) on the GitHub repository.  
Hinweis:  
This configuration is optional and is done after you've configured the Service Graph Connector for Microsoft Azure.

## Prozedur

1. Sign in to the [Azure portal](https://portal.azure.com/).
2. Navigate to Subscriptions and then select Manage policies.
3. From the left menu, select SettingsPolicies.
4. On the Policy page, select Assign policy.
5. In the Policy definition field of the Basics tab, select the ellipsis icon (...).
6. In the Available Definitions side panel, search for the policy based on your machine type.
   * For Windows-based VMs, select Deploy - Configure Log Analytics extension to be enabled on Windows virtual machines policy.
   * For Linux-based VMs, select Deploy - Configure Log Analytics extension to be enabled on Windows virtual machines policy.
   {#sgc-cmdb-set-azure-policies__choices_idt_bl5_vxb}
7. Select Add.
8. Select the Parameters tab.
9. In the Log Analytics workspace field of the Parameters tab, select the ellipsis icon (...).
10. From the Subscription and workspaces lists of the Log Analytics workspace side panel, select a subscription and the workspace to connect the multiple VMs with different subscriptions. {#sgc-cmdb-set-azure-policies__workspace}
{#sgc-cmdb-set-azure-policies__workspace}
11. Select Review + create on the Assign policy page.
12. Review the selected options and then select Create.  
    The assignment of the policy could take some time.  
    Hinweis:  
    The policy enables the role assignments to the VMs of that subscription by installing the extension in the VMs. {#sgc-cmdb-set-azure-policies__create-policy}
{#sgc-cmdb-set-azure-policies__create-policy}
13. Repeat steps [10](https://www.servicenow.com/docs/nhpY_fc_cPnsE~YIPZRliw#sgc-cmdb-set-azure-policies__workspace) to [12](https://www.servicenow.com/docs/nhpY_fc_cPnsE~YIPZRliw#sgc-cmdb-set-azure-policies__create-policy) for each subscription to be associated with the workspace.
14. Create a remediation task for the policy to complete the compliance process of the existing VMs associated with the subscriptions.  
    For more information, see [Create a remediation task](https://learn.microsoft.com/en-us/azure/governance/policy/how-to/remediate-resources?tabs=azure-portal#create-a-remediation-task) in the Azure documentation.
15. Add the VMs to the inventory in the linked automation account.  
    For more information, see [Enable Change Tracking and Inventory from an Automation account](https://learn.microsoft.com/en-us/azure/automation/change-tracking/enable-from-automation-account) in the Azure documentation.