Merge pull request #263906 from gabesmsft/patch-3

prmerger-automator[bot] · web-flow · commit af1c8ba75f6c · 2024-01-23T01:20:40.000Z
Update manage-automatic-scaling.md
diff --git a/articles/app-service/manage-automatic-scaling.md b/articles/app-service/manage-automatic-scaling.md
@@ -10,7 +10,7 @@ author: msangapu-msft
 # Automatic scaling in Azure App Service
 
 > [!NOTE]
-> Automatic scaling is in preview. It's available for Premium V2 (P1V2, P2V2, P3V2) and Premium V3 (P1V3, P2V3, P3V3) pricing tiers, and supported for all app types: Windows, Linux, and Windows container. Automatic scaling is not supported on deployment slots.
+> Automatic scaling is in preview. It's available for Premium V2 (P1V2, P2V2, P3V2) and Premium V3 (P1V3, P2V3, P3V3) pricing tiers, and supported for all app types: Windows, Linux, and Windows container. Automatic scaling is not supported for deployment slot traffic.
 >
 
 Automatic scaling is a new scale out option that automatically handles scaling decisions for your web apps and App Service Plans. It's different from the pre-existing **[Azure autoscale](../azure-monitor/autoscale/autoscale-overview.md)**, which lets you define scaling rules based on schedules and resources. With automatic scaling, you can adjust scaling settings to improve your app's performance and avoid cold start issues. The platform prewarms instances to act as a buffer when scaling out, ensuring smooth performance transitions. You can use Application Insights [Live Metrics](../azure-monitor/app/live-stream.md) to check your current instance count, and [performanceCounters](../azure-functions/analyze-telemetry-data.md#query-telemetry-data) to see the instance count history. You're charged per second for every instance, including prewarmed instances. 

Original file line number	Diff line number	Diff line change
`@@ -10,7 +10,7 @@ author: msangapu-msft`
`10`	`10`	`# Automatic scaling in Azure App Service`
`11`	`11`
`12`	`12`	`> [!NOTE]`
`13`		`-> Automatic scaling is in preview. It's available for Premium V2 (P1V2, P2V2, P3V2) and Premium V3 (P1V3, P2V3, P3V3) pricing tiers, and supported for all app types: Windows, Linux, and Windows container. Automatic scaling is not supported on deployment slots.`
	`13`	`+> Automatic scaling is in preview. It's available for Premium V2 (P1V2, P2V2, P3V2) and Premium V3 (P1V3, P2V3, P3V3) pricing tiers, and supported for all app types: Windows, Linux, and Windows container. Automatic scaling is not supported for deployment slot traffic.`
`14`	`14`	`>`
`15`	`15`
`16`	`16`	Automatic scaling is a new scale out option that automatically handles scaling decisions for your web apps and App Service Plans. It's different from the pre-existing [Azure autoscale](../azure-monitor/autoscale/autoscale-overview.md), which lets you define scaling rules based on schedules and resources. With automatic scaling, you can adjust scaling settings to improve your app's performance and avoid cold start issues. The platform prewarms instances to act as a buffer when scaling out, ensuring smooth performance transitions. You can use Application Insights [Live Metrics](../azure-monitor/app/live-stream.md) to check your current instance count, and [performanceCounters](../azure-functions/analyze-telemetry-data.md#query-telemetry-data) to see the instance count history. You're charged per second for every instance, including prewarmed instances.