azure-application-insights - 将 App Insights 可用性测试部署到英国南部，但奇怪的是 ARM 说俄罗斯

Question

在自动部署 Application Insights 可用性监视资源时，我注意到奇怪的是，在保存 UK South 并从门户导出 ARM 模板时，该位置的名称似乎是俄罗斯。

我认为这是我的错误，但在深入研究 JavaScript 和网络流量后，我发现以下返回:

https://management.azure.com/batch?api-version=2015-11-01

{
    "DisplayName": "North Central US",
    "Tag": "us-il-ch1-azr"
},
{
    "DisplayName": "West Europe",
    "Tag": "emea-nl-ams-azr"
},
{
    "DisplayName": "Southeast Asia",
    "Tag": "apac-sg-sin-azr"
},
{
    "DisplayName": "West US",
    "Tag": "us-ca-sjc-azr"
},
{
    "DisplayName": "South Central US",
    "Tag": "us-tx-sn1-azr"
},
{
    "DisplayName": "East US",
    "Tag": "us-va-ash-azr"
},
{
    "DisplayName": "East Asia",
    "Tag": "apac-hk-hkn-azr"
},
{
    "DisplayName": "North Europe",
    "Tag": "emea-gb-db3-azr"
},
{
    "DisplayName": "Japan East",
    "Tag": "apac-jp-kaw-edge"
},
{
    "DisplayName": "Australia East",
    "Tag": "emea-au-syd-edge"
},
{
    "DisplayName": "France Central (Formerly France South)",
    "Tag": "emea-ch-zrh-edge"
},
{
    "DisplayName": "France Central",
    "Tag": "emea-fr-pra-edge"
},
{
    "DisplayName": "UK South",
    "Tag": "emea-ru-msa-edge"
},
{
    "DisplayName": "UK West",
    "Tag": "emea-se-sto-edge"
},
{
    "DisplayName": "Brazil South",
    "Tag": "latam-br-gru-edge"
},
{
    "DisplayName": "Central US",
    "Tag": "us-fl-mia-edge"
}

当看 quick start template它表明这似乎是莫斯科。

运行 availability monitoring is being deprecated 的一些基础设施，还有关于 Microsoft docs repo where an overhaul is mentioned 的讨论让它运行一段时间。莫斯科的名字是否有可能被用作代表英国的变通办法？或者这是一个奇怪的错误？

似乎没有一个 github 来讨论可用性监视器，只有像 SDK 这样的东西，上面的票在文档仓库中，所以我不确定提到这一点的最佳论坛。值得注意的是，似乎确实有 general confusion in the community whether it impacts Availability monitoring ，所以似乎值得讨论以防万一它是一个错误(或者如果我很傻并且错过了什么!)。

Answer 1

我直接联系了 Microsoft 一位友好的项目经理，他热情地回复了:

ARM templates must use our internal location IDs, which, due to historical reasons, do not match their actual location. This isn't documented anywhere externally unfortunately. I'll take care of updating the documentation, in the meantime here is a snippet from our repository - Display Name is the actual location, and the Tag is our internal location ID, which is also used in ARM.

DisplayName = "North Central US",
Tag = "us-il-ch1-azr"

DisplayName = "West Europe",
Tag = "emea-nl-ams-azr"

DisplayName = "Southeast Asia",
Tag = "apac-sg-sin-azr"

DisplayName = "West US",
Tag = "us-ca-sjc-azr"

DisplayName = "South Central US",
Tag = "us-tx-sn1-azr"

DisplayName = "East US",
Tag = "us-va-ash-azr"

DisplayName = "East Asia",
Tag = "apac-hk-hkn-azr"

DisplayName = "North Europe",
Tag = "emea-gb-db3-azr"

DisplayName = "Japan East",
Tag = "apac-jp-kaw-edge"

DisplayName = "Australia East",
Tag = "emea-au-syd-edge"

DisplayName = "France Central (Formerly France South)",
Tag = "emea-ch-zrh-edge"

DisplayName = "France Central",
Tag = "emea-fr-pra-edge"

DisplayName = "UK South",
Tag = "emea-ru-msa-edge"

DisplayName = "UK West",
Tag = "emea-se-sto-edge"

DisplayName = "Brazil South",
Tag = "latam-br-gru-edge"

DisplayName = "Central US",
Tag = "us-fl-mia-edge"

(我已经从看起来像 c# 代码的内容中删减了这个)

该文档将在适当的时候更新，因此如果有人在我之前遇到它，请随时将其添加为评论。