---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Azure change processing

# Azure change processing {#ariaid-title1}

Release version: Australia  
Updated May 11, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Azure change processing

The Azure change processing feature enables ServiceNow customers to collect near real-time information about lifecycle state or configuration changes in Microsoft Azure resources.
This information is then used to update the Configuration Management Database (CMDB), ensuring it reflects current Azure resource states.
Show full answer Show less  
The process runs through scheduled jobs that query the Azure API to gather changes since the last cycle, typically every 5 minutes by default. Changes are updated in the CMDB using response mappings, and during subsequent discoveries, Cloud Discovery triggers relevant patterns to populate detailed resource data.

## Key Features

* **Scheduled Jobs:** Azure change processing includes scheduled jobs---renamed in version 1.21.0 to ACP Pull Changes and ACP Process Changes---that query Azure APIs and process resource changes efficiently.
* **ACP Tables:** New tables introduced in version 1.21.0 help manage and track change processing:
  * **ACP Resource Type:** Lists supported Azure resource types, allows enabling/disabling change processing per resource, and defines queries.
  * **ACP Order Status:** Monitors query status per resource type and credential, tracking success or failure of change pulls.
  * **ACP Resource Change:** Stores detected changes with snapshots of resource attributes and processing state.
  * **ACP Resource Status:** Tracks overall processing state of each resource change with detailed error messages if failures occur.
* **Supported Azure Resource Types:** Tracks changes in key resource properties for virtual machines, disks, network security groups, network interfaces, and public IP addresses, capturing create/delete events, status changes, storage profiles, tags, IP configurations, and more.
* **Domain Assignment and Event Visibility:** Events are assigned to domains based on the service account. Configuration options exist to control visibility of unassigned or error events for security.
* **Setup and Upgrade:** Requires service accounts created by discoveryadmin or sncmp.cloudadmin roles. Customers must update Discovery and Service Mapping Patterns plugin to at least version 1.21.0 for enhanced functionality and renamed scheduled jobs.

## Benefits for ServiceNow Customers

* **Improved Performance:** Unlike alert-driven discovery, Azure change processing avoids triggering targeted discovery for each resource change, reducing Azure API throttling risks and improving the ServiceNow AI Platform's change processing efficiency.
* **Simplified Setup:** Uses Azure Resource Graph API and MID Server instead of multiple webhooks required per subscription, enabling management group level change monitoring and easier configuration.
* **Accurate CMDB Updates:** Provides timely and detailed updates to the CMDB, ensuring reliable configuration data for IT operations and service management.

## Practical Considerations

* Initial execution may take several hours to process changes from the previous four hours.
* Execution frequency can be customized down to a minimum of one minute, but scaling requires sufficient worker nodes.
* Failed event domain assignment can be controlled using system properties to restrict event visibility.
* Migration from Microsoft Azure alert-driven discovery to Azure change processing is recommended to leverage performance and setup advantages.  
The Azure change processing feature collects information about Microsoft Azure resources that have undergone a life-cycle state change or configuration change near real time. Then, it uses the
collected information to update the Configuration Management Database (CMDB).

The Azure Change Processing scheduled jobs query the Azure API and collect the resource change information. During each execution cycle, the scheduled job collects information about all the resources that have changed
after the last Azure Change Processing cycle. After collecting the change information, the Azure Change Processing uses response mappings to update the change information in the CMDB. During the next discovery, Cloud Discovery triggers appropriate patterns, if available, and populates detailed resource information in the CMDB.

By default, the Azure change processing scheduled jobs run in every 5 minutes. If necessary, update the execution frequency of the schedule according to your needs. Set the execution frequency within the minimum value of one
minute.

When you execute the Azure change processing for the first time, it may run a few hours. This is due to processing resource changes that occurred in the last four hours. If you want to increase the default schedule execution period, ensure that enough worker nodes are available to execute the schedule.

During event processing, the Cloud Event Scheduler identifies the domain of the associated service account and assigns it to the event. If domain identification fails before processing, the event can remain
unassigned and be visible across all domains. To limit the visibility of failed events to the service-provider administrator, set the sn_cmp.error_events.default_domain property to the sys_id of the
service-provider domain.  
Note:  
Azure change processing can fetch resource change information only from the service accounts created by the discovery_admin or sn_cmp.cloud_admin.

