Merge pull request #311103 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-29 23:00 UTC

Author: learn-build-service-prod[bot]

articles/app-service/configure-ssl-certificate-in-code.md

@@ -17,7 +17,7 @@ ms.custom:
 
 [!INCLUDE [app-service-managed-certificate](./includes/managed-certs/managed-certs-note.md)]
 
-In your application code, you can access the [public or private certificates that you add to Azure App Service](configure-ssl-certificate.md). Your app code might act as a client and access an external service that requires certificate authentication. It might also need to perform cryptographic tasks. This article shows how to use public or private certificates in your application code.
+In your application code, you can access both [public key certificates and certificates that contain a private key that you add to Azure App Service.](configure-ssl-certificate.md). Your app code might act as a client and access an external service that requires certificate authentication. It might also need to perform cryptographic tasks. This article shows how to use public or private certificates in your application code.
 
 This approach to using certificates in your code makes use of the Transport Layer Security (TLS) functionality in App Service, which requires your app to be in the Basic tier or higher. If your app is in the Free or Shared tier, you can [include the certificate file in your app repository](#load-a-certificate-from-a-file).
 

articles/app-service/overview-hosting-plans.md

@@ -70,6 +70,13 @@ Except for the Free tier, an App Service plan carries a charge on the compute re
 
 - **Shared tier**: Each app receives a quota of CPU minutes, so *each app* is charged for the CPU quota.
 - **Dedicated compute tiers (Basic, Standard, Premium, PremiumV2, PremiumV3, PremiumV4)**: The App Service plan defines the number of VM instances that the apps are scaled to, so *each VM instance* in the App Service plan is charged. These VM instances are charged the same, regardless of how many apps are running on them. To avoid unexpected charges, see [Delete an App Service plan](app-service-plan-manage.md#delete-an-app-service-plan).
+
+> [!NOTE] 
+> In dedicated compute tiers, the VM resources are **dedicated to your App Service plan and are not shared with other customers**.  
+> However, **any apps you place inside the same App Service plan share those dedicated resources with each other**.    
+> This means compute is dedicated at the **plan level**, not the **per-app level**.  
+> To isolate compute per app, create a separate App Service plan.
+
 - **IsolatedV2 tier**: The App Service Environment defines the number of isolated workers that run your apps, and *each worker* is charged.
 
 You aren't charged for using the App Service features that are available to you. These features include configuring custom domains, TLS/SSL certificates, deployment slots, and backups. The exceptions are:

articles/azure-functions/functions-event-grid-blob-trigger.md

@@ -273,7 +273,7 @@ Visual Studio Code uses Azurite to emulate Azure Storage services when running l
 
 1. Verify that the *local.settings.json* file has `"UseDevelopmentStorage=true"` set for `AzureWebJobsStorage`. This setting tells Core Tools to use Azurite instead of a real storage account connection when running locally. 
 
-1. Press F1 to open the command palette, type `Azurite: Start Blob Service`, and press enter. This action starts the Azurite Blob Storage service emulator.
+1. Press F1 to open the command palette, type `Azurite: Start`, and press Enter. This action starts the Azurite Blob Storage service emulator.
 
 1. Select the Azure icon in the Activity bar, expand **Workspace** > **Attached Storage Accounts** > **Local Emulator**, right-click **Blob Containers**, select **Create Blob Container...**, enter the name `samples-workitems`, and press Enter.
 

articles/azure-maps/supported-languages.md

@@ -495,7 +495,7 @@ The following table provides supported views.
 | QA      | Qatar (Arabic View)                   | ✓    |        |             |
 | SA      | Saudi Arabia (Arabic View)            | ✓    |        |             |
 | SY      | Syria (Arabic View)                   | ✓    |        |             |
-| US      | United States of America              |      | ✓      |             |
+| US      | United States of America              | ✓    | ✓      |             |
 | YE      | Yemen (Arabic View)                   | ✓    |        |             |
 | Auto    | Automatically detect based on request | ✓    | ✓      |             |
 | Unified | Unified View (Others)                 | ✓    | ✓      |

articles/azure-netapp-files/azure-netapp-files-resource-limits.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 11/11/2025
+ms.date: 01/29/2026
 ms.author: anfdocs
 # Customer intent: As an IT administrator managing Azure NetApp Files, I want to understand the resource limits and how to request limit increases, so that I can effectively plan and allocate storage resources for my organization’s needs.
 ---

articles/azure-netapp-files/azure-netapp-files-service-levels.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 09/16/2025
+ms.date: 01/29/2026
 ms.author: anfdocs
 # Customer intent: "As a cloud storage administrator, I want to understand the throughput capabilities of different service levels in Azure NetApp Files, so that I can choose the right configuration to meet my application's performance requirements."
 ---
@@ -17,7 +17,7 @@ Service levels are an attribute of a capacity pool. Service levels are defined a
 
 Azure NetApp Files supports five service levels: *Elastic*, *Flexible*, *Standard*, *Premium*, and *Ultra*. 
 
-The Elastic service level isn't bare-metal flash and is based on Azure infrastructure. 
+The Flexible, Standard, Premium, and Ultra service levels deliver in‑Azure bare‑metal flash performance. The Elastic service level runs on Azure infrastructure and provides built‑in zonal redundancy with low single‑digit millisecond latency.
 
 * **Elastic service level (preview)**:
     Elastic is an advanced, high-availability service level designed to deliver continuous data access with zero data loss even if an entire Azure Availability Zone becomes unavailable. This service eliminates single points of failure, making it ideal for mission-critical workloads that require uncompromising resilience and in-region data protection.

articles/azure-netapp-files/elastic-zone-redundant-concept.md

@@ -1,5 +1,5 @@
 ---
-title: Understand Azure NetApp Files zone-redundant storage service level
+title: Understand Azure NetApp Files Elastic zone-redundant storage service level
 description: Understand the unique qualities of Elastic zone-redundant storage, which delivers built-in local redundancy is designed as a more affordable alternative. 
 services: azure-netapp-files
 author: b-ahibbard
@@ -10,7 +10,7 @@ ms.author: anfdocs
 ms.custom: references-regions 
 ---
 
-# Understand Azure NetApp Files zone-redundant storage service level (preview)
+# Understand Azure NetApp Files Elastic zone-redundant storage service level (preview)
 
 Azure NetApp Files Elastic zone-redundant storage is a high-availability storage service level for Azure NetApp Files that synchronously replicates your data across multiple Azure Availability Zones in a single region. This means if one zone experiences an outage, your data and applications remain available from the other zones with zero data loss. Azure NetApp Files Elastic zone-redundant storage delivers similar enterprise-grade features as other Azure NetApp Files service levels (support for NFSv3, NFSv4.1, SMB, snapshots, clones, encryption, backup) but with built-in multi-availability zone redundancy. It eliminates single points of failure, ensuring continuous data access even during an entire zone outage.
 

articles/azure-netapp-files/whats-new.md

@@ -19,11 +19,11 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## January 2026
 
-* [Elastic zone-redundant service level](elastic-zone-redundant-concept.md) (preview)
+* [Elastic zone-redundant storage service level](elastic-zone-redundant-concept.md) (preview)
 
-    Azure NetApp Files Elastic zone-redundant storage is an advanced high-availability service level for Azure NetApp Files that provides continuous data access with zero data loss, even if an entire Azure Availability Zone goes offline. Built on Azure’s Zone-redundant storage (ZRS) architecture and compute infrastructure, Azure NetApp Files Elastic zone-redundant storage synchronously replicates file data across availability zones within one region. By eliminating single points of failure, it ensures mission-critical workloads remain online and protected without requiring special configuration or manual intervention. This makes it ideal for applications that demand uncompromising resilience and in-region data protection. 
+    Azure NetApp Files Elastic zone-redundant storage service level is an advanced high-availability service level for Azure NetApp Files that provides continuous data access with zero data loss, even if an entire Azure Availability Zone goes offline. Built on Azure’s Zone-redundant storage (ZRS) architecture and compute infrastructure, Azure NetApp Files Elastic zone-redundant storage synchronously replicates file data across availability zones within one region. By eliminating single points of failure, it ensures mission-critical workloads remain online and protected without requiring special configuration or manual intervention. This makes it ideal for applications that demand uncompromising resilience and in-region data protection. 
 
-    As a modern data platform, Azure NetApp Files Elastic zone-redundant storage provides consistent performance for metadata-heavy workloads across VMs and containers, making it well suited for AI, analytics, and Kubernetes/OpenShift environments. Whether you’re running SAP shared files, AKS and containerized apps, cloud‑native applications, or general file shares, Azure NetApp Files Elastic zone-redundant storage delivers continuity without compromise, cost‑effective scalability, and operational simplicity. You can create volumes as small as 1 GiB, giving you the flexibility to optimize storage for workloads of any size. 
+    As a modern data platform, Azure NetApp Files Elastic zone-redundant storage provides consistent performance for metadata-heavy workloads across VMs and containers, making it well suited for AI, analytics, and Kubernetes/OpenShift environments. Whether you're running AKS and containerized apps, cloud‑native applications, or general file shares, Azure NetApp Files Elastic zone-redundant storage delivers continuity without compromise, cost‑effective scalability, and operational simplicity. You can create volumes as small as 1 GiB, giving you the flexibility to optimize storage for workloads of any size. 
 
 * [Application volume group for Oracle](configure-application-volume-oracle-api.md#replication) support for cross-zone and cross-region replication is now generally available (GA)
 

articles/container-apps/plans.md

@@ -1,24 +1,24 @@
 ---
-title: Azure Container Apps plan types
-description: Compare different plans available in Azure Container Apps
+title: Azure Container Apps Plan Types
+description: Compare the plans that are available in Azure Container Apps.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom:
   - ignite-2024
-ms.topic: conceptual
-ms.date: 11/05/2024
+ms.topic: concept-article
+ms.date: 01/28/2026
 ms.author: cshoe
 ---
 
 # Azure Container Apps plan types
 
-Azure Container Apps features two different plan types.
+Azure Container Apps features two plan types:
 
 | Plan type | Description |
 |--|--|
-| [Dedicated](#dedicated) | Fully managed environment with support for scale-to-zero and pay only for resources your apps use. Run apps with customized hardware and increased cost predictability using Dedicated [workload profiles](workload-profiles-overview.md) in the default workload profiles environment. |
-| [Consumption](#consumption) | Serverless environment with support for scale-to-zero and pay only for resources your apps use. |
+| [Dedicated](#dedicated) | Fully managed environment with support for scale-to-zero and paying only for resources that your apps use. Run apps with customized hardware and increased cost predictability by using Dedicated [workload profiles](workload-profiles-overview.md) in the default workload profiles environment. |
+| [Consumption](#consumption) | Serverless environment with support for scale-to-zero and paying only for resources that your apps use. |
 
 <a id="consumption-dedicated"></a>
 
@@ -27,28 +27,28 @@ Azure Container Apps features two different plan types.
 The Dedicated plan consists of a series of workload profiles that range from the default consumption profile to profiles that feature dedicated hardware customized for specialized compute needs.  
 
 You can select from general purpose or specialized compute
-[workload profiles](workload-profiles-overview.md) that provide larger amounts of CPU and memory or GPU enabled features. You pay per instance of the workload profile, versus per app, and workload profiles can scale in and out as demand rises and falls.
+[workload profiles](workload-profiles-overview.md) that provide larger amounts of CPU and memory or GPU-enabled features. You pay per instance of the workload profile, versus per app, and workload profiles can scale in and out as demand rises and falls.
 
 Use the Dedicated plan when you need any of the following in a single environment:
 
 - **Compute isolation**: Dedicated workload profiles provide access to dedicated hardware with a single tenant guarantee.
 
-- **Customized compute**: Select from many types and sizes of workload profiles based on your apps requirements. You can deploy many apps to each workload profile. Each workload profile can scale independently as more apps are added or removed or as apps scale their replicas up or down.
+- **Customized compute**: Select from many types and sizes of workload profiles based on your app requirements. You can deploy many apps to each workload profile. Each workload profile can scale independently as more apps are added or removed or as apps scale their replicas up or down.
 
-    The Dedicated plan can be more cost effective when you're running higher scale deployments with steady throughput.
+    The Dedicated plan can be more cost effective when you're running higher-scale deployments with steady throughput.
 
 > [!NOTE]
 > When configuring your cluster with a user defined route for egress, you must explicitly send egress traffic to a network virtual appliance such as Azure Firewall.
 
 ## Consumption
 
-The Consumption plan features a serverless architecture that allows your applications to scale in and out on demand. Applications can scale to zero, and you only pay for running apps.
+The Consumption plan features a serverless architecture that enables your applications to scale in and out on demand. Applications can scale to zero, and you only pay for running apps.
 
-When you need on-demand specialized compute resources, you can use [serverless GPUs (preview)](gpu-serverless-overview.md).
+When you need on-demand specialized compute resources, you can use [serverless GPUs](gpu-serverless-overview.md).
 
-## Next steps
+## Next step
 
-Deploy an app with:
+Deploy an app with a:
 
 - [Consumption plan](quickstart-portal.md)
 - [Dedicated plan](workload-profiles-manage-cli.md)