Merge branch 'main' into pr/7827

Author: Simonx Xu

.openpublishing.build.ps1

@@ -5779,6 +5779,11 @@
       "source_path": "support/developer/visualstudio/visual-basic/ide/mouse-wheel-events-do-not-work.md",
       "redirect_url": "/previous-versions/troubleshoot/visualstudio/ide/mouse-wheel-events-do-not-work",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "support/developer/visualstudio/installation/known-issues-visual-studio-2012-update.md",
+      "redirect_url": "/troubleshoot/developer/visualstudio/welcome-visual-studio",
+      "redirect_document_id": false
     }
   ]
 }

.openpublishing.redirection.developer.json

@@ -19,12 +19,7 @@ summary: |
   
 sections:
   - name: Built-in images
-    questions:
-      - question: |
-          I want to fork the built-in Docker containers that the platform provides. Where can I find those files?
-        answer: |
-          You can find all Docker files on [GitHub](https://github.com/Azure/app-service-quickstart-docker-images).
-                    
+    questions:            
       - question: |
           What are the expected values for the Startup File section when I configure the runtime stack?
         answer: |
@@ -293,3 +288,4 @@ additionalContent: |
   - [Environment variables and app settings reference](/azure/app-service/reference-app-settings)
   
   [!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
+

.openpublishing.redirection.json

@@ -4,9 +4,9 @@ metadata:
   description: Describe common questions and answers about scaling in Azure App Service.
   services: app-service
   author: auolivei
-  ms.reviewer: amehrot, rimarr, genli
+  ms.reviewer:  genli
   ms.topic: faq
-  ms.date: 08/03/2022
+  ms.date: 12/05/2024
   ms.author: auolivei
   ms.service: azure-app-service
 title: Frequently asked questions about scaling web apps in Azure App Service
@@ -62,7 +62,7 @@ sections:
           Autoscale is triggered when metrics exceed preconfigured boundaries. Sometimes, you might notice that the capacity is only partially filled compared to what you expected. This behavior might occur when the number of instances you want isn't available. In that scenario, autoscale partially fills in with the available number of instances. Autoscale then runs the rebalance logic to get more capacity. It allocates the remaining instances, and this allocation might take a few minutes. If you don't see the expected number of instances after a few minutes, it might be because the partial refill was enough to bring the metrics within the boundaries. Or, autoscale might have scaled down because it reached the lower metrics boundary.
 
       - question: |
-           When I scale up an App Service Plan to a Premium V3 tier, the "Premium V3 is not supported for this scale unit. Please consider redeploying or cloning your app." error occurs. What should I do?
+           When I scale up an App Service Plan to a Premium V3 tier, the "Premium V3 isn't supported for this scale unit. Please consider redeploying or cloning your app." error occurs. What should I do?
         answer: |
           The Premium V3 feature requires the site to run on the newest hardware infrastructure. To scale up an App Service Plan to Premium V3, the Web App must be running in an App Service deployment that supports PremiumV3. For more information, see [Scale up from an unsupported resource group and region combination](/azure/app-service/app-service-configure-premium-tier#scale-up-from-an-unsupported-resource-group-and-region-combination).
 
@@ -76,5 +76,10 @@ sections:
         answer: |
           The file change audit logs "AppServiceFileAuditLogs" are only available for App Services in Premium, PremiumV2, and Isolated App Service Plans. If you need "AppServiceFileAuditLogs," you won't be able to scale down to the Basic tier. To have these audit logs available, configure your App Service Plan for Premium or higher tier. 
 
+      - question: |
+          I'm getting the "App Service Plans with fewer than 3 workers aren't allowed for zone redundancy. Requested number of workers: number" error. What should I do?
+        answer: |
+          [Availability zone support](/azure/reliability/reliability-app-service#availability-zone-support) requires at least three instances. Verify if the App Service Plan has zone redundancy enabled and if you have autoscale on the App Service Plan. If so, correct the autoscale rule to not set the number of instances to a value less than three.
+
 
           [!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]

support/azure/.openpublishing.redirection.azure.json

@@ -0,0 +1,49 @@
+---
+title: ContainerGroupQuotaReached error when deploying Spot containers
+description: Provides solutions to the ContainerGroupQuotaReached error that occurs when you deploy a Spot container to Azure Container Instances.
+ms.date: 10/28/2024
+ms.reviewer: chiragpa, v-weizhu
+ms.service: azure-container-instances
+ms.custom: sap:Configuration and Setup
+---
+# ContainerGroupQuotaReached error - Container group quota exceeded in region
+
+This article provides a solution to the Spot container deployment error ContainerGroupQuotaReached.
+
+## Symptoms 
+
+When you deploy a Spot container to Azure Container Instances (ACI) from the Azure portal or by using the Azure CLI, the deployment fails with a ContainerGroupQuotaReached error like the following text:
+
+> Code: ContainerGroupQuotaReached  
+> Message: Resource type 'Microsoft.ContainerInstance/containerGroups' container group quota 'StandardSpotCores' exceeded in region 'westeurope'. Limit: '100', Usage: '12' Requested: '90'.
+
+Here's a command example for deploying a Spot container:
+
+```azurecli
+az container create -g MyResourceGroup --name myapp --image myimage:latest --priority spot --cpu 10
+```
+
+> [!NOTE]
+> Currently, Spot containers are only available in these regions: East US 2, West Europe, and West.
+
+## Cause
+
+This issue occurs because the container group default quota exceeds the default Spot quota bound by your Azure subscription. The following table shows the default Spot quota for different subscription types:
+
+|Subscription type|	StandardSpotCores limit|
+|---|---|
+|Enterprise Agreement|	100|
+|Default|	10|
+|Others|	0|
+
+To check the subscription type of your billing account, see [Check the type of your account](/azure/cost-management-billing/manage/view-all-accounts#check-the-type-of-your-account).
+
+## Solution
+
+To resolve this issue, increase the StandardSpotCores limit. To do so, use one of the following methods:
+
+- Change the subscription type to Default to get 10 StandardSpotCores limit.
+- [Change the subscription type to Enterprise Agreement](/azure/cost-management-billing/manage/mosp-ea-transfer) to get 100 StandardSpotCores limits.
+- File support request to increase capacity for Spot containers. For more information, see [How do I file quota requests for ACI Spot containers?](/azure/container-instances/container-instances-faq#spot-containers-on-azure-container-instances--preview)
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/app-service/faqs-app-service-linux.yml

@@ -19,6 +19,8 @@ items:
     href: configuration-setup/long-image-pulls.md
   - name: Error "service unavailable" when deploying GPU-enabled containers
     href: configuration-setup/service-unavailable-gpu-enabled-aci-deployment-failures.md
+  - name: ContainerGroupQuotaReached - container group quota exceeded in region
+    href: configuration-setup/spot-container-group-quota-reached-error.md
   - name: ServiceUnavailable - container group quota exceeded in region
     href: configuration-setup/service-unavailable-container-group-quota-exceeded.md
   - name: ServiceUnavailable (409) - requested resource is not available in the location

support/azure/app-service/scaling-web-app-faq.yml

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Container Registry authentication issues
 description: Helps resolve the most common authentication errors that occur when you pull images from an Azure container registry.
 ms.date: 08/19/2024
 ms.reviewer: chiragpa, v-rekhanain, v-weizhu
-ms.service: azure-container-instances
+ms.service: azure-container-registry
 ms.custom: sap:Authenticate to registry
 ---
 # Troubleshoot Azure Container Registry authentication issues

support/azure/azure-container-instances/configuration-setup/spot-container-group-quota-reached-error.md

@@ -6,7 +6,7 @@ author: AndreiBarbu95
 ms.author: andbar
 editor: v-jsitser
 ms.reviewer: avtakkar, v-rekhanain, v-leedennis
-ms.service: azure-container-instances
+ms.service: azure-container-registry
 ms.topic: troubleshooting-problem-resolution
 ms.custom: sap:Image Pull Issues
 #Customer intent: As an Azure Container Registry user, I want to fix an "unauthorized: authentication required" error so that I can pull a container image or artifact successfully.