Update your Discovery and Service Mapping Patterns
plugin on ServiceNow Store to have at least 1.21.0 version of Azure Change Processing. See the upgrade scenario in [KB1705862](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1705862)  
Starting in the Discovery and Service Mapping Patterns 1.21.0 version, the scheduled jobs were enhanced and renamed:

* The Azure Process Changes scheduled job was renamed as ACP Pull Changes.
* The CPG Build Azure Changes IRE Payload scheduled job was renamed as ACP Process Changes.
{#azure-change-processing__ul_c2h_npc_ddc}

## ACP tables {#azure-change-processing__section_nw2_jtm_2dc}

Starting with Discovery and Service Mapping Patterns 1.21.0 version, Azure change processing enhancement populates the following tables:

ACP Resource Type \[sn_itom_pattern_acp_supported_resource_types\]

:   You can use this table to review all supported resource types, add a resource type for change processing, and disable or enable the processing for a certain resource.

    For more information on adding support for an Azure resource type, see [Add change processing support for an Azure resource type](https://www.servicenow.com/docs/UGH73I~nIYhYwDWPAdlOYQ "Add Azure change processing support for an Azure resource type per the needs of your organization.").  
    Key fields:

    * Resource Type.
    * Query: The resource graph query that retrieves changes from Azure.
    * Active: Indicates if the resource type is actively being queried.
    {#azure-change-processing__ul_lnn_jzm_2dc}

ACP Order Status \[sn_itom_pattern_acp_order_status\]

:   This table tracks the status of the Azure Resource Graph query for each resource type, based on the associated credentials that are used for querying Azure. You can use this table to review the processing status. For more information about the query, see [KB1705862](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1705862).

    Key fields:

    * Resource Type.
    * Credential: the specific credential used for pulling changes.
    * Last Processed time.
    * Status: Tracks the success or failure of the event pull process. After the next ACP Pull Changes scheduled job, this status will be updated based on the CMP Order status.
    * CMP Order: Reference to the CMP Order \[sn_cmp_order\] field, which provides details about the current order progress and outcome.
    {#azure-change-processing__ul_e3j_yym_2dc}

ACP Resource Change \[sn_itom_pattern_acp_resource_change\]

:   This table records changes detected in Azure resources. The \[sn_cmp_resource_changes_payload_info\] table that used to store this info before the 1.21.0 version is no longer available.

    Key fields:

    * Resource ID: the unique identifier for the changed resource in Azure.
    * Change Payload: a snapshot of the attributes of interest for the resource.
    * Order: A reference to the CMP Order \[sn_cmp_order\] field that pulled the change.
    * Resource Status: A reference to the ACP Resource Status table to track the processing status of the change.
    * State: the current processing state of the change. If the state is marked as 'Error', review the associated Resource Status record for further details.
    {#azure-change-processing__ul_ftb_rxm_2dc}

ACP Resource Status \[sn_itom_pattern_acp_resource_status\]

:   This table tracks the overall status of resource processing.

    Key fields:

    * Resource ID: the identifier for the resource being processed.
    * Status: the processing state. The states are: Ready, In Progress, Failure, and Success.
    * Error Message: If the processing failed, this field contains details about the error.
    {#azure-change-processing__ul_b33_lym_2dc}

## Supported Azure resource types and changes {#azure-change-processing__section_xrg_n23_5wb}

Azure Change Processing tracks a set of resource properties for each supported resource type. When a change is detected in one of these properties, Azure Change Processing retrieves an updated snapshot of the resource from Azure. It then processes the snapshot in the CMDB to reflect the change.  
{#azure-change-processing__table_w3g_w23_5wb__entry__2}

| Resource type | Resource Property |
|-|-|
| Microsoft.Compute/virtualMachine | * CreateOrDeleteVm : properties.changeType in ('Create','Delete') * ChangeStatus: (properties.extended.instanceView.powerState.code) in ('PowerState/running', 'PowerState/stopped', 'PowerState/deallocated')) * ChangeDisk: properties.storageProfile * ChangeTag: tags.\* * ChangeNetworkInterface : properties.networkProfile.networkInterfaces {#azure-change-processing__ul_bg4_cf3_5wb} |
| Microsoft.Compute/disks | * CreateOrDeleteDisk : properties.changeType in ('Create','Delete') * ChangeState : properties.diskState * ChangeSize : properties.storageProfile * ChangeTag : tags.\* {#azure-change-processing__ul_lqq_ff3_5wb} |
| Microsoft.Network/networkSecurityGroups | * CreateOrDeleteNsg : properties.changeType in ('Create','Delete') * ChangeTag : tags.\* {#azure-change-processing__ul_ivp_lf3_5wb} |
| Microsoft.Network/networkinterfaces | * CreateOrDeleteNic : properties.changeType in ('Create','Delete'), * changePrimary : properties. properties.primary * ChangeIp : properties.ipConfigurations\[0\]' * ChangeTag : tags.\* {#azure-change-processing__ul_fg3_g3c_fdc} |
| Microsoft.Network/publicIPAddresses | * CreateOrDeleteIp : properties.changeType in ('Create','Delete'), * ChangeIpAddress : 'properties.ipaddress', * ChangeFqdn : properties.dnsSettings.fqdn * ChangeIpConfig : properties.ipConfiguration * ChangeTag : tags.\* {#azure-change-processing__ul_fn1_pf3_5wb} |
[ ]

{#azure-change-processing__table_w3g_w23_5wb}

## Advantages of the Azure change processing {#azure-change-processing__section_jnh_zf3_5wb}

The Azure change processing offers the following advantages over the Microsoft Azure alert-driven discovery:

* Improved performance and reduced probability of Azure API throttling
* Simple setup
{#azure-change-processing__ul_xky_cg3_5wb}

Improved performance and reduced probability of Azure API throttling
:   The Microsoft Azure alert-driven discovery triggers a targeted discovery for each affected resource. Therefore, when the ServiceNow AI Platform receives a huge number of alerts, the targeted discovery may cause the Azure APIs to throttle. As a result, the alert processing performance of the ServiceNow AI Platform may decline. In contrast, the Azure change processing doesn't trigger targeted discovery for each affected resource. Instead, it uses response mappings to update the CMDB per the available change information. During the next discovery, Cloud Discovery triggers appropriate patterns, if available, and populates detailed resource information in the CMDB. Therefore, Azure change processing improves the change handling performance of the ServiceNow AI Platform and reduces the probability of Azure API throttling.

Simple setup
:   The Microsoft Azure alert-driven discovery uses a webhook to send the alerts to the ServiceNow AI Platform. As the Azure cloud generates alerts at the subscription level, the Microsoft Azure alert-driven discovery needs a webhook for each subscription you want to monitor. In contrast, Azure change processing uses CAPI and MID Server to interact with the Azure resource changes API. The API can provide change information at the management group level. Therefore, Azure change processing removes the need for webhooks and simplifies the setup.

You can [configure Azure change processing](https://www.servicenow.com/docs/AWDwehXrJ9BpVYNj8P6KcA "Configure the Azure change processing to collect resource change information from the Microsoft Azure cloud and use it to update the Configuration Management Database (CMDB).") to get resource change information from the Microsoft Azure cloud and use it to update the CMDB.

If you're using the Microsoft Azure alert-driven discovery, then you can [migrate to Azure change processing](https://www.servicenow.com/docs/rwr5shk85xDzrctsQRmz8Q "Migrate to Azure change processing to improve the change processing performance of the ServiceNow AI Platform and take advantage of the simplified setup.") to improve the change processing performance of the ServiceNow AI Platform and take advantage of the simplified setup.
**Related reference**   

* [Microsoft Azure Cloud discovery using patterns](https://www.servicenow.com/docs/e2521~KHAw8EO7j1nC9QMA "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")  
**Related topics**   

* [https://support.servicenow.com/kb?id=kb_article_view\&sysparm_article=KB1705862](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1705862)