Intune intergration for two ServiceNow instances

[Timothy Stevens]

We are looking to integrate one global instance of Intune with two separate ServiceNow instances. We have one for our US based BU's and one for our EU based BU's. 

Has anyone developed a solution on how to filter Intune data so that it populates into the multiple ServiceNow instances?

[Ravi Gaurav · Accepted solution]

Hi @Timothy Stevens 

Great question  this is something that comes up often in global enterprises that maintain multiple ServiceNow instances but want to leverage a single Intune tenant as the source of truth. Let’s break this down.

Note : This details are my private write-up

• One Intune tenant → manages devices globally.

• Two ServiceNow instances → US BU instance + EU BU instance.

• Need: Route Intune data to the “right” ServiceNow instance so you don’t duplicate or cross-contaminate device data.

1. Intune → Middleware → ServiceNow (Best Practice)

• Use middleware (Azure Logic Apps, Azure Data Factory, API Gateway, MuleSoft, Boomi, etc.) to:

  • Call Intune Graph API.

  • Apply filter logic (region, AD group, device tag, BU metadata).

  • Push data to the appropriate ServiceNow instance.

• Pros:

  • Central control point.

  • Easy to add rules (for example, US devices to US SNOW, EU to EU SNOW).

  • Avoids duplication & reconciliation issues.

• Cons:

  • Extra infra component.

2. Direct Integration with Scoped Filters (More Complex in SNOW)

• Both ServiceNow instances could connect directly to Intune Graph API.

• Each instance applies its own filter based on device attributes (e.g., devicePhysicalLocation, enrolledByUser, azureADGroup).

• Pros:

  • No middleware.

• Cons:

  • Risk of overlap/duplication if filters aren’t watertight.

  • Double load on Intune API (rate limits).

3. Master → Slave Model (One SNOW pulls, pushes to another)

• One ServiceNow instance becomes the “master” pulling from Intune.

• Then, a custom eBonding or Data Replication pushes relevant records to the other SNOW instance.

• Pros:

  • Simple if you already have integration frameworks between SNOW instances.

• Cons:

  • Tight coupling between ServiceNow instances.

  • Adds dependency if one instance is down.

[Timothy Stevens]

Thanks....I will pass this on to our team.

[Pratiksha]

 

Go with guided setup, it has option to configure for multiple instances. 

[MackI]

HI @Timothy Stevens 

This is a large Architectual discussion and the solution will take 8-10 months to implement and test.If you want , I can provide you a document link which can assist you on your decision journey.Are you looking to implement it on Global Company or MNC?

If you like this opinion and your problem is resolved after reviewing and applying it. Please kindly mark this your best answer‌🌠‌ OR  mark it  Helpful ‌⛑‌ if you think that you get some insight from this content relevant to your problem and help me to contribute more to this community. if you mark my answer helpful then ,I can provide you the document for your solution.