Hello Partners,
I would like to ask for your insights on the following implementation scenario:
Case:
Within a holding, there are 15 companies, each located in a different country. Each company operates in a separate Microsoft tenant.
One of the 15 companies is already using Business Central SaaS in the cloud. Let’s refer to this tenant as Tenant X.
Approach 1
Create 14 additional BC production environments in Tenant X, each localized for the appropriate country.
Then, by using B2B collaboration in AzurePortal (Microsoft Entra ID), invite all users from the other tenants to Tenant X (as #EXT#).
At first glance, this seemed to be the best approach — all environments, companies, and data would be centralized within a single tenant, and licensing costs would be lower.
However, after some testing, I discovered issues with native integrations — for example, Microsoft Teams, Outlook, Power Automate, Power Apps, and OneDrive are not working properly in this configuration. I don't know what else could be wrong, where else there could be problems....
From what I understand, these integrations only work correctly if both Business Central and the integrated service/application reside in the same tenant as Business Central. In this setup, Business Central is hosted in Tenant X, but the licenses for the other services/applications are assigned in the users "home tenants" (in the one from which user is invited to tenant X). Although the users are invited to Tenant X via B2B collaboration, the services/applications seem to look for Business Central in the users "home tenant" — not the one they were invited to, and integration cannot be done.
I would like to ask for confirmation whether this is actually how it works? So I can be sure. Or maybe I'm doing something incorrectly?
Approach 2
Create one BC production environment per tenant. 15 tenants = 15 BC production environments.
This would resolve all issues with Microsoft services and it's integrations.
However, this approach would result in higher licensing costs, and data/environments would be dispersed across multiple tenants. In the context of a holding, data consolidation is clearly a key concern.
Approach 3
Migrate all 15 tenants into a single, global tenant, and then create 15 BC production environments there.
This would allow centralized data and environments, full compatibility with Microsoft services, and lower licensing costs.
However, migrating all tenants into one is a highly complex and costly project. There are approximately 10,000 licensed users that would need to be migrated.
And I assume it will be impossible to push it to the client
What are your thoughts on this?
Have you faced a similar case before?
Maybe something I listed here as a concern shouldn't be a concern?
Would you recommend any other approach?
Looking forward to your opinions.
Best regards,
