How to Integrate Multiple Azure Tenants/Portals with a Single ServiceNow Instance?

[NISCHITHHEGDE]

Hi Community,

I am looking for guidance on integrating multiple Azure tenants with a single ServiceNow instance.

Our requirement is to connect more than one Azure tenant to the same ServiceNow instance for functionalities such as user provisioning, authentication, or other Azure-ServiceNow integrations.

I would like to understand:

1. Is it supported to integrate multiple Azure tenants with a single ServiceNow instance?
2. What is the recommended approach for configuring multiple Azure connections?
3. Are separate applications, credentials, or integration users required for each Azure tenant?
4. Are there any limitations or best practices regarding security and maintenance?
5. Has anyone implemented a similar setup and can share their experience?

Any documentation, implementation guidance, or lessons learned would be appreciated.

Thank you.

[NISCHITHHEGDE]

This requirement is related to the Microsoft Teams–ServiceNow integration in a domain-separated ServiceNow instance that serves multiple clients. Since each client may have its own Microsoft Teams tenant, we are evaluating whether a single ServiceNow instance can be integrated with multiple Teams tenants simultaneously while maintaining proper domain separation and tenant isolation.

We would like to understand the supported architecture, configuration approach, and any limitations or best practices for implementing and managing such a multi-tenant integration scenario.

[Tanushree Maiti]

Hi @NISCHITHHEGDE 

High level idea:

1. If you are using the Azure Entra spoke, you can leverage the out-of-the-box (OOB) flow actions.
2. Create OAuth profiles and connection aliases separately for each tenant/environment. For example, use one connection alias for non-production and a different one for production.
3. In Flow Designer, use an If condition to determine the instance/environment and invoke the appropriate flow action.

Example:

• If the instance is Production:
  • Use the flow action configured with the Production connection alias.
• If the instance is Non-Production:
  • Use the flow action configured with the Non-Production connection alias mapped to a different Azure tenant.