--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/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 App Service App Service Plan # Azure App Service App Service Plan 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 App Service App Service Plan pattern-based discovery Azure App Service App Service Plan pattern-based discovery enables ServiceNow customers to discover and map Azure App Service Plans within their cloud environment using Discovery and Service Mapping Patterns. This process helps populate critical data into both the Configuration Management Database (CMDB) and non-CMDB tables, enhancing visibility and management of Azure resources. Show full answer Show less ## Key Features * **Pattern Activation:** The discovery pattern for Azure App Service Plans is disabled by default. Activating or deactivating patterns does not count as customization and patterns reset to the latest predefined versions after upgrades while retaining activation status. * **Prerequisites:** Customers must verify Microsoft Azure discovery prerequisites and configure Azure service accounts correctly, especially when discovering Azure GovCloud (US), which requires a datacenter URL setup. * **Data Population:** The pattern populates data into both CMDB and non-CMDB tables: * *Non-CMDB Tables:* Includes detailed resource attributes such as kind, location, provisioning state, resource group, status, subscription ID, tenant ID, and tier for Azure App Service Plans. * *CMDB Tables:* Populates Cloud App Server table with essential fields like install status, location, name, object ID, operational status, and type set to `microsoft.web/serverfarms`. * **CI Relationships:** The pattern establishes key relationships between Cloud App Servers, Resource Groups, and Azure Datacenters to support comprehensive discovery and mapping. * **Azure Tag Discovery:** Tags associated with Azure App Service Plans are collected and stored in the Key Value table for enhanced metadata management. ## Practical Benefits for ServiceNow Customers * Enables automated and up-to-date discovery of Azure App Service Plans, ensuring accurate configuration data in the CMDB. * Supports governance and operational management by capturing detailed resource attributes and relationships. * Facilitates integration with Azure GovCloud environments by providing specific setup instructions for service accounts. * Improves tagging visibility to aid in resource categorization, cost tracking, and compliance efforts. * Simplifies management by aligning pattern activation with ServiceNow upgrade processes, reducing maintenance complexity. 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-app-service-plan__section_ipy_53n_jfc} 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 components discovery using patterns](https://www.servicenow.com/docs/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-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/R5W5GP640V_5uNIhVNRPCw "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/wA59_lRoV_0PzpuODHnNjA "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