You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JSON Content Type Handling | [GA](./reference-dotnet-provider.md#json-content-type-handling) | GA | GA | GA | [GA](./reference-javascript-provider.md#json-content-type-handling) | [GA](./reference-go-provider.md#json-content-type-handling)
57
57
JSON with Comments | [GA](./reference-dotnet-provider.md#json-content-type-handling) | GA | GA | GA | [GA](./reference-javascript-provider.md#json-content-type-handling) | [GA](./reference-go-provider.md#json-content-type-handling)
Key Vault References | [GA](./reference-dotnet-provider.md#key-vault-reference) | GA | GA | GA | [GA](./reference-javascript-provider.md#key-vault-reference) | [GA](./reference-go-provider.md#key-vault-reference)
Feature Flags | [GA](./reference-dotnet-provider.md#feature-flag) | GA | GA | GA | [GA](./reference-javascript-provider.md#feature-flag) | [GA](./reference-go-provider.md#feature-flags)
64
-
Variant Feature Flags | [GA](./reference-dotnet-provider.md#feature-flag) | Preview | GA | GA | [GA](./reference-javascript-provider.md#feature-flag) | [GA](./reference-go-provider.md#feature-flags)
65
-
Feature Flag Telemetry | [GA](./reference-dotnet-provider.md#feature-flag-telemetry) | Preview | GA | GA | GA | WIP
64
+
Variant Feature Flags | [GA](./reference-dotnet-provider.md#feature-flag) | GA | GA | GA | [GA](./reference-javascript-provider.md#feature-flag) | [GA](./reference-go-provider.md#feature-flags)
65
+
Feature Flag Telemetry | [GA](./reference-dotnet-provider.md#feature-flag-telemetry) | GA | GA | GA | GA | WIP
66
66
Key Prefix Trim | [GA](./reference-dotnet-provider.md#trim-prefix-from-keys) | GA | GA | GA | [GA](./reference-javascript-provider.md#trim-prefix-from-keys) | [GA](./reference-go-provider.md#trim-prefix-from-keys)
Replica Auto Discovery | [GA](./reference-dotnet-provider.md#geo-replication) | GA | GA | GA | [GA](./reference-javascript-provider.md#geo-replication) | [GA](./reference-go-provider.md#geo-replication)
69
69
Replica Failover | [GA](./reference-dotnet-provider.md#geo-replication) | GA | GA | GA | [GA](./reference-javascript-provider.md#geo-replication) | [GA](./reference-go-provider.md#geo-replication)
70
-
Replica Load Balancing | [GA](./reference-dotnet-provider.md#geo-replication) | WIP | GA | GA | [GA](./reference-javascript-provider.md#geo-replication) | [GA](./reference-go-provider.md#geo-replication)
71
-
Snapshots | [GA](./reference-dotnet-provider.md#snapshot) | GA | GA | WIP | [GA](./reference-javascript-provider.md#snapshot) | [GA](./reference-go-provider.md#snapshot)
70
+
Replica Load Balancing | [GA](./reference-dotnet-provider.md#geo-replication) | GA | GA | GA | [GA](./reference-javascript-provider.md#geo-replication) | [GA](./reference-go-provider.md#geo-replication)
71
+
Snapshots | [GA](./reference-dotnet-provider.md#snapshot) | GA | GA | GA | [GA](./reference-javascript-provider.md#snapshot) | [GA](./reference-go-provider.md#snapshot)
Health Check | [GA](./reference-dotnet-provider.md#health-check) | GA | WIP | WIP | WIP | N/A
74
74
Select by Tag Filters | [GA](./reference-dotnet-provider.md#load-specific-key-values-using-selectors) | WIP | GA | GA | [GA](./reference-javascript-provider.md#tag-filters) | [GA](./reference-go-provider.md#tag-filters)
Time Window Filter | [GA](./feature-management-dotnet-reference.md#microsofttimewindow) | GA | [GA](./feature-management-python-reference.md#microsofttimewindow) | [GA](./feature-management-javascript-reference.md#microsofttimewindow) | [GA](./feature-management-go-reference.md#microsofttimewindow)
47
47
Recurring Time Window | [GA](./feature-management-dotnet-reference.md#microsofttimewindow) | GA | GA | [GA](./feature-management-javascript-reference.md#microsofttimewindow) | WIP
Copy file name to clipboardExpand all lines: articles/cdn/cdn-app-dev-node.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,12 @@
2
2
title: Get started with the Azure CDN SDK for Node.js
3
3
description: Learn how to create a simple Node.js console application that demonstrates how to automate creation and management of Azure CDN profiles and endpoints.
4
4
services: cdn
5
-
author: zhangmanling
6
-
manager: erikre
5
+
author: cynthn
6
+
manager: akashdubey
7
7
ms.service: azure-cdn
8
8
ms.topic: how-to
9
9
ms.date: 03/31/2025
10
-
ms.author: erikre
10
+
ms.author: cynthn
11
11
ms.custom: devx-track-js
12
12
ROBOTS: NOINDEX
13
13
# Customer intent: As a developer, I want to create and manage Azure CDN profiles and endpoints using Node.js, so that I can automate content delivery network operations in my applications.
Copy file name to clipboardExpand all lines: articles/container-apps/billing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.author: cshoe
14
14
15
15
# Billing in Azure Container Apps
16
16
17
-
Billing in Azure Container Apps depends on your [plan type](plans.md) (Consumption or Dedicated). Your plan type depends on the environmenttype you select.
17
+
Billing in Azure Container Apps depends on your [plan type](plans.md) (Consumption or Dedicated). Your plan type depends on the workload profile you use within your environment. The default environment type is workload profiles, which supports both Consumption and Dedicated plans.
Copy file name to clipboardExpand all lines: articles/container-apps/environment-type-consumption-only.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Consumption-only environment type in Azure Container Apps
3
-
description: Learn about features and billing considerations for Consumption-only environment types in Azure Container Apps.
2
+
title: Consumption-only environment type in Azure Container Apps (legacy)
3
+
description: Learn about features and billing considerations for the legacy Consumption-only environment type in Azure Container Apps.
4
4
services: container-apps
5
5
author: craigshoemaker
6
6
ms.service: azure-container-apps
@@ -9,15 +9,18 @@ ms.date: 02/05/2025
9
9
ms.author: cshoe
10
10
---
11
11
12
-
# Consumption-only environment type in Azure Container Apps
12
+
# Consumption-only environment type in Azure Container Apps (legacy)
13
+
14
+
> [!NOTE]
15
+
> The Consumption-only environment type is a legacy option. For new Container Apps environments, the *Workload profiles (v2)* environment type is the default and recommended choice.
13
16
14
17
In Azure Container Apps, there are two environment types which determine what features are available to your applications.
15
18
16
19
The Consumption-only environment runs your application using compute resources exclusively allocated on-demand. In other words, you only pay for resources consumed by your application.
17
20
18
21
This article explains features of the *Consumption-only (v1)* environment type. For more information on the default *Workload profiles (v2)* environment type, see [Compute and billing structures in Azure Container Apps](structure.md).
19
22
20
-
While Consumption-only environments are an option, for new Container Apps environmentsthat need the consumption model, creating a *Workload profiles v2* environment with the built-in [consumption workload profile](./structure.md#workload-profiles) is recommended.
23
+
While Consumption-only environments are still an option, the *Workload profiles (v2)* environment type is now the default when creating new Container Apps environments. For environments that need the consumption model, the built-in [consumption workload profile](./structure.md#workload-profiles) in a *Workload profiles v2* environment is recommended.
21
24
22
25
The Consumption-only environment type works on the consumption plan. Apps running in the Consumption-only have access to 4 vCPUs with 8 GB of memory. There's no access to GPUs in a Consumption-only environment.
23
26
@@ -33,7 +36,7 @@ Yes, but there are some distinctions between how the consumption plan operates a
33
36
34
37
### I need consumption pricing. Should I use a Consumption-only (v1) environment, or a Workload profiles (v2) environment with the consumption profile?
35
38
36
-
If you need the features of a consumption model, and you're creating a new Azure Container Apps environment, use the *Workload profiles (v2)* environment with the consumption profile. Using this approach gives you the flexibility to add dedicated resources to your environment should you need them in the future.
39
+
Use the *Workload profiles (v2)* environment with the consumption profile. This the default environment type when creating new Container Apps environments. This approach gives you the flexibility to add dedicated resources to your environment should you need them in the future, along with access to improved networking features.
Copy file name to clipboardExpand all lines: articles/container-apps/environment.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Environments include the following features:
18
18
19
19
| Feature | Description |
20
20
|---|---|
21
-
| Type | There are [two different types](#types) of Container Apps environments: Workload profiles environments and Consumption only environments. Workload profiles environments support both the Consumption and Dedicated [plans](plans.md) whereas Consumption only environments support only the Consumption [plan](plans.md). |
21
+
| Type | There are [two different types](#types) of Container Apps environments: Workload profiles environments (the default) and Consumption only environments (legacy). Workload profiles environments support both the Consumption and Dedicated [plans](plans.md) whereas Consumption only environments support only the Consumption [plan](plans.md). |
22
22
| Virtual network | A virtual network supports each environment, which enforces the environment's secure boundaries. As you create an environment, a virtual network with [limited network capabilities](networking.md) is created for you, or you can provide your own. Adding an [existing virtual network](vnet-custom.md) gives you fine-grained control over your network. |
23
23
| Multiple container apps | When multiple container apps are in the same environment, they share the same virtual network and write logs to the same logging destination. |
24
24
| Multi-service integration | You can add [Azure Functions](../container-apps/functions-overview.md) and [Azure Spring Apps](https://aka.ms/asaonaca) to your Azure Container Apps environment. |
@@ -49,8 +49,8 @@ Use more than one environment when you want two or more applications to:
49
49
50
50
| Type | Description | Plan | Billing considerations |
51
51
|--|--|--|--|
52
-
| Workload profile | Run serverless apps with support for scale-to-zero and pay only for resources your apps use with the consumption profile. You can also run apps with customized hardware and increased cost predictability by using dedicated workload profiles. | Consumption and Dedicated | You can choose to run apps under either or both plans by using separate workload profiles. The Dedicated plan has a fixed plan management cost for the entire environment regardless of how many workload profiles you're using. The Dedicated plan also has a variable cost based on the number of workload profile instances and the resources allocated to each instance. For more information, see [Billing](billing.md#dedicated-plan). |
53
-
| Consumption only | Run serverless apps with support for scale-to-zero and pay only for resources your apps use. | Consumption only | Billed only for individual container apps and their resource usage. There's no cost associated with the Container Apps environment. |
52
+
| Workload profile (default) | Run serverless apps with support for scale-to-zero and pay only for resources your apps use with the consumption profile. You can also run apps with customized hardware and increased cost predictability by using dedicated workload profiles. | Consumption and Dedicated | You can choose to run apps under either or both plans by using separate workload profiles. The Dedicated plan has a fixed plan management cost for the entire environment regardless of how many workload profiles you're using. The Dedicated plan also has a variable cost based on the number of workload profile instances and the resources allocated to each instance. For more information, see [Billing](billing.md#dedicated-plan). |
53
+
| Consumption only (legacy) | Run serverless apps with support for scale-to-zero and pay only for resources your apps use. | Consumption only | Billed only for individual container apps and their resource usage. There's no cost associated with the Container Apps environment. |
Copy file name to clipboardExpand all lines: articles/container-apps/firewall-integration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ In the workload profiles environment, user-defined routes (UDRs) and [securing o
22
22
23
23
When using an external workload profiles environment, inbound traffic to Azure Container Apps is routed through the public IP that exists in the [managed resource group](./networking.md#ports-and-ip-addresses) rather than through your subnet. This means that locking down inbound traffic via NSG or Firewall on an external workload profiles environment isn't supported. For more information, see [Control outbound traffic with user defined routes](./user-defined-routes.md).
24
24
25
-
In the Consumption only environment, express routes aren't supported, and custom user-defined routes (UDRs) have limited support. For more information on the level of UDR support available in a Consumption-only environment, see the [FAQ](faq.yml#do-consumption-only-environments-support-custom-user-defined-routes-).
25
+
In the legacy Consumption only environment, express routes aren't supported, and custom user-defined routes (UDRs) have limited support. For more information on the level of UDR support available in a Consumption-only environment, see the [FAQ](faq.yml#do-consumption-only-environments-support-custom-user-defined-routes-).
Copy file name to clipboardExpand all lines: articles/container-apps/functions-container-apps.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,10 +64,10 @@ Use these commands to create your required Azure resources:
64
64
65
65
This `az group create` command creates a resource group in the East US region. If you instead want to use a region near you, using an available region code returned from the `az account list-locations` command. You must modify subsequent commands to use your custom region instead of `eastus`.
66
66
67
-
1. Create Azure Container App environment with workload profiles enabled.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments