Forum Discussion
Optimizing Microsoft Fabric Performance for Global Users: Addressing Latency and Connectivity
Scenario:
Microsoft Fabric has been provisioned in the Southeast Asia (SEA) region. However, users from other regions—such as the United States (US), Latin America, and others—are connecting to the environment.
Questions:
How can I ensure that users from different regions do not experience latency issues when accessing Microsoft Fabric?
Are there specific optimizations or configurations that can be applied to improve performance?
Can you recommend alternative solutions to enhance performance and provide a seamless experience for global users?
Would multi-region deployment or any other architectural approach be beneficial?
Hi iamclp ,
Thank you for reaching out to the Microsoft Fabric Community Forum about the issue you are encountering.
1.Since Fabric data and processing are bound to SEA, users in other regions (e.g., US, LATAM) may experience latency due to network distance and data transfer times.
2.Instead of importing large datasets, use DirectQuery or Direct Lake mode to reduce data transfer times.
3.Power BI caches frequently used queries, reducing repeated cross-region data pulls.
Please refer the documents below for more understanding.
https://learn.microsoft.com/en-us/azure/reliability/reliability-fabric
Multi-Geo support for Fabric - Microsoft Fabric | Microsoft Learn
https://learn.microsoft.com/en-us/fabric/admin/region-availabilityIf this post helps, please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Regards,
Pallavi.
4 Replies
Hi iamclp ,
Thank you for reaching out to the Microsoft Fabric Community Forum about the issue you are encountering.
1.Since Fabric data and processing are bound to SEA, users in other regions (e.g., US, LATAM) may experience latency due to network distance and data transfer times.
2.Instead of importing large datasets, use DirectQuery or Direct Lake mode to reduce data transfer times.
3.Power BI caches frequently used queries, reducing repeated cross-region data pulls.
Please refer the documents below for more understanding.
https://learn.microsoft.com/en-us/azure/reliability/reliability-fabric
Multi-Geo support for Fabric - Microsoft Fabric | Microsoft Learn
https://learn.microsoft.com/en-us/fabric/admin/region-availabilityIf this post helps, please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Regards,
Pallavi.Hi iamclp ,
I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you as 'Accept as Solution' or sharing your solution. It would be greatly appreciated by others in the community who may have the same question.
Thank you for being a valued member of the Microsoft Fabric Community Forum!Hi iamclp ,
I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you or sharing your answer and Accept it as solution. It would be greatly appreciated by others in the community who may have the same question
Thank you for being a valued member of the Microsoft Fabric Community Forum!Hi iamclp ,
May I ask if you have gotten this issue resolved?
If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.
Thank you for being a valued member of the Microsoft Fabric Community Forum!