Products

nav.hidden, nav ul [x-cloak], nav ul li ul { display: block !important; } This website requires Javascript for some parts to function properly. Your experience may vary.

Cookie Settings

This site uses cookies that need consent.

Functional First party cookies are needed for the website to function. These can't be turned off.

Products / Azure Connector

Azure Source Connector for CI Synchronizer

Microsoft Azure is a comprehensive cloud computing platform that empowers organisations to build, deploy, and manage a wide range of applications and services through a global network of data centers with capabilities spanning virtual computing, storage, networking, databases, and AI.

Seamlessly integrate CI Synchronizer with Azure to populate your Configuration Management Database (CMDB) with the assets contained in your Azure infrastructure to ensure you have complete visibility of your Azure operational landscape.

The integration requires minimal configuration to connect to your Azure Tenancy. All that is required is an Azure AD application registration with access to your subscriptions and you are up and running.

Supports multiple Azure Tenancies
Supports delta synchronisations by maintaining checksums of the last successfully synchronised version of every record.

Comprehensive Coverage

Currently extracts and synchronises 10 Azure resource classes with more to come.

Dynamically Generates CI-to-CI Relationships

Detects 22 discrete dependency types between your Azure resources and generates the corresponding relationships in your CMDB.

Tags Mapping

Provides for the configuration of tag value mapping to field values. Talk to us about how our customers have been able to populate the Lansweeper CI record's environment, support group and resource owner from their Azure tag values.

Detects Instantiated Computers

Automatically finds corresponding computer CI records that have been synchronised from other discovery sources and creates a relationship in the destination system so the dependency on the underlying virtualisation host is known in your CMDB.

Relationships

Frequently Asked Questions

CI Synchronizer (Professional Edition) provides a comprehensive solution for CMDB automation with out-of-the-box support for a large range of asset/record types and CI-to-CI relationships, a range of source and destination connectors, and rapid deployment.

CI Synchronizer (Enterprise Edition) offers everything in Professional Edition along with advanced customisation options, several additional features such as Application Service Mapping, Digital Certificate syncing, additional related lists and and support for larger and more complex data synchronisation requirements. Enterprise Edition also allows for bespoke configuration of CMDB data rules and support for additional Azure regions.

Compare CI Synchronizer editions

Many! Check out each source connector page for details of the supported assets and other records.

Yes. CI Synchronizer can detect which source records have changed since the previous synchronisation job and only sync the newly changed source data.

Throughput is affected by factors outside of the control of CI Synchronizer, however we see a typical throughput of between 200,000 and 400,000 records per hour (and even higher rates are possible).

Yes. CI Synchronizer has a highly customisable rules engine. Such changes are made by Syncfish.

Yes. Please use the “Organise a Demo” button or visit the Contact Us page to book a time to meet with one of the Syncfish team.

No. Each customer is provisioned with a dedicated CI Synchronizer instance.

Ultimately the customer decides, however Syncfish recommends hosting each customer instance physically close to the location of their ServiceNow instance (for best performance). It can be hosted in most/all Azure Regions globally (it is still hosted/managed/maintained by Syncfish, but the customer decides which geography it is physically located in).

No. The source asset data (read from the relevant source system by one of the CI Synchronizer connectors) is transited through your dedicated CI Synchronizer instance then deleted after it’s been processed into ServiceNow.