--- 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 WebSite # Azure WebSite pattern-based discovery {#ariaid-title1} Release version: Australia Updated June 18, 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 WebSite pattern-based discovery The Azure WebSite pattern-based discovery in ServiceNow enables automated identification and mapping of Azure App Service web applications within your cloud environment. This pattern specifically targets Azure App Service web apps, helping you maintain an accurate and up-to-date CMDB for these resources. For discovering Azure Functions, a separate pattern is available. Show full answer Show less To use this pattern effectively, ensure you meet Microsoft Azure discovery prerequisites and configure discovery schedules properly, especially when working with Azure GovCloud environments. ## Key Features * **CMDB Population:** The pattern collects detailed data about Azure App Service web applications, populating the `cmdbcicloudwebserver` and `cmdbciipaddress` tables with key attributes such as app name, unique Azure object ID, FQDN, inbound IP address, state, operational status, vendor, and install status. * **Relationship Mapping:** It creates important relationships between discovered web servers, Azure datacenters, and associated IP addresses to accurately reflect hosting and ownership within the CMDB. Relationships are only created for web apps with valid inbound IP addresses and FQDNs. * **Tag Collection:** The pattern collects Azure tags associated with web applications and stores them in the `cmdbkeyvalue` table, enabling enhanced organization and filtering of your CMDB records. * **Service Mapping Integration:** During top-down discovery, the Azure WebSite TD pattern identifies connections to backend services such as Microsoft SQL Server, MySQL, Redis, and NoSQL databases like Cosmos DB, supporting comprehensive service maps. * **GovCloud Support:** Special configuration is required to discover Azure GovCloud accounts, specifically using appropriate datacenter URLs when setting up Azure service accounts. ## Key Outcomes * Accurate and enriched CMDB records for Azure App Service web applications, including essential attributes and relationships that reflect real-world infrastructure. * Enhanced visibility into Azure web application environments, supporting impact analysis, compliance, and operational management. * Improved service mapping through discovery of dependencies on databases and caches connected to Azure web apps. * Ability to leverage Azure tags for categorization and reporting within ServiceNow CMDB. Discovery and Service Mapping Patterns finds Azure App Service web applications in 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. This pattern discovers Azure App Service web applications only. For Azure Functions discovery, see [Microsoft Azure Functions discovery with Patterns](https://www.servicenow.com/docs/GnLTuZfQgRXkhX65Cio1Hw "The Discovery and Service Mapping Patterns application uses the Azure - Functions (LP) and Azure - Functions TD Patterns to discover Azure Functions apps and map them in the context of application services. 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-website-pattern__section_rpj_fj2_bgc} Verify the Microsoft Azure discovery prerequisites : 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."). Configure the Discovery schedule to support GovCloud : 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-website-pattern__configure-govcloud-azure-dd} {#azure-website-pattern__configure-govcloud-azure-dd} ## Data collected by Discovery during horizontal discovery {#azure-website-pattern__section_ggp_ql2_bgc} Discovery populates the data in the CMDB when running the Azure WebSite (LP) pattern. {#azure-website-pattern__table_webserver__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the Azure web application. | | Object ID \[object_id\] | A unique identifier, allocated by Azure for this resource. | | Fully qualified domain name \[fqdn\] | The fully qualified domain name (FQDN) of the web application. | | IP Address \[ip_address\] | The inbound IP address of the web application. | | State \[state\] | The current state of the web application. Possible values are: available or terminated. | | Operational status \[operational_status\] | The operational status of the web application. The value is 1 (Operational) when the state is available, or 2 (Non-Operational) otherwise. | | Vendor \[vendor\] | The vendor of the web application. The value is set to Microsoft. | | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | [Table 1. Cloud WebServer \[cmdb_ci_cloud_webserver\]] {#azure-website-pattern__table_webserver} {#azure-website-pattern__table_ip_address__entry__2} | Field | Description | |-|-| | Name \[name\] | The name of the web application associated with this IP address. | | IP Address \[ip_address\] | The inbound IP address of the web application. | | Fully qualified domain name \[fqdn\] | The fully qualified domain name (FQDN) of the web application. | | Netmask \[netmask\] | The netmask of the IP address. The value is set to 0.0.0.0. | | Vendor \[vendor\] | The vendor of the web application. The value is set to Microsoft. | [Table 2. IP Address \[cmdb_ci_ip_address\]\*] {#azure-website-pattern__table_ip_address}\* Populated only when the web application has a non-empty inbound IP address. ## CI relationships and references {#azure-website-pattern__section_dc4_ghc_dgc} The Azure WebSite (LP) pattern creates the following relationships and references to support Azure WebSite discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table. {#azure-website-pattern__table_relationships__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud WebServer \[cmdb_ci_cloud_webserver\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] | | Cloud WebServer \[cmdb_ci_cloud_webserver\] | Owns::Owned by | IP Address \[cmdb_ci_ip_address\]\* | [Table 3. CI relationships] {#azure-website-pattern__table_relationships}\* This relationship is created only when the web application has a non-empty inbound IP address and an FQDN. {#azure-website-pattern__table_ci_references__entry__3} | CI | Field | Referenced CI | |-|-|-| | Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Cloud WebServer \[cmdb_ci_cloud_webserver\] | [Table 4. CI references] {#azure-website-pattern__table_ci_references} ## Azure Tag discovery {#azure-website-pattern__section_lyw_zhc_dgc} The Azure WebSite (LP) pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-website-pattern__table_tags__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | | Configuration item \[configuration_item\] | References the Cloud WebServer \[cmdb_ci_cloud_webserver\] table. | [Table 5. Key Value \[cmdb_key_value\]] {#azure-website-pattern__table_tags} ## Connections found by Service Mapping during top-down discovery {#azure-website-pattern__section_m2h_n3p_skc} The Azure WebSite TD pattern discovers the following connections during top-down discovery: Microsoft SQL Server, MySQL, Redis, and NoSQL (Cosmos DB).