Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Configure scaling for Azure Cloud Services (extended support) description: How to enable scaling options for Azure Cloud Services (extended support) ms.topic: how-to ms.service: azure-virtual-machines author: gachandw ms.author: gachandw ms.reviewer: mimckitt ms.date: 07/24/2024 # Customer intent: As a cloud administrator, I want to configure scaling options for Azure Cloud Services (extended support) so that I can optimize resource usage and maintain high availability based on workload demands. --- # Configure scaling options with Azure Cloud Services (extended support) > [!IMPORTANT] > As of March 31, 2025, cloud Services (extended support)is deprecated and will be fully retired on March 31, 2027. [Learn more](https://aka.ms/csesretirement) about this deprecation and [how to migrate](https://aka.ms/cses-retirement-march-2025). Conditions can be configured to enable Cloud Services (extended support) deployments to scale in and out. These conditions can be based on CPU usage, disk load, and network load. Consider the following information when configuring scaling of your Cloud Service deployments: - Scaling impacts core usage. Larger role instances consume more cores and you can only scale within the core limit of your subscription. For more information, see [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md). - Scaling based on queue messaging threshold is supported. For more information, see [Get started with Azure Queue storage](/azure/storage/queues/storage-quickstart-queues-dotnet?tabs=passwordless%2Croles-azure-portal%2Cenvironment-variable-windows%2Csign-in-azure-cli). - To ensure high availability of your Cloud Service (extended support) applications, ensure to deploy with two or more role instances. - Custom autoscale can only occur when all roles are in a **Ready** state. ## Configure and manage scaling 1. Sign in to the [Azure portal](https://portal.azure.com). 2. Select the Cloud Service (extended support) deployment you want to configure scaling on. 3. Select the **Scale** blade. :::image type="content" source="media/enable-scaling-1.png" alt-text="Image shows selecting the Remote Desktop option in the Azure portal"::: 4. A page displays a list of all the roles in which scaling can be configured. Select the role you want to configure. 5. Select the type of scale you want to configure - **Manual scale** sets the absolute count of instances. 1. Select **Manual scale**. 2. Input the number of instances you want to scale up or down to. 3. Select **Save**. :::image type="content" source="media/enable-scaling-2.png" alt-text="Image shows setting up manual scaling in the Azure portal"::: 4. The scaling operation begins immediately. - **Custom Autoscale** allows you to set rules that govern how much or how little to scale. 1. Select **Custom autoscale** 2. Choose to scale based on a metric or instance count. :::image type="content" source="media/enable-scaling-3.png" alt-text="Image shows setting up custom autoscale in the Azure portal"::: 3. If scaling based on a metric, add rules as needed to achieve the desired scaling results. :::image type="content" source="media/enable-scaling-4.png" alt-text="Image shows setting up custom autoscale rules in the Azure portal"::: 4. Select **Save**. 5. The scaling operations begin as soon as a rule is triggered. 6. You can view or adjust existing scaling rules applied to your deployments by selecting the **Scale** tab. :::image type="content" source="media/enable-scaling-5.png" alt-text="Image shows adjusting an existing scaling rule in the Azure portal"::: ## Next steps - Review the [deployment prerequisites](deploy-prerequisite.md) for Cloud Services (extended support). - Review [frequently asked questions](faq.yml) for Cloud Services (extended support). - Deploy a Cloud Service (extended support) using the [Azure portal](deploy-portal.md), [PowerShell](deploy-powershell.md), [Template](deploy-template.md) or [Visual Studio](deploy-visual-studio.md).