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/service-limits.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn about service limits in Azure API Management, including their
4
4
author: dlepow
5
5
ms.service: azure-api-management
6
6
ms.topic: concept-article
7
-
ms.date: 09/09/2025
7
+
ms.date: 10/22/2025
8
8
ms.author: danlep
9
9
ai-usage: ai-assisted
10
10
---
@@ -27,7 +27,9 @@ Resource limits are interrelated and tuned to work together. They prevent any si
27
27
28
28
## Changes to service limits in Classic tiers
29
29
30
-
Starting in November 2025, Azure API Management is updating the service limits in the Classic (Developer, Basic, Standard, and Premium) and Consumption tiers to better reflect the capabilities of the service and help customers make decisions when choosing an API Management tier for their needs. Limits for Classic tiers are published [here](/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-classic-tiers).
30
+
Starting March 2026, Azure API Management will apply updated limits to instances in the Classic tiers (Developer, Basic, Standard, and Premium) and the Consumption tier. These updates align with each tier’s capabilities and help customers choose the right option for their needs.
31
+
32
+
Current limits for Classic tiers are published [here](/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-classic-tiers). By March 2026, the scope of entities with limits could be reduced.
31
33
32
34
### What's changing
33
35
@@ -55,7 +57,7 @@ If you're approaching or have reached certain resource limits, consider these st
55
57
56
58
### Optimize API and operation organization
57
59
58
-
When counting the number of APIs and API-related resource (such as API operations, backends, tags, and so on), API Management also includes API versions and revisions. Consider the following strategies when approaching limits for these resources:
60
+
When counting the number of APIs and API-related resources (such as API operations, backends, tags, and so on), API Management also includes API versions and revisions. Consider the following strategies when approaching limits for these resources:
59
61
60
62
* Remove unused API versions or revisions
61
63
* Consolidate or remove operations where appropriate
@@ -73,10 +75,9 @@ If you're consistently hitting resource limits, it may be worth evaluating your
73
75
74
76
In some cases, you may want to request an increase to certain service limits. Before doing so, note the following guidelines:
75
77
78
+
* Explore strategies to address the issue proactively before requesting a limit increase. See the preceding [Strategies to manage resources](#strategies-to-manage-resources) section for more information.
76
79
77
-
* Explore strategies to address the issue proactively before requesting a limit increase. See the [Strategies to manage resources](#strategies-to-manage-resources) section for more information.
78
-
79
-
* Consider potential impacts of the limit increase on overall service performance and stability. Increasing a limit might affect service capacity or cause increased latency in some service operations.
80
+
* Consider potential impacts of the limit increase on overall service performance and stability. Increasing a limit might affect your service's capacity or cause increased latency in some service operations.
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-how-to-azure-devops.md
+71-1Lines changed: 71 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,7 @@ Choose your task version at the top of the article.
40
40
* If you plan to use GitHub instead of Azure Repos, you also need a GitHub repository. If you don't have a GitHub account, you can [create one for free](https://github.com).
41
41
42
42
* An existing function app in Azure that has its source code in a supported repository. If you don't yet have an Azure Functions code project, you can create one by completing the following language-specific article:
43
+
43
44
### [C\#](#tab/csharp)
44
45
45
46
[Quickstart: Create a C# function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-csharp)
@@ -56,9 +57,13 @@ Choose your task version at the top of the article.
56
57
57
58
[Quickstart: Create a PowerShell function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-powershell)
58
59
60
+
### [Java](#tab/java)
61
+
62
+
[Quickstart: Create a Java function in Azure using Visual Studio Code](how-to-create-function-vs-code.md?pivot=programming-language-java)
63
+
59
64
---
60
65
61
-
Remember to upload the local code project to your GitHub or Azure Repos repository after you publish it to your function app.
66
+
Remember to upload the local code project to your GitHub or Azure Repos repository after you publish it to your function app.
62
67
63
68
## Build your app
64
69
@@ -74,6 +79,7 @@ Choose your task version at the top of the article.
74
79
### Example YAML build pipelines
75
80
76
81
The following language-specific pipelines can be used for building apps.
82
+
77
83
#### [C\#](#tab/csharp)
78
84
79
85
You can use the following sample to create a YAML file to build a .NET app:
0 commit comments