New Region Request – Azure SRE (East Asia Priority)

We recommend prioritizing the deployment of Azure SRE in the East Asia region.

East Asia serves as a key regional hub for APAC, hosting a significant number of regional workloads and customers.
Many APAC applications are architected with their hub VNet located in East Asia, following a hub-and-spoke model.

Currently, if Azure SRE is only available in regions such as Korea Central or Australia East:

It introduces additional network latency for APAC workloads connected to an East Asia hub.
It incurs cross-region VNet peering costs, as spoke VNets in East Asia must peer with SRE components deployed in other regions.

Deploying Azure SRE in East Asia would:

Reduce latency for regional applications
Avoid unnecessary cross-region peering charges
Align with the existing network architecture of APAC customers

The issue names no files, tests, or implementation entry points. Start by reviewing the repository's Azure deployment and regional availability process, then determine whether East Asia support is controlled here or by an external Azure service; done means a documented and implemented path to East Asia availability.

Written by the indexing model from the issue text.