The Service Graph Connector for Microsoft Azure enables cloud teams to integrate Azure data to the ServiceNow CMDB and ServiceNow workflows quickly, seamlessly, and securely. Designed with Azure security best practices and built on Azure native technologies including Azure Resource Manager and Azure Log Analytics. The Service Graph Connector for Microsoft Azure automates access to populate multiple configuration classes including virtual servers, network infrastructure, and installed software with minimal required credentials. Plug-and-play Service Graph Connectors simplify setup and facilitate quick improvements to business outcomes: reducing costs, automating processes, and optimizing the use of cloud resources.
Key use cases:
- Visibility of cloud resource identities, relationships, and statuses in near real-time
- Deep discovery of applications and software for Asset Management, Application Portfolio Management, and Service Operations outcomes
- Easy to set up
- Complements other Azure cloud discovery
- Populates software details from Azure VMs
- No MID Server required
New
- Life cycle management is supported for service accounts, IP addresses, and tags.
- Updated SNK delimiter and key structure migration are used for Azure CI identification.
- Operating system domain is mapped for imported Azure virtual machines.
- Azure datacenter (location) names are aligned with the naming used by Cloud Discovery patterns.
- Azure virtual desktop instances are classified correctly even when their power state is off. Powered-down VDI resources are now correctly classified and included in imports.
- Managed database, multi workspace, and NIC are now related to their logical datacenter.
- Azure Microsoft SQL managed instances are imported into the CMDB.
- Multiple log analytics workspaces can be imported for a single hardware connection.
Changed
- The connector doesn’t depend on the deprecated WMIC utility when running commands on Windows hosts.
- The field mapping for properties.privateEndpointConnections is removed from Azure Functions.
Fixed
- Resolved the issue where the connector uses a database view that breaks when sys_object_source is moved to a gateway database. (PRB2057749)
- Resolved the issue where a "Found multiple dependent relation items" error occurs when resources are moved between Azure datacenters. (PRB2031891)
- Resolved the issue where the Disk Space field isn’t populated with the correct size during hardware import because the temporary disk size (returned in megabytes) is written to the hardware template without being converted to gigabytes. (PRB2020861)
- Duplicate network interface card (NIC) CIs are created after SNK updates. (PRB2075962)
- The Install status and Disk Space fields are populated with RTE mappings for the Server class and the Computer class. (PRB2029112)
- The install status is now correctly updated for scale set virtual machines. (PRB2058752)
- Resolved the issue where the operational_status of a virtual machine CI reverts from Retired to Deployed after the virtual machine is deleted because the ETL transform script reads only the provisioning state and doesn’t check the change type. (PRB2026420)
- Relationships are created from Kubernetes Clusters and Azure Functions for service accounts. (PRB2072840)
- Resolved the issue where software removal responses that were returned as "modified" created new CIs, resulting in duplicate records. (PRB2010434)
- Resolved the issue where the hardware consolidation job and its underlying database view join filter on PoweredState = ON, which excludes powered-off virtual machines and can lead to incorrect data when the import runs outside business hours. (PRB2027092)
- CIDR information is now correctly populated. (PRB2066702)
- Resolved the issue where a datacenter is incorrectly marked as Passive when it contains only resource groups with no resources. (PRB2025724)
-
Dependencies
- Integration Commons for CMDB
- CMDB CI Class Models
- Discovery and Service Mapping Patterns
- IntegrationHub Datastream action
- Discovery Core
Usage of this Service Graph Connector requires a subscription to Subscription Unit based IT Operations Management (ITOM) Visibility or ITOM Discovery application. Managed IT Resources (as defined in Section 1.1 of the ServiceNow Subscription Unit Overview - https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/servicenow-subscription-unit-overview.pdf) created or modified in the CMDB by this Service Graph Connector, but not yet managed by ITOM Visibility or ITOM Discovery, will increase Subscription Unit consumption within that application. Customers should review their current Subscription Unit consumption within ITOM Visibility or ITOM Discovery to ensure available capacity.