Microsoft 365

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 / Microsoft 365

Microsoft 365 (M365) is a comprehensive platform providing a wide range of services used by enterprises across the globe. Microsoft Entra ID underpins M365 with authentication and authorization information which can be leveraged to enhance your ITSM platform and associated business processes.

The CI Sync Microsoft 365 connector reads multiple object types to create a combination of records and relationships in your CMDB and other related tables in within ServiceNow. This enables novel use cases to be leveraged by your organization to improve visibility and management of MS Team (SharePoint) sites as an example.

The CI Sync M365 connector can take advantage of any data available through the Microsoft 365 and Entra ID APIs. Syncfish are keen for more customer use cases to expand the connector and the benefits it can provide to your ServiceNow platform.

Take control of SharePoint Site proliferation

The CI Sync M365 connector synchronizes SharePoint sites to your CMDB as Website CIs. CI Sync goes a step further by synchronizing the SharePoint Owner Group records into ServiceNow and automatically correlates the Owner Group members between the M365 user records and your ServiceNow user table. The combination of these features means you can drive automated workflows to perform SharePoint lifecycle management and drive decommissioning of unnecessary/unused SharePoint sites, particularly the SharePoint sites created by Microsoft Teams.

Out of Office records so tickets aren’t routed to staff on leave

You can use the M365 connector to sync Out of Office records from Outlook as Schedule Records in ServiceNow. Having this Schedule Records automatically generated means ServiceNow can be configured so it’s sensitive to the availability of ticket resolvers (i.e. to avoid tickets being routed to resolvers who are on leave). This functionality can be made sensitive to only target certain groups of M365 users (i.e. known groups of resolvers).

Relationships

Roadmap Connectors

AirWatch (Workspace ONE)

Lansweeper Cloud (Native)

Meraki

Microsoft Defender

SentinelOne

Tanium

Frequently Asked Questions

CI Synchronizer Professional Edition provides a streamlined, out-of-the-box solution for businesses looking for efficient, hassle-free CMDB synchronisation without the need for extensive customisation.

CI Synchronizer Enterprise Edition offers advanced customisation and high-volume data handling capabilities, perfect for organisations with complex synchronisation needs and custom configuration requirements.

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. Amendment of some Standard (simple) default Data Sync Rules can be performed via the CI Sync Web User Interface and supported with Knowledge Base articles. Amendment of Advanced Data Sync Rules or creation of Custom Data Sync Rules requires an “Extended Implementation and Ongoing Support Plan” available at an additional cost to your CI Sync Subscription Plan.

Visit the Support page for details on amending the Default CI Sync Data Sync Rules relative to the support plan (including no plan) offered by Syncfish.

Yes. Please fill and submit the Book a Demo form to set up 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.