microsoft / microsoft/sre-agent

New region request: Japan East (japaneast)

Open
#247 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

region request
Dominant language
PowerShell
Stars
160
Forks
97
Avg merge
2d 5h
Merged PRs (30d)
12

Description

Region Request: Japan East

Requested region: Japan East (japaneast)

Use case

We are operating Azure workloads in Japan East, which is the primary region
for many Japanese enterprises and Microsoft's main Azure region in Japan.
Japan East offers the broadest service availability and the largest capacity
in the Japan geography.

We would like to deploy Azure SRE Agent in Japan East to:

  • Meet data residency requirements for Japanese regulations (e.g., handling
    of operational data within Japan)
  • Minimize latency between the SRE Agent and the monitored resources
    deployed in Japan East
  • Align with our organization's region strategy that designates Japan East
    as the primary region for production workloads
Current workaround

We are currently forced to use australiaeast or koreacentral as the nearest
supported regions, which does not satisfy our data residency and latency
requirements.

References

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Supported regions – Azure SRE Agent reference linked in the issue and inspect how the current region list is represented in the project. Determine the changes required to enable Japan East (japaneast); done means the region is supported without relying on the listed workarounds and the supported-regions information is updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.