用于使用新的 VNet 集成功能配置应用服务的 ARM 模板?

Pra*_*eep 12 azure azure-virtual-network azure-web-app-service azure-rm-template

我正在研究 ARM 模板,我已经创建了包含两个或多个 azure 应用服务以及应用服务计划的模板文件,然后配置了每个应用服务的 VNET 集成。

这是示例 JSON 代码:

    {
  "comments": "Web-App-01",
  "name": "[variables('app_name_01')]",
  "type": "Microsoft.Web/sites",
  "location": "[variables('location')]",
  "apiVersion": "2016-08-01",
  "dependsOn": [
    "[resourceId('Microsoft.Web/serverfarms', variables('asp_name_01'))]"
  ],
  "tags": {
    "displayName": "[variables('app_name_01')]"
  },
  "properties": {
    "name": "[variables('app_name_01')]",
    "serverFarmId": "[resourceId('Microsoft.Web/serverfarms', variables('asp_name_01'))]",
    "siteConfig": {
      "alwaysOn": true
    }
  },
    "resources": [
      {
        "type": "Microsoft.Web/sites/virtualNetworkConnections",
        "name": "[concat(variables('app_name_01'), '/', variables('vnet_connection_name'),uniqueString('asdsdaxsdsd'))]",
        "apiVersion": "2016-08-01",
        "location": "[variables('location')]",
        "properties": {
          "vnetResourceId": "[resourceId('Microsoft.Network/virtualNetworks/subnets', variables('vm_vnet_name'), variables('web_subnet_name'))]"
        },
        "dependsOn": [
          "[resourceId('Microsoft.Web/sites', variables('app_name_01'))]",
          "[resourceId('Microsoft.Network/virtualNetworks/subnets', variables('vm_vnet_name'), variables('web_subnet_name'))]"
        ]
      }
    ]
},
{
  "comments": "Web-App-02",
  "name": "[variables('app_name_02')]",
  "type": "Microsoft.Web/sites",
  "location": "[variables('location')]",
  "apiVersion": "2016-08-01",
  "dependsOn": [
    "[resourceId('Microsoft.Web/serverfarms', variables('asp_name_02'))]"
  ],
  "tags": {
    "displayName": "[variables('app_name_02')]"
  },
  "properties": {
    "name": "[variables('app_name_02')]",
    "serverFarmId": "[resourceId('Microsoft.Web/serverfarms', variables('asp_name_01'))]",
    "siteConfig": {
      "alwaysOn": true
    }
  },
    "resources": [
      {
        "type": "Microsoft.Web/sites/virtualNetworkConnections",
        "name": "[concat(variables('app_name_02'), '/', variables('vnet_connection_name'),uniqueString('asdsdaxsdsd'))]",
        "apiVersion": "2016-08-01",
        "location": "[variables('location')]",
        "properties": {
          "vnetResourceId": "[resourceId('Microsoft.Network/virtualNetworks/subnets', variables('vm_vnet_name'), variables('web_subnet_name'))]"
        },
        "dependsOn": [
          "[resourceId('Microsoft.Web/sites', variables('app_name_02'))]",
          "[resourceId('Microsoft.Network/virtualNetworks/subnets', variables('vm_vnet_name'), variables('web_subnet_name'))]"
        ]
      }
    ]
}
Run Code Online (Sandbox Code Playgroud)

上面的代码适用于少数 azure 应用服务,但对于其余的应用服务,我在 Azure 应用服务的 VNET 集成期间收到内部服务器错误或冲突或错误请求。

注意:当我部署上述 JSON 代码时,配置的是旧 VNET 集成而不是新 VNET(预览)功能。因此,我需要为每个应用服务配置新的 VNET(预览)功能。

所以,任何人都可以建议我如何解决上述问题。

Sim*_*ory 19

我在 Azure Docs GitHub 帖子中找到了一个工作示例:

我们如何将新的 vnet 集成与 ARM 模板集成?

似乎与新的 VNet 集成以不同的方式工作,该集成使用Microsoft.Web/sites/config名为virtualNetwork而不是Microsoft.Web/sites/virtualNetworkConnections子资源的子资源

以及需要在目标子网/vnet 上设置的一些要求(在链接中描述)。集成部分看起来像这样:

   {
      "apiVersion": "2018-02-01",
      "type": "Microsoft.Web/sites",
      "name": "[parameters('appName')]",
      "location": "[resourceGroup().location]",

...

      "resources": [
        {
          "name": "virtualNetwork",
          "type": "config",
          "apiVersion": "2018-02-01",
          "location": "[resourceGroup().location]",
          "properties": {
            "subnetResourceid": "[parameters('subnetResourceId')]",
            "swiftSupported": true
          },
          "dependsOn": [
            "[resourceId('Microsoft.Web/sites', parameters('appName'))]"
          ]
        }
      ]
   },
Run Code Online (Sandbox Code Playgroud)

除此之外,我没有找到太多其他记录,除了在"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/networkConfig/virtualNetwork"定义端点的 azure-rest-api-specs 中对它的引用:

azure-rest-api-specs / WebApps.json

似乎(如规范所示)替换"type": "config""type": "networkConfig"也有效。

  • 这也确实对我们有帮助,请务必在子网上设置委派才能使其发挥作用。(正如顶部的 github 链接也指出的那样) (2认同)

小智 8

我和微软的一位高级工程师谈过。

关键是更换自动化模板

    {
        "type": "Microsoft.Web/sites/virtualNetworkConnections",
        "apiVersion": "2018-11-01",
        "name": "[concat(parameters('sites_FelixOFA_name'), '/xxxxxxx_Functions')]",
        "location": "West Europe",
        "dependsOn": [
            "[resourceId('Microsoft.Web/sites', parameters('sites_FelixOFA_name'))]"
        ],
        "properties": {
            "vnetResourceId": "[concat(parameters('virtualNetworks_FelixODevPremNet_externalid'), '/subnets/Functions')]",
            "isSwift": true
        }
    }
Run Code Online (Sandbox Code Playgroud)

{
  "type": "Microsoft.Web/sites/networkConfig",
  "name": "[concat(parameters('webAppName'),'/VirtualNetwork')]",
  "apiVersion": "2016-08-01",
  "properties":
              {
                            "subnetResourceId": "[parameters('subnetResourceId')]"
              }
}
Run Code Online (Sandbox Code Playgroud)

其中子网资源 ID 是其子网的资源 ID - 它应该看起来像 /subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.Network/virtualNetworks/{vnetName}/subnets/{subnetName}