Performance based "Azure region" of Workspace Collection?

[kevhav]

We're starting to use Power BI Embedded, to provide reports in a web app to external users across the globe. I have assumed that users would get better performance with Power BI Embedded reports if those reports were stored in a Workspace Collection in an Azure region closer to them. E.g., for a user in London, give them reports housed in the "UK South" region, and for users in California, give them reports housed in the "West US" region. Is this true?

We noticed that the embedUrl always has the same domain ('https://app.powerbi.com/...'), regardless of the Azure region of the Workspace Collection where the report is stored. So...I don't understand these things...but the web developer with whom I'm working is hypothesizing that the performance of reports shouldn't vary much based on the Azure region of the Workspace Collection, because the physical location of web services API must be the same, and all reports/data would have to flow through through there. Is this true?

Also, some quick/informal performance testing shows that for a user in a given location, there is no major difference in performance when pulling reports from Azure regions that are near to vs. far from that user's physical location.

So, now I'm thinking it would be simpler to just house all of our reports in a single Workspace Collection, in one arbitrary Azure region, for delivery to external users across the globe.

What would you recommend? For the purpose of Power BI Embedded, why would I choose to set up a Workspace Collection in one Azure region vs. another? Is there any use case for using multiple Workspace Collections in different Azure regions?

[Eric_Zhang]

@kevhav

I'm by no means an Azure expert, I just share something based on my monitoring(via chrome dev tool(F12)) and understanding.

For more accurate explanation on Azure structure, you shall go to Microsoft Azure forum.

For Power BI Embedded, the embeded url is like "https://embedded.powerbi.com" 

The embed url host is a cluster url, you will actually be distributed to a closest server instance when trying to access an embedded url.

After that, to retrieve data from your workspace, in Azure, the request would be redirected to a server which would connect to your workspace fast.

So based on my understanding, toughly speaking, as long as your user can connect to "https://embedded.powerbi.com" fast, they won't experience performance slowness, regardless of where your workspace collection is located.