Azure Static Web App - Static Content Location

Question

Azure Static Web App - Static Content Location

Pearce Fleming 20

The documentation for Azure SWA isn't totally clear about which regions are included in the "global" distribution of static content (not the API location).

I've done some testing and have found that the SWA service does not utilize any of the Australian regions. Any traffic from Australia (or New Zealand) is instead routed to the Hong Kong (Asia East) server.

This is unfortunate and I was wondering if there is any information available on the regions that are included in the SWA "global" distribution? This would help for deciding where to deploy any BYO APIs.

Or maybe there is a roadmap spelling out when/if more regions will be added to the list of regions that the SWA apps are deployed to? I was hoping at least 1 of the Australian regions would be used...

Thanks in advance for any guidance anyone can provide =]

RONEL BOHOLANO 0 Reputation points

2025-08-26T08:26:46.84+00:00

What is the nearest SWA option for Philippines? is there no available SWA for Southeast Asia (Singapore) rather than the East Asia (Hongkong)?

Accepted answer

0 additional answers

Your answer

RONEL BOHOLANO 0 Reputation points

2025-08-26T08:26:46.84+00:00

What is the nearest SWA option for Philippines? is there no available SWA for Southeast Asia (Singapore) rather than the East Asia (Hongkong)?

Answer 1

Shree Hima Bindu Maganti 5,485 Microsoft External Staff Moderator

Hi Pearce Fleming ,

Welcome to the Microsoft Q&A Platform!
Azure Static Web Apps (SWA) globally distribute static content using a content delivery network (CDN). However, the specifics of which Azure regions are utilized for edge distribution aren't directly published by Microsoft.

Azure SWA uses Azure Front Door for global content delivery. However, not all Azure regions are included in the edge distribution.
Australian traffic is routed to Asia East (Hong Kong) due to no SWA edge nodes in Australian regions.
Deploy APIs in Australian Azure regions (e.g., Australia East or Australia Southeast) to reduce latency for Australian users. This does not affect static content delivery.
Use Azure Front Door or Azure CDN to manually configure content delivery closer to Australian users.
Tools like Azure Network Watcher or traceroute can help verify routing and latency. Reference:
Azure Static Web Apps documentation and Azure Updates
Azure Network Watcher. Azure Front Door and Azure CDN.
If the answer is helpful, please click "Accept Answer" and kindly upvote it.

Shree Hima Bindu Maganti 5,485 Reputation points Microsoft External Staff Moderator

2024-12-03T05:07:04.1466667+00:00

Hi Pearce Fleming ,

Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.
Shree Hima Bindu Maganti 5,485 Reputation points Microsoft External Staff Moderator

2024-12-04T04:27:59.3266667+00:00

Hi Pearce Fleming ,

Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.
Pearce Fleming 20 Reputation points

2024-12-11T04:43:33.56+00:00

Thanks, that is pretty much as I expected. My only question is if my SWA app is deployed to the Asia East region and I "bring my own" API that is deployed to an Australian region, if the client browser makes a request to a "/api/..." endpoint, won't that request have to be routed from the SWA instance in Asia East to my API instance in an Australian region?

So, Client (Aus) >> SWA Server (Asia) >> WebApp API (Aus).

I understand that the latency between East Asia and Australia is actually quite low, I'm just trying to understand the mechanics

Share via

Azure Static Web App - Static Content Location

0 additional answers

Your answer