尝试扩大应用服务计划时出错扩大并更正应用服务计划 SKU 以进行 VNET 集成
Error while trying to scale up App Service Plan scale up and correct app service plan SKU for VNET integration
我想为我的 Web 应用程序使用 VNET 集成。我的 Web 应用程序目前正在与 Azure SQL 数据库通信，我将为 Azure SQL 使用私有 Link。因此，必须根据 URL 为我的 Web 应用程序启用 VNET 集成：
https://docs.microsoft.com/en-us/azure/app-service/web-sites-integrate-with-vnet
我目前使用的是标准 S1 SKU。我想知道我的 SKU 是否支持 VNET 集成，或者我必须将我的 Web 应用程序升级到高级版？
在我粘贴的 link 中说：
“VNet 集成功能：
需要 Standard、Premium、PremiumV2、PremiumV3 或 Elastic Premium 定价计划。
支持TCP和UDP。
使用 Azure App Service 应用程序和函数应用程序。"
那么无论我使用什么 SKU，是否支持 VNET 集成？
此外，当我尝试扩展到 Premium P2v2 时，我收到消息“此扩展单元不支持 Premium V2”。
请帮忙
编辑：我刚刚读到 older Standard App Services do not support VNET Integration - 只有较新的 built 在 Standard 或 Premium V2 上才这样做。这意味着即使从旧的标准 S1 升级也可能会导致问题 - 可能就是您所看到的。
The feature is available from all App Service scale units in Premium
V2 and Premium V3. It's also available in Standard but only from newer
App Service scale units. If you are on an older scale unit, you can
only use the feature from a Premium V2 App Service plan. If you want
to make sure you can use the feature in a Standard App Service plan,
create your app in a Premium V3 App Service plan. Those plans are only
supported on our newest scale units. You can scale down if you desire
after that.
有关详细信息，请参阅下文。从 Github 问题中复制以便于参考。
If your app runs in an App Service deployment where PremiumV2 isn't
available, or if your app runs in a region that currently does not
support PremiumV2, you will need to re-deploy your app to take
advantage of PremiumV2. You have two options:
Create a new resource group, and then create a new app and App Service
plan in the new resource group, choosing your desired Azure region
during the creation process. You must select the PremiumV2 plan at the
time the new app service plan is created. This ensures the combination
of resource group, App Service plan, and Azure region will result in
the App Service plan being created in an App Service deployment that
supports PremiumV2. Then redeploy your application code into the newly
created app and app service plan. If desired you can subsequently
scale the App Service plan down from PremiumV2 to save costs, and you
will still be able to successfully scale back up again in the future
using PremiumV2.
If your app already runs in an existing Premium tier, then you can
clone your app with all app settings, connection strings, and
deployment configuration into a new app service plan that uses
PremiumV2. In the Clone app page, you can create an App Service plan
using PremiumV2 in the region you want, and specify the app settings
and configuration that you want to clone.
同样来自同一 Microsoft 文档的内容说：
The feature is available from all App Service scale units in Premium
V2 and Premium V3. It's also available in Standard but only from newer
App Service scale units. If you are on an older scale unit, you can
only use the feature from a Premium V2 App Service plan. If you want
to make sure you can use the feature in a Standard App Service plan,
create your app in a Premium V3 App Service plan. Those plans are only
supported on our newest scale units. You can scale down if you desire
after that.
还有关于 incompatible Resource Group and App Service SKU combination 的更多信息。您会注意到此文档已将其更改为 Premium v3
原答案
因此 Microsoft clearly says 标准计划属于 VNET 集成支持的范围。正如您正确指出的那样：
The VNet Integration features:
Require a Standard, Premium, PremiumV2, PremiumV3, or Elastic Premium
pricing plan.
您不需要升级到其他计划。
首先S1是支持VNet集成的最小SKU。
但是，您的问题是由于 Azure 数据中心的硬件布置方式引起的。这些是由“缩放单元”组成的，不知道实际的硬件大小，但它们具有特定的功能。
随着更新的硬件可用，引入了新的缩放单元和 SKU，但旧的缩放单元通常不支持新功能，通常升级它们这样做并不经济。
因此，在您的方案中，您部署到支持 S1 但不支持较新 SKU 的缩放单元中。
解决这个问题的方法是对更大的尺寸进行初始部署，例如PremiumV3，然后将大小降低到 S1 - 这样您就可以使用能够支持更新 SKU 的硬件。
我想为我的 Web 应用程序使用 VNET 集成。我的 Web 应用程序目前正在与 Azure SQL 数据库通信，我将为 Azure SQL 使用私有 Link。因此，必须根据 URL 为我的 Web 应用程序启用 VNET 集成： https://docs.microsoft.com/en-us/azure/app-service/web-sites-integrate-with-vnet
我目前使用的是标准 S1 SKU。我想知道我的 SKU 是否支持 VNET 集成，或者我必须将我的 Web 应用程序升级到高级版？ 在我粘贴的 link 中说：
“VNet 集成功能：
需要 Standard、Premium、PremiumV2、PremiumV3 或 Elastic Premium 定价计划。 支持TCP和UDP。 使用 Azure App Service 应用程序和函数应用程序。"
那么无论我使用什么 SKU，是否支持 VNET 集成？ 此外，当我尝试扩展到 Premium P2v2 时，我收到消息“此扩展单元不支持 Premium V2”。
请帮忙
编辑：我刚刚读到 older Standard App Services do not support VNET Integration - 只有较新的 built 在 Standard 或 Premium V2 上才这样做。这意味着即使从旧的标准 S1 升级也可能会导致问题 - 可能就是您所看到的。
The feature is available from all App Service scale units in Premium V2 and Premium V3. It's also available in Standard but only from newer App Service scale units. If you are on an older scale unit, you can only use the feature from a Premium V2 App Service plan. If you want to make sure you can use the feature in a Standard App Service plan, create your app in a Premium V3 App Service plan. Those plans are only supported on our newest scale units. You can scale down if you desire after that.
有关详细信息，请参阅下文。从 Github 问题中复制以便于参考。
If your app runs in an App Service deployment where PremiumV2 isn't available, or if your app runs in a region that currently does not support PremiumV2, you will need to re-deploy your app to take advantage of PremiumV2. You have two options:
Create a new resource group, and then create a new app and App Service plan in the new resource group, choosing your desired Azure region during the creation process. You must select the PremiumV2 plan at the time the new app service plan is created. This ensures the combination of resource group, App Service plan, and Azure region will result in the App Service plan being created in an App Service deployment that supports PremiumV2. Then redeploy your application code into the newly created app and app service plan. If desired you can subsequently scale the App Service plan down from PremiumV2 to save costs, and you will still be able to successfully scale back up again in the future using PremiumV2.
If your app already runs in an existing Premium tier, then you can clone your app with all app settings, connection strings, and deployment configuration into a new app service plan that uses PremiumV2. In the Clone app page, you can create an App Service plan using PremiumV2 in the region you want, and specify the app settings and configuration that you want to clone.
同样来自同一 Microsoft 文档的内容说：
The feature is available from all App Service scale units in Premium V2 and Premium V3. It's also available in Standard but only from newer App Service scale units. If you are on an older scale unit, you can only use the feature from a Premium V2 App Service plan. If you want to make sure you can use the feature in a Standard App Service plan, create your app in a Premium V3 App Service plan. Those plans are only supported on our newest scale units. You can scale down if you desire after that.
还有关于 incompatible Resource Group and App Service SKU combination 的更多信息。您会注意到此文档已将其更改为 Premium v3
原答案
因此 Microsoft clearly says 标准计划属于 VNET 集成支持的范围。正如您正确指出的那样：
The VNet Integration features:
Require a Standard, Premium, PremiumV2, PremiumV3, or Elastic Premium pricing plan.
您不需要升级到其他计划。
首先S1是支持VNet集成的最小SKU。
但是，您的问题是由于 Azure 数据中心的硬件布置方式引起的。这些是由“缩放单元”组成的，不知道实际的硬件大小，但它们具有特定的功能。
随着更新的硬件可用，引入了新的缩放单元和 SKU，但旧的缩放单元通常不支持新功能，通常升级它们这样做并不经济。
因此，在您的方案中，您部署到支持 S1 但不支持较新 SKU 的缩放单元中。
解决这个问题的方法是对更大的尺寸进行初始部署，例如PremiumV3，然后将大小降低到 S1 - 这样您就可以使用能够支持更新 SKU 的硬件。