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
Copy file name to clipboardExpand all lines: articles/api-management/automate-portal-deployments.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
@@ -26,7 +26,7 @@ You can automate the migration of content between two API Management services, f
26
26
> Using the script to migrate developer portal content between an API Management instance in a classic tier (for example, Standard) and an instance in a v2 tier (for example, Standard v2) isn't currently supported. Migration of portal content between instances in the v2 tiers is also not supported.
27
27
28
28
> [!NOTE]
29
-
> If you're using a self-hosted developer portal with an explicitly defined custom storage account to host media files (that is, you define the `blobStorageUrl` setting in the `config.design.json` configuration file), you need to use the [original `scripts.v2/migrate.js` script](https://github.com/Azure/api-management-developer-portal/blob/master/scripts.v2/migrate.js). The original script doesn't work for managed or self-hosted portals with the media storage account managed by API Management. In that case, use the script from the `/scripts.v3` folder instead.
29
+
> If you're using a self-hosted developer portal with an explicitly defined custom storage account to host media files (that is, you define the `blobStorageUrl` setting in the `config.design.json` configuration file), you need to use the [original `scripts.v3/migrate.js` script](https://github.com/Azure/api-management-developer-portal/blob/master/scripts.v3/migrate.js). The original script doesn't work for managed or self-hosted portals with the media storage account managed by API Management. In that case, use the script from the `/scripts.v3` folder instead.
Copy file name to clipboardExpand all lines: articles/api-management/backends.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: api-management
5
5
author: dlepow
6
6
ms.service: azure-api-management
7
7
ms.topic: concept-article
8
-
ms.date: 11/14/2025
8
+
ms.date: 11/20/2025
9
9
ms.author: danlep
10
10
ms.custom:
11
11
- build-2024
@@ -113,6 +113,8 @@ To add CA certificate details, follow these steps:
113
113
1. Select **Add**.
114
114
1. Select **Create**.
115
115
116
+
:::image type="content" source="media/backends/ca-certificate.png" alt-text="Screenshot of configuring CA certificate details for a backend in the portal.":::
117
+
116
118
> [!NOTE]
117
119
> When you configure details of a custom CA certificate in the backend entity, API Management always validates the certificate name and certificate chain, regardless of whether you enable or disable validation settings in the backend's `backendTlsProperties`.
Copy file name to clipboardExpand all lines: articles/api-management/v2-service-tiers-overview.md
+31-25Lines changed: 31 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: dlepow
6
6
7
7
ms.service: azure-api-management
8
8
ms.topic: concept-article
9
-
ms.date: 11/11/2025
9
+
ms.date: 11/21/2025
10
10
ms.author: danlep
11
11
ms.custom:
12
12
- references_regions
@@ -25,7 +25,7 @@ The following v2 tiers are generally available:
25
25
26
26
***Standard v2** - Standard v2 is a production-ready tier with support for network-isolated backends.
27
27
28
-
***Premium v2** - Premium v2 offers enterprise features including full virtual network isolation, scaling for high volume workloads, availability zones, and workspaces.
28
+
***Premium v2** - Premium v2 offers enterprise features including full virtual network isolation, scaling for high volume workloads, availability zones, and workspaces.[Read the blog post](https://techcommunity.microsoft.com/blog/integrationsonazureblog/announcing-the-general-availability-ga-of-the-premium-v2-tier-of-azure-api-manag/4471499) announcing general availability.
29
29
30
30
## Key capabilities
31
31
@@ -58,26 +58,36 @@ For a current list of regions where the v2 tiers are available, see [Availabilit
58
58
59
59
### Classic feature availability
60
60
61
-
Most capabilities of the classic API Management tiers are supported in the v2 tiers. However, the following capabilities aren't supported in the v2 tiers:
61
+
Most capabilities of the classic API Management tiers are supported directly in the v2 tiers. However, some features have replacements in the v2 tiers, and some currently aren't available. For detailed comparisons, see
62
62
63
-
* API Management service configuration using Git
64
-
* Back up and restore of API Management instance
65
-
* Enabling Azure DDoS Protection
66
-
* Direct Management API access
63
+
*[Feature-based comparison of the Azure API Management tiers](api-management-features.md)
|[CA certificates](api-management-howto-ca-certificates.md) managed in the global certificate list | CA certificates referenced in [backend](backends.md#configure-certificates-for-authorization-credentials) entity |
72
+
|[Capacity](api-management-capacity.md#available-capacity-metrics) metric |[CPU Percentage of Gateway and Memory Percentage of Gateway](api-management-capacity.md#available-capacity-metrics) metrics<sup>1</sup> |
67
73
68
-
### Limitations
74
+
<sup>1</sup> Also available in the classic tiers.
69
75
70
-
The following API Management capabilities are currently unavailable in the v2 tiers.
71
76
72
-
**Infrastructure and networking**
77
+
#### Currently unavailable features
78
+
79
+
The following are currently unavailable in the v2 tiers.
80
+
81
+
**Infrastructure and configuration**
73
82
* Multi-region deployment
74
83
* Multiple custom domain names
75
-
* Capacity metric - *replaced by CPU Percentage of Gateway and Memory Percentage of Gateway metrics*
76
-
* Built-in analytics - *replaced by Azure Monitor-based dashboard*
77
-
* CA certificates - *replaced by CA certificates in backend entity*
78
84
* Sending events to Event Grid
79
85
* Event Hubs event metrics
80
-
* Upgrade to v2 tiers from classic tiers
86
+
* API Management service configuration using Git
87
+
* Enabling Azure DDoS Protection
88
+
* Direct Management API access
89
+
* Back up and restore of API Management instance
90
+
* Upgrade to v2 tiers from classic tiers
81
91
82
92
**Developer portal**
83
93
* Reports
@@ -92,15 +102,11 @@ The following API Management capabilities are currently unavailable in the v2 ti
92
102
93
103
## Resource limits
94
104
95
-
The following resource limits apply to the v2 tiers.
The following resource limits apply to the v2 tiers:
100
106
101
-
The following limits apply to the developer portal in the v2 tiers.
107
+
*[Resource limits for v2 tiers](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=%2Fazure%2Fapi-management%2Fbreadcrumb%2Ftoc.json#limits---api-management-v2-tiers)
108
+
*[Developer portal limits for v2 tiers](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=%2Fazure%2Fapi-management%2Fbreadcrumb%2Ftoc.json#limits---developer-portal-in-api-management-v2-tiers)
@@ -112,10 +118,6 @@ Deploy a v2 tier instance using the Azure portal or using tools such as the Azur
112
118
113
119
A: No. Currently you can't migrate an existing API Management instance (in the Consumption, Developer, Basic, Standard, or Premium tier) to a new v2 tier instance. Currently the v2 tiers are available for newly created service instances only.
114
120
115
-
### Q: What's the relationship between the stv2 compute platform and the v2 tiers?
116
-
117
-
A: They're not related. stv2 is a compute platform version of the Developer, Basic, Standard, and Premium tier service instances. stv2 is a successor to the stv1 compute platform that retired in 2024.
118
-
119
121
### Q: Will I still be able to provision Developer, Basic, Standard, or Premium tier services?
120
122
121
123
A: Yes, there are no changes to the classic Developer, Basic, Standard, or Premium tiers.
@@ -130,6 +132,10 @@ The Premium tier and Premium v2 tier support full network isolation by deploymen
130
132
131
133
A: No, such a deployment is only supported in the Premium and Premium v2 tiers.
132
134
135
+
### Q: What's the relationship between the stv2 compute platform and the v2 tiers?
136
+
137
+
A: They're not related. stv2 is a compute platform version of the Developer, Basic, Standard, and Premium tier service instances. stv2 is a successor to the stv1 compute platform that retired in 2024.
138
+
133
139
## Related content
134
140
135
141
* Compare the API Management [tiers](api-management-features.md).
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments