Is cross-region connectivity between Power BI Service and Dynamics 365 Business Central supported?

(1) Share

Report

Posted on by FB-07070454-0

Hi everyone,

We are implementing Microsoft Dynamics 365 Business Central for one of our customers.

The customer is already using Power BI, with several reports published in the Power BI Service. The Power BI tenant's home region is Germany West Central.

Since Business Central will replace the customer's existing ERP system, we need to update the data sources of the existing Power BI reports after the migration.

Our main question is:

Is it supported to connect Power BI Service (home region: Germany West Central) to a Dynamics 365 Business Central environment hosted in a different geographic region?

If this scenario is supported, are there any known limitations, performance considerations, or Microsoft recommendations regarding cross-region connectivity?

Any guidance or references to the relevant Microsoft documentation would be greatly appreciated.

Thank you!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

OussamaSabbouh 18,128 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hello,

Yes, this scenario is generally supported; Power BI Service can connect to Business Central online through the standard Business Central connector / APIs / OData even if the Power BI tenant home region and the Business Central environment are in different geographies. Microsoft documentation does not state a same-region requirement between Power BI and Business Central. The main points to watch are data residency and performance: once the dataset is published/refreshed in Power BI, imported Business Central data is stored in the Power BI tenant/capacity region, so confirm this is acceptable for the customer’s compliance requirements. From a performance side, cross-region refresh can add latency, especially with large OData/API datasets, so keep the datasets optimized, expose only needed API pages/queries, avoid pulling unnecessary columns/companies, and use scheduled refresh/import models where possible. If strict residency or latency requirements exist, then review Power BI/Fabric Multi-Geo or consider aligning the BC environment and Power BI capacity region.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No