--- 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 App Service App Service Plan # Azure App Service App Service Plan pattern-based discovery {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 App Service App Service Plan pattern-based discovery The Azure App Service App Service Plan pattern-based discovery in ServiceNow enables automated identification and mapping of Azure App Service Plans within your cloud environment. This discovery leverages the Discovery and Service Mapping Patterns application to populate detailed configuration and inventory data into both CMDB and non-CMDB tables, enhancing visibility and management of Azure App Service resources. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure App Service Plan discovery pattern is disabled by default and requires activation. Starting from Visibility Content version 6.28.0, enabling or disabling patterns no longer counts as a customization and will receive regular updates. * **Permissions and Prerequisites:** Proper REST API permissions must be granted, guided by the Cloud Discovery patterns spreadsheet which includes pattern names, CI classes, and documentation links. Additionally, Microsoft Azure discovery prerequisites must be met to ensure successful discovery. * **Resource Inclusion List:** To avoid duplicate discoveries, ensure relevant resources are not listed in the Resource Inclusion List \[sacloudinventoryresourcewhitelist\] table. * **Support for Azure GovCloud:** Discovery of Azure GovCloud (US) accounts requires configuring the Azure service account with a datacenter URL specific to GovCloud. * **Data Population:** Discovered data is stored in both CMDB and non-CMDB tables: * **Non-CMDB Tables:** The pattern populates detailed inventory data in Azure-specific tables accessible through the ServiceNow navigation. * **CMDB Tables:** Key configuration items are stored in the Cloud App Server \[cmdbcicloudappserver\] table, including operational status, location, and resource type. * **CI Relationships:** The pattern establishes relationships among configuration items such as Cloud App Servers, Resource Groups, and Azure Datacenters, supporting comprehensive service mapping and impact analysis. * **Tag Discovery:** Azure resource tags are collected and stored in the Key Value \[cmdbkeyvalue\] table, enabling tagging-based management and reporting. ## Practical Benefits for ServiceNow Customers * Gain accurate and up-to-date visibility into your Azure App Service Plans and their configurations within your CMDB. * Enhance cloud asset management and service mapping accuracy by leveraging discovered relationships between App Service Plans and Azure infrastructure components. * Support compliance and governance requirements by maintaining detailed inventory data, including tags and operational states. * Reduce manual effort and errors by automating discovery with pattern-based updates delivered quarterly. * Ensure smooth integration of Azure GovCloud resources into your overall cloud discovery strategy. Discovery and Service Mapping Patterns finds Azure services on your cloud environment. Discovering some of these resources might 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-app-service-plan__section_ipy_53n_jfc} Verify the REST API permissions : Download the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.{#azure-app-service-plan__cloud-discovery-api-ph-short-prereq} Verify the Microsoft Azure discovery prerequisites{#azure-app-service-plan__verify-azure-discovery-prerequisites-dlentry} : For more information, see the prerequisites section in [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."). Remove resources from the Resource Inclusion List table{#azure-app-service-plan__remove-resource-inclusion-list-azure} : Verify that the relevant resource isn't listed in the Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table to avoid duplicate discovery. For more information on removing resources from the Resource Inclusion List, see [Microsoft Azure resource inventory discovery](https://www.servicenow.com/docs/tO3nNqXv4zOe7q99krvAnA "The ServiceNow Discovery application uses the Azure Resource Inventory (LP) pattern to find resources available through Azure that don’t have a dedicated pattern. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store."). Enable the relevant pattern{#azure-app-service-plan__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://www.servicenow.com/docs/aypCYVQdO8oFebLMLEI89g "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-app-service-plan__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-app-service-plan__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://www.servicenow.com/docs/XKQpJvxWTKNL58XCkRHVxA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-app-service-plan__configure-govcloud-azure-dd} {#azure-app-service-plan__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-app-service-plan__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populate data in the non-CMDB table when running the Azure - App Service App Service Plan - 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-app-service-plan__section_aq4_qkq_hfc__entry__2} | Field | Description | |-|-| | Kind \[kind\] | The category or specialization of the resource, often specific to certain Azure services. | | Location \[location\] | The Azure region where the resource is hosted. | | Object Id \[object_id\] | The unique identifier for the resource. | | Provisioning State \[provisioning_state\] | The current provision status of the resource. | | Resource Group \[resource_group\] | Name of the resource group. | | Status \[status\] | The operational status or health of the resource. | | Subscription Id \[subscription_id\] | The subscription ID. | | Tenant Id \[tenant_id\] | The identifier of the Azure Active Directory tenant associated with the resource. | | Tier \[tier\] | The performance level or pricing tier assigned to the resource. | | Configuration Item \[configuration_item\] | References the Cloud App Server \[cmdb_ci_cloud_appserver\] table. | [Table 1. Azure App Service - App Service Plan \[cmdb_azure_app_service_app_service_plan\]] ## Data stored in CMDB tables Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - App Service App Service Plan - Extended Inventory(LP) pattern. {#azure-app-service-plan__entry__24} | Field | Description | |-|-| | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Location \[location\] | The Azure region where the resource is hosted. | | Name \[name\] | The name assigned to the resource. | | Object ID \[object_id\] | The unique identifier for the resource. | | Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. | | Type \[type\] | Type of resource. The value is set to microsoft.web/serverfarms. | [Table 2. Cloud App Server \[cmdb_ci_cloud_appserver\]] ## CI relationships The pattern creates these relationships to support discovery. {#azure-app-service-plan__entry__39} | CI | Relationship | CI | |-|-|-| | Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud App Server \[cmdb_ci_cloud_appserver\] | | Cloud App Server \[cmdb_ci_cloud_appserver\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] | | Azure App Service - App Service Plan \[cmdb_azure_app_service_app_service_plan\] | References | Cloud App Server \[cmdb_ci_cloud_appserver\] | [ ] ## Azure tag discovery {#azure-app-service-plan__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-app-service-plan__table_axq_spc_y2c__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | [Table 3. Key Value \[cmdb_key_value\]] {#azure-app-service-plan__table_axq_spc_y2c} *[\>]: and then