Merge pull request #53996 from staleycyn/patch-2

Update app service plans module

Author: v-dirichards

learn-pr/wwl-azure/configure-app-service-plans/includes/3-determine-plan-pricing.md

@@ -20,13 +20,13 @@ The pricing tiers are grouped into three categories:
 
 Here's a sample of different [plan details](/azure/app-service/overview-hosting-plans). 
 
-| Feature | Free F1 | Basic B1 | Standard S1 | Premium P1V3 | 
-| --- | --- | --- | --- | --- | 
-| Usage | Development, Testing | Development, Testing | Production workloads | Enhanced scale, performance | 
-| Staging slots | N/A | N/A | 5 | 20 |
-| Auto scale | N/A | Manual | Rules | Rules, Elastic |
-| Scale instances | N/A | 3 | 10 | 30 |
-| Daily backups | N/A | N/A | 10 | 50 |
+| Feature | Free F1 | Basic B1 | Standard S1 | Premium P1V3 | Isolated V2 |
+| --- | --- | --- | --- | --- | --- |
+| Usage | Development, Testing | Development, Testing | Production workloads | Enhanced scale, performance | Network-isolated workloads |
+| Staging slots | N/A | N/A | 5 | 20 | 20 |
+| Auto scale | N/A | Manual | Rules | Rules, Elastic | Rules |
+| Scale instances | N/A | 3 | 10 | 30 | 200 |
+| Daily backups | N/A | N/A | 10 | 50 | 50 |
 
 ### Free and Shared
 
@@ -42,11 +42,11 @@ The Standard service plan is designed for running production workloads. Pricing
 
 ### Premium
 
-The Premium service plan is designed to provide enhanced performance for production applications. The upgraded Premium plan, Premium v2, offers Dv2-series virtual machines with faster processors, SSD storage, and double memory-to-core ratio compared to the Standard tier. The new Premium plan also supports higher scale via increased instance count while still providing all the advanced capabilities of the Standard tier. The first generation of Premium plan is still available to support existing customer scaling needs.
+The Premium service plan is designed for production apps that need higher performance and scale. PremiumV3 is the current Premium tier, offering Dav4 and Ddv4-series virtual machines and SSD storage. PremiumV3 supports standard compute SKUs and memory-optimized SKUs for high-memory workloads. PremiumV3 supports both rule-based autoscaling and automatic scaling. PremiumV3 is recommended for new deployments.
 
 ### Isolated
 
-The Isolated service plan is designed to run mission critical workloads that are required to run in a virtual network. The Isolated plan allows customers to run their applications in a private, dedicated environment in an Azure datacenter. The plan offers Dv2-series virtual machines with faster processors, SSD storage, and a double memory-to-core ratio compared to the Standard tier. The private environment used with an Isolated plan is called the App Service Environment. The plan can scale to 100 instances with more available upon request.
+The Isolated service plan supports mission-critical workloads needing network isolation. IsolatedV2 is the preferred tier offering newer hardware, up to 200 instances, private environments, and enhanced security. IsolatedV2 is recommended for new workloads due to better performance and simpler pricing.
 
 ## Task to be done: Select an App Service plan
 

learn-pr/wwl-azure/configure-app-service-plans/includes/4-scale-up-scale-out.md

@@ -10,7 +10,7 @@ Let's examine the details of scaling for your Azure App Service plan and App Ser
 
 - The scale up method increases the amount of CPU, memory, and disk space. Scaling up gives you extra features like dedicated virtual machines, custom domains and certificates, staging slots, autoscaling, and more. You scale up by changing the pricing tier of the Azure App Service plan where your application is placed.
 
-- The scale-out method increases the number of virtual machine instances that run your application. You can scale to as many as instances, depending on your App Service plan pricing tier. Take advantage of App Service Environments in the Isolated tier to further increase your scale-out count to 100 instances. The scale instance count can be configured manually or automatically (autoscale).
+- The scale-out method increases the number of virtual machine instances that run your application. You can scale out to the maximum number of instances for your pricing tier. Take advantage of App Service Environments in the Isolated tier to further increase your scale-out count to 100 instances. The scale instance count can be configured manually or automatically (autoscale).
 
 - With autoscale, you can automatically increase the scale instance count for the scale-out method. Autoscale is based on predefined rules and schedules.
 

learn-pr/wwl-azure/configure-app-service-plans/includes/5-plan-scaling.md

@@ -33,9 +33,30 @@ There are several considerations to keep in mind when you configure autoscale fo
 - **Adequate scale margin**. Make sure your maximum and minimum instance count values are different, and set an adequate margin between the two values. You can automatically scale between the minimum and maximum by using rules you create.
 
 - **Scale rule combinations**. Always use a scale-out and scale-in rule combination that performs an increase and decrease. If you don't set a scale-out rule, your application might fail, or performance might degrade under increased loads. If you don't set a scale-in rule, you can experience unnecessary and extensive costs when the load decreases.
-
+  
 - **Metric statistics**. Carefully choose the appropriate statistic for your diagnostic metrics, including Average, Minimum, Maximum, and Total.
-
+ 
 - **Default instance count**. Always select a safe default instance count. The default instance count is important because autoscale scales your service to the count you specify when metrics aren't available.
 
 - **Notifications**. Always configure autoscale notifications. It's important to maintain awareness of how your application is performing as the load changes.
+
+
+### Things to consider when configuring automatic scaling
+
+In addition to rule-based autoscale, Azure App Service offers Automatic scaling (also called Elastic scaling) for PremiumV2 and PremiumV3 tiers. This is a separate scaling feature that works differently from the autoscale rules.
+
+- **HTTP traffic-based.** Automatic scaling responds directly to incoming HTTP requests without requiring you to configure scaling rules.
+ 
+- **Platform-managed.** Azure automatically manages the scaling decisions based on traffic patterns, eliminating the need for rule configuration.
+ 
+- **Always-ready instances.** Maintains warmed instances to handle traffic spikes immediately.
+ 
+- **Tier availability.** Available only on PremiumV2 and PremiumV3  tiers.
+ 
+### Choose between Autoscale and Automatic scaling
+
+- **Use rule-based Autoscale.** You need custom scaling logic, want to scale based on multiple metrics, or need schedule-based scaling.
+  
+- **Use Automatic scaling.** You want less management, can't predict load patterns, or need fast response to traffic changes without rule configuration.
+
+