Unable to provision Fabric F-Capacity across multi-tenant setup (Azure Subscription in Tenant A, M365/Fabric in Tenant B)

Maverick 20 Reputation points
2026-07-08T13:31:32.05+00:00

Hi everyone,

We are encountering an issue provisioning a Microsoft Fabric F2 capacity in a multi-tenant environment and need architectural clarification.

Our Environment:

Tenant A (Azure Tenant): Hosts our Azure Subscription.

Tenant B (M365 Tenant): Hosts our primary Microsoft 365, Power BI, and Microsoft Fabric infrastructure.

User Setup: The administrator account in Tenant A was recently converted from an Entra ID B2B External Guest to a Internal Member account.

The Issue: Following the user conversion, Azure now successfully recognizes Tenant A when attempting to create a Microsoft Fabric F2 capacity. However, the Fabric capacity cannot be fully provisioned or linked.

When a cloud-only user in Tenant A attempts access, they receive the error: "Your organization doesn't currently allow its users to purchase Microsoft Fabric Free."

Checking Billing → Your products in Tenant A confirms that no Microsoft 365 or Fabric products/licenses are available or listed.

Our Questions:

Architectural Support: Is a split architecture—where the Azure Subscription sits in Tenant A, but the target Fabric/M365 deployment sits in Tenant B—supported for Fabric F (Pay-as-you-go) capacities?

Tenant A Enablement: If this is supported, what specific steps or tenant-level settings must be adjusted in Tenant A to allow it to recognize and provision Fabric capacities given its lack of existing M365/Fabric products?

Any support would be much appreciated.

Azure Service Fabric
Azure Service Fabric

An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.

0 comments
Answer accepted by question author
Vinodh247-1375 44,556 Reputation points Volunteer Moderator
2026-07-08T15:21:20.2433333+00:00

Hi ,

Thanks for reaching out to Microsoft Q&A.

This setup is not supported for Fabric F (payg) capacity provisioning. Fabric capacity is tightly bound to a single Entra tenant that owns both the azure subscription (billing) and the M365/fabric service plane. In your case, Tenant A can create the Azure resource, but since Fabric and PBI are anchored in Tenant B, the capacity cannot attach or activate hence the “Fabric Free not allowed” and missing products. Fabric F SKUs require the same tenant to have PBI/Fabric enabled and service plans available, which Tenant A does not. There is no tenant-level switch in Tenant A to “light up” Fabric without M365 context. The correct approach is to align subscription and Fabric into the same tenant (move subscription to Tenant B or provision capacity directly in Tenant B); cross-tenant capacity linkage is not supported today.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

Was this answer helpful?

1 person found this answer helpful.
0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.