Merge pull request #308804 from simonjj/wp-flex-updates

fixing official Flex naming and updating CLI output sample to include…

Author: prmerger-automator[bot]

articles/container-apps/workload-profiles-manage-cli.md

@@ -190,7 +190,7 @@ az containerapp env workload-profile add \
   --max-nodes <MAX_NODES>
 ```
 
-The value you select for the `<WORKLOAD_PROFILE_NAME>` placeholder is the workload profile *friendly name*.
+When selecting a workload profile to add it is important to ensure regional availability. The value you select for the `<WORKLOAD_PROFILE_NAME>` placeholder is the workload profile *friendly name*.
 
 Using friendly names allow you to add multiple profiles of the same type to an environment. The friendly name is what you use as you deploy and maintain a container app in a workload profile.
 
@@ -242,16 +242,23 @@ az containerapp env workload-profile list-supported \
 The response resembles a table similar to the below example:
 
 ```output
-Name         Cores    MemoryGiB    Category
------------  -------  -----------  ---------------
-D4           4        16           GeneralPurpose
-D8           8        32           GeneralPurpose
-D16          16       64           GeneralPurpose
-E4           4        32           MemoryOptimized
-E8           8        64           MemoryOptimized
-E16          16       128          MemoryOptimized
-E32          32       256          MemoryOptimized
-Consumption  4        8            Consumption
+Name                       Cores    MemoryGiB    Category
+-------------------------  -------  -----------  --------------------
+D4                         4        16           GeneralPurpose
+D8                         8        32           GeneralPurpose
+D16                        16       64           GeneralPurpose
+D32                        32       128          GeneralPurpose
+E4                         4        32           MemoryOptimized
+E8                         8        64           MemoryOptimized
+E16                        16       128          MemoryOptimized
+E32                        32       256          MemoryOptimized
+Consumption                4        8            Consumption
+Consumption-GPU-NC24-A100  24       220          Consumption-GPU-A100
+Consumption-GPU-NC8as-T4   8        56           Consumption-GPU-T4
+Flex                       4        16           Consumption
+NC24-A100                  24       220          GPU-NC-A100
+NC48-A100                  48       440          GPU-NC-A100
+NC96-A100                  96       880          GPU-NC-A100
 ```
 
 Select a workload profile and use the *Name* field when adding or updating workload profiles with the `az containerapp env workload-profile add` or `az containerapp env workload-profile update` commands for the `--workload-profile-type` option.

articles/container-apps/workload-profiles-overview.md

@@ -29,12 +29,12 @@ Each profile type determines how your apps scale, the level of resource isolatio
 
 - **Dedicated profiles** run on reserved compute resources in your own dedicated pool. You select the size and type of virtual machine, deploy multiple apps per profile, and pay per-profile instance. Dedicated profiles can be more cost-effective for steady workloads and support general purpose, memory-optimized, and GPU use cases.
 
-- **Flex profiles** (preview) blends the billing and setup simplicity of the *Consumption* profile with many of the performance characteristics of the Dedicated profiles. Flex profiles are billed like a Consumption profile plus the dedicated management fee, run in a single‑tenant compute pool, offer planned maintenance windows, and dedicated networking and access to larger replica sizes. Flex profiles require a subnet of at least `/25`.
+- **Flexible profile** (preview) blends the billing and setup simplicity of the *Consumption* profile with many of the performance characteristics of the Dedicated profiles. Flexible profiles are billed like a Consumption profile plus the dedicated management fee, run in a single‑tenant compute pool, offer planned maintenance windows, and dedicated networking and access to larger replica sizes. Flexible profiles require a subnet of at least `/25`.
 
-Each Container Apps environment includes a default Consumption profile. You can add Dedicated or Consumption GPU profiles and, when available, Flex profiles to meet your application's needs.
+Each Container Apps environment includes a default Consumption profile. You can add Dedicated or Consumption GPU profiles and, when available, Flexible profiles to meet your application's needs.
 
 > [!NOTE]
-> The Flex profile is currently only available in the following regions: Central US EUAP, East US2 EUAP, East Asia, and West Central US.
+> The Flexible profile is currently only available in the following regions: Central US EUAP, East US2 EUAP, East Asia, and West Central US.
 
 ## Workload profile form factors
 
@@ -76,11 +76,11 @@ All Consumption profiles support serverless scaling and are billed based on per
 > [!NOTE]
 > GPU‑enabled Dedicated profiles allocate capacity on a per‑case basis. [You must submit a support ticket to request the required capacity](/azure/container-apps/quotas#gpu-quotas).
 
-### Flex profile details (preview)
+### Flexible profile details (preview)
 
 | Profile names | vCPU range | Memory range | Regions | Allocation |
 |--|--|--|--|--|
-| **Flex** | 0.25-4 | 0.5-16 GiB | Central US (EUAP), East US2 (EUAP), East Asia, West Central US | per replica |
+| **Flexible** | 0.25-4 | 0.5-16 GiB | Central US (EUAP), East US2 (EUAP), East Asia, West Central US | per replica |
 
 ## Resource consumption and scaling