Azure Network and Subnet pattern-based discovery
Summarize
Summary of Azure Network and Subnet pattern-based discovery
The Azure Network and Subnet pattern-based discovery in ServiceNow identifies and maps Azure virtual networks, subnets, and virtual network peerings within your cloud environment. This discovery relies on the Discovery and Service Mapping Patterns application, which should be kept up to date to ensure comprehensive resource detection. It supports both standard Azure and Azure GovCloud (US) environments, with specific configuration needed for GovCloud accounts.
Show less
Key Features
- Discovery Prerequisites: Ensure Microsoft Azure discovery prerequisites are met as detailed in the Azure Cloud discovery patterns documentation.
- GovCloud Support: Requires setting a datacenter URL when configuring Azure service accounts for GovCloud discovery.
- Data Collection: The discovery pattern populates key CMDB tables—Cloud Network (
cmdbcinetwork), Cloud Subnet (cmdbcicloudsubnet), and Virtual Network Peering (cmdbcivnetpeering)—with detailed attributes including name, unique Azure object IDs, state, CIDR blocks, and install status. - CI Relationships: The pattern creates relationships to represent containment and hosting among Azure Datacenters, Resource Groups, Networks, Subnets, and Peerings, which helps visualize network hierarchy and dependencies.
- Tag Discovery: Azure tags associated with networks are harvested and stored in the Key Value (
cmdbkeyvalue) table, linking tag keys and values back to respective Cloud Network CIs for enhanced metadata management.
Practical Benefits for ServiceNow Customers
By implementing this discovery pattern, customers gain:
- A comprehensive and up-to-date view of their Azure network infrastructure within the ServiceNow CMDB.
- Visibility into the hierarchical relationships between Azure resources, improving impact analysis and change management.
- Enhanced metadata capture through tag collection, enabling better categorization and reporting of cloud resources.
- Support for Azure GovCloud environments, ensuring compliance and visibility in specialized cloud deployments.
Overall, this discovery pattern enables efficient management and governance of Azure network components directly within ServiceNow, supporting operational excellence and cloud optimization efforts.
Discovery and Service Mapping Patterns finds Azure virtual networks, subnets, and virtual network peerings 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
- Verify the Microsoft Azure discovery prerequisites
- For more information, see the prerequisites section in Microsoft Azure Cloud discovery using patterns.
- 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.
Data collected by Discovery during horizontal discovery
Discovery populates the data in the CMDB when running the Azure - Network and Subnet (LP) pattern.
| Field | Description |
|---|---|
| Name [name] | The Name or ID if no Name is specified for the cloud network. |
| Object ID [object_id] | A unique identifier, allocated by Azure for this resource. |
| State [state] | The current state of the network. |
| Cidr [cidr] | Classless Inter-Domain Routing (CIDR) representation of the network. For example: 10.0.0.0/24. |
| Install Status [install_status] | Install status of the resource. Default value is Installed. |
| Field | Description |
|---|---|
| Name [name] | The Name or ID if no Name is specified for the cloud subnet. |
| Object ID [object_id] | A unique identifier, allocated by Azure for this resource. |
| State [state] | The current state of the subnet. |
| CIDR [cidr] | CIDR representation of the subnet. For example, 10.0.0.0/24. |
| Install Status [install_status] | Install status of the resource. Default value is Installed. |
| Field | Description |
|---|---|
| Name [name] | The Name or ID if no Name is specified for the virtual network peering. |
| Object ID [object_id] | A unique identifier, allocated by Azure for this resource. |
| State [state] | The current state of the virtual network peering. |
| Use Remote Gateways [use_remotegateways] | Indicates whether remote gateways are used for this peering. |
| Install Status [install_status] | Install status of the resource. Default value is Installed. |
CI relationships
The Azure - Network and Subnet (LP) pattern creates the following relationships and references to support Azure Network and Subnet discovery. References link to records in other tables and don't appear in the CI Relationship [cmdb_rel_ci] table.
| CI | Relationship | CI |
|---|---|---|
| Cloud Network [cmdb_ci_network] | Hosted on::Hosts | Azure Datacenter [cmdb_ci_azure_datacenter] |
| Resource Group [cmdb_ci_resource_group] | Contains::Contained by | Cloud Network [cmdb_ci_network] |
| Cloud Network [cmdb_ci_network] | Contains::Contained by | Cloud Subnet [cmdb_ci_cloud_subnet] |
| Cloud Network [cmdb_ci_network] | Contains::Contained by | Virtual Network Peering [cmdb_ci_vnet_peering] |
| CI | Field | Referenced CI |
|---|---|---|
| Key Value [cmdb_key_value] | Configuration item [configuration_item] | Cloud Network [cmdb_ci_network] |
Azure Tag discovery
The Azure - Network and Subnet (LP) pattern collects tags and populates them in the Key Value [cmdb_key_value] table.
| Field | Description |
|---|---|
| Key [key] | Tag name. |
| Value [value] | Tag value. |
| Configuration item [configuration_item] | References the Cloud Network [cmdb_ci_network] table. |