Regional Setup for Microsoft Fabric

As your Org needs to have only 1 Fabric capacity under US,

Then for dataverse in US, there is no need of setting up synapse link . You can use Fabric link that would create shortcut directly to dataverse in fabric lakehouse.

For Dataverse in Japan, you can have synapse link with spark enabled to create a lakehouse shoartcut in Fabric as Fabric link has a Geo limimtation that dataverse and fabric capacity needs to be in same Geo region

Hi Chary ,

This is a really interesting setup challenge you've got with data spread across Japan and US. Let me break this down based on what I've seen work (and not work) with Fabric regional setups.

For your primary region: Honestly, I'd go with US. Not because it's "better" per se, but because Fabric tends to be more stable there and you'll have fewer weird edge cases to deal with. Plus, if most of your team is US-based, latency will be better for day-to-day work.

Multi-region data migration: The good news is Fabric does support Multi-Geo, so you can have capacities in different regions. The bad news is there are some annoying limitations - once you create certain Fabric items in a region, they're stuck there. You can't just move a lakehouse from Japan to US later if you change your mind.

Performance wise: US regions (especially East/West 2) generally perform best, but honestly the difference isn't huge unless you're doing massive data transfers. The bigger issue is going to be the latency between your Fabric setup and your D365 sources.

Europe feasibility: Sure, it'll work, but you're adding an extra hop for everything. Your reports might feel a bit sluggish, and you'll definitely see higher data transfer costs. Unless you've got strict EU data residency requirements, I wouldn't recommend it for your use case.

My advice: Start with US, enable Multi-Geo from day one, and do a small pilot to test performance before committing to the full migration. Way easier to fix things early than after you've moved everything over.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

This response was assisted by AI for translation and formatting purposes.

This plan do look good but from 2nd view point : 

• If you have no compliance/privacy restrictions:

  • You can load directly from D365 Japan → Synapse Link → ADLS Gen2 (US), then into Fabric Lakehouse.

Which will give you : 

• Simplicity: Fewer ETL steps and pipelines to manage.

• Data Consolidation: All data lands in the US upfront, which may make downstream integration easier.

Hi Chary,
Have you had a chance to review the solution we shared by sandeephijam NandanHegde ? If the issue persists, feel free to reply so we can help further.

Thank you.

Hi Chary,

Checking in to see if your issue has been resolved. let us know if you still need any assistance.

Thank you.

Hi Chary,

We haven’t heard back from you in a while regarding your issue. let us know if your issue has been resolved or if you still require support.

Thank you.

Thank you for your time.
Could you please provide a response to the request mentioned below.
" I have four different D365/Dataverse instances located in four different regions. For the instance that matches the Microsoft Fabric region, I can use the 'Link to Fabric' feature. However, for the other instances located in different regions, my organization does not allow multi-geo setups. We are planning to purchase an F16 capacity for the project.
Please suggest cost effective options to bring data from these other Dataverse regions into Fabric. Also,
how many different ways are available to pull data from Dataverse into Fabric in a multi-region setup?