---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Azure Automation Account

# Azure Automation Account pattern-based discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Automation Account pattern-based discovery

The Azure Automation Account pattern-based discovery in ServiceNow enables automated detection and mapping of Azure Automation Account resources within your cloud environment.
This discovery helps populate key configuration management database (CMDB) and non-CMDB tables, allowing you to maintain an accurate and comprehensive view of your Azure automation resources.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The Azure Automation Account discovery pattern is disabled by default. Starting with Visibility Content version 6.28.0, enabling or disabling patterns is no longer treated as a customization, ensuring patterns receive updates after upgrades while retaining active status.
* **Discovery Prerequisites:** Proper Microsoft Azure discovery prerequisites must be met, including configuration of Azure service accounts. Special configuration is required for discovering Azure GovCloud (US) accounts by using the appropriate datacenter URL.
* **Data Population:** The discovery populates data into both CMDB and non-CMDB tables:
  * **Non-CMDB Table:** The `cmdbazureautomationautomationaccount` table stores detailed Azure Automation Account properties such as identity, location, public network access, subscription and tenant IDs, and authentication settings.
  * **CMDB Table:** The `cmdbcicmpresource` table stores general cloud resource information like install status, operational status, resource type, and location.
* **CI Relationships:** The pattern automatically creates relationships to represent resource group containment, hosting by Azure datacenters, and references between Azure Automation Account and cloud resource CIs.
* **Tag Discovery:** Azure resource tags are collected and stored in the `cmdbkeyvalue` table, capturing tag names and values to support richer metadata management.

## Practical Benefits for ServiceNow Customers

* Enables accurate, up-to-date discovery of Azure Automation Accounts, critical for managing automation workflows and cloud resource compliance.
* Supports comprehensive CMDB population with both detailed Azure-specific attributes and general cloud resource data for effective configuration management.
* Facilitates discovery in specialized Azure environments such as GovCloud by allowing customized service account configurations.
* Maintains relationships among discovered CIs, improving service mapping, impact analysis, and operational visibility.
* Captures Azure tags to enhance asset categorization and reporting within ServiceNow.  
Discovery and Service Mapping Patterns finds Azure services on your cloud environment. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Pattern-based discovery and mapping requirements {#azure-automation-account__section_ipy_53n_jfc}

Verify the Microsoft Azure discovery prerequisites{#azure-automation-account__verify-azure-discovery-prerequisites-dlentry}
:   For more information, see the prerequisites section in [Microsoft Azure Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Enable the relevant pattern{#azure-automation-account__enable-pattern-reuse-dlentry}
:   The pattern for this service is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating a pattern won't be considered a customization, and it will continue to receive updates. Patterns that were previously activated or deactivated will reset to the latest predefined version after upgrading while retaining the last active field value. For more information on enabling patterns, see [Activate a disabled pattern](https://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-automation-account__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-automation-account__configure-govcloud-azure-dlentry}
:   Discovering Azure GovCloud (US) accounts requires using a datacenter URL when setting up an Azure service account. For more information, see [Set up Azure service accounts](https://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-automation-account__configure-govcloud-azure-dd}
{#azure-automation-account__configure-govcloud-azure-dd} Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

## Data stored in non-CMDB tables {#azure-automation-account__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Automation Account - Extended Inventory(LP) pattern.

You can review the non-CMDB
Azure tables by navigating to AllConfigurationAzure. You can also search the navigation filter for the specific pattern name.  
{#azure-automation-account__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Disable Local Auth \[disable_local_auth\] | A setting indicating whether local authentication is disabled for the resource. |
| Identity \[identity\] | The managed identity associated with the resource. |
| Location \[location\] | The geographical location where the resource is hosted. |
| Object Id \[object_id\] | The unique identifier of the resource. |
| Public Network Access \[public_network_access\] | The configuration status of public network access for the resource. |
| Resource Group \[resource_group\] | Name of the resource group. |
| Subscription Id \[subscription_id\] | The subscription ID. |
| Tenant Id \[tenant_id\] | The identifier for the Azure Active Directory tenant associated with the resource. |
| Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. |
[Table 1. Azure Automation Account \[cmdb_azure_automation_automation_account\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Automation Account - Extended Inventory(LP) pattern.  
{#azure-automation-account__entry__22}

| Field | Description |
|-|-|
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Location \[location\] | The geographical location where the resource is hosted. |
| Name \[name\] | The name of the resource. |
| Object ID \[object_id\] | The unique identifier of the resource. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
| Resource type \[resource_type\] | Type of resource. The value is set to microsoft.automation/automationaccounts. |
[Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]]

## CI relationships

The pattern creates these relationships to support discovery.
{#azure-automation-account__entry__37}

| CI | Relationship | CI |
|-|-|-|
| Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud Resource \[cmdb_ci_cmp_resource\] |
| Cloud Resource \[cmdb_ci_cmp_resource\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Azure Automation Account \[cmdb_azure_automation_automation_account\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] |
[ ]

## Azure tag discovery {#azure-automation-account__section_ezc_jwt_jfc}

The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-automation-account__table_axq_spc_y2c__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
[Table 3. Key Value \[cmdb_key_value\]]

{#azure-automation-account__table_axq_spc_y2c}

*[\>]: and then


