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/active-directory-b2c/service-limits.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
@@ -8,7 +8,7 @@ manager: CelesteDG
8
8
ms.service: azure-active-directory
9
9
10
10
ms.topic: reference
11
-
ms.date: 08/19/2025
11
+
ms.date: 01/08/2026
12
12
ms.subservice: b2c
13
13
zone_pivot_groups: b2c-policy-type
14
14
@@ -186,7 +186,7 @@ The following table lists the administrative configuration limits in the Azure A
186
186
187
187
## Region specific service limits
188
188
189
-
As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits.
189
+
As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits. These limits apply to both SMS and Voice verification.
190
190
191
191
| Region Code | Region Name | Limit per tenant per 60 minutes | Limit per tenant per 24 hours |
Copy file name to clipboardExpand all lines: articles/api-center/includes/api-center-portal-compare-apim-dev-portal.md
+5-5Lines changed: 5 additions & 5 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-center
8
8
ms.topic: include
9
-
ms.date: 03/05/2025
9
+
ms.date: 01/13/2026
10
10
ms.author: danlep
11
11
ms.custom: Include file
12
12
---
@@ -15,10 +15,10 @@ ms.custom: Include file
15
15
16
16
The [Azure API Management](../../api-management/api-management-key-concepts.md) and [Azure API Center](../overview.md) services both provide portals for developers to discover and consume APIs:
17
17
18
-
* The *API Management developer portal* allows users to find managed APIs, learn how to use them, request access, and test them.
19
-
* The *API Center portal* (preview) is a multi-gateway portal where users can discover and filter the organization's complete API inventory.
18
+
* The *API Management developer portal* allows users to find managed APIs (including groups of APIs managed as products), learn how to use them, request access, and test them.
19
+
* The *API Center portal* (preview) is a multigateway portal where users can discover and filter the organization's complete API inventory.
20
20
21
-
While the two portals share some features, they also have distinct differences. The following table compares current capabilities to help determine which portal to use. Some organizations may prefer one portal, while others may need both.
21
+
While the two portals share some features, they also have distinct differences. The following table compares current capabilities to help determine which portal to use. Some organizations might prefer one portal, while others might need both.
22
22
23
23
| Feature | API Management developer portal | API Center portal (preview) |
24
24
| --- | --- | --- |
@@ -30,7 +30,7 @@ While the two portals share some features, they also have distinct differences.
30
30
| Add custom widgets | ✔️ | ❌ |
31
31
| Customize with WordPress | ✔️ | ❌ |
32
32
| Test APIs in test console | ✔️ | ✔️ |
33
-
| Subscribe to APIs | ✔️ | ❌ |
33
+
| Subscribe to APIs and products | ✔️ | ❌ |
34
34
| View API usage analytics | ✔️ | ❌ |
35
35
36
36
<sup>1</sup> The API Center portal can contain all APIs in your organization, including those managed in Azure API Management and other platforms, as well as unmanaged APIs and APIs under development.
Can I move an API Management instance from one subscription to another?
53
53
answer: |
54
-
Yes. To learn how, see [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).
54
+
Yes. To learn how, see [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md). Certain features or resources can't be moved and should be disabled or removed before the move, including:
55
+
56
+
* System-assigned or user-assigned managed identities.
57
+
* Virtual network subnet configurations.
55
58
56
59
- question: |
57
60
Can I manage my API Management instance programmatically?
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-use-managed-service-identity.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,8 @@ You can grant two types of identities to an API Management instance:
27
27
- A *user-assigned identity* is a standalone Azure resource that can be assigned to your service. The service can have multiple user-assigned identities.
28
28
29
29
> [!NOTE]
30
-
> Managed identities are specific to the Microsoft Entra tenant in which your Azure subscription is hosted. They don't get updated if a subscription is moved to a different directory. If a subscription is moved, you need to re-create and reconfigure the identities.
30
+
> - Managed identities are specific to the Microsoft Entra tenant in which your Azure subscription is hosted. They don't get updated if a subscription is moved to a different directory. If a subscription is moved, you need to recreate and reconfigure the identities.
31
+
> - API Management managed identities are also specific to the Azure subscription in which the service is hosted. If you move the service to a different subscription in the same tenant, you need to recreate and reconfigure the identities.
Copy file name to clipboardExpand all lines: articles/api-management/virtual-network-reference.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
@@ -63,7 +63,7 @@ NSG rules allowing outbound connectivity to Storage, SQL, and Azure Event Hubs s
63
63
64
64
## TLS functionality
65
65
66
-
To enable TLS/SSL certificate chain building and validation, the API Management service needs outbound network connectivity on ports `80` and `443` to `ocsp.msocsp.com`, `oneocsp.msocsp.com`, `mscrl.microsoft.com`, `crl.microsoft.com`, `cacerts.digicert.com`, `crl3.digicert.com` and `csp.digicert.com`.
66
+
To enable TLS/SSL certificate chain building and validation, the API Management service needs outbound network connectivity on ports `80` and `443` to `mscrl.microsoft.com`, `crl.microsoft.com`, `oneocsp.microsoft.com`, `cacerts.digicert.com`, `crl3.digicert.com` and `csp.digicert.com`.
Copy file name to clipboardExpand all lines: articles/app-service/environment/networking.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,6 +78,10 @@ You can bring your own inbound address to your App Service Environment. If you c
78
78
- For App Service Environment with external VIP, the Azure Public IP address resource must be in the same subscription as the App Service Environment.
79
79
- The inbound address can't be changed after the App Service Environment is created.
80
80
81
+
### ILB App Service Environment inbound traffic limitation
82
+
83
+
For App Service Environments with an internal VIP, inbound traffic to the front ends can be dropped if the source IP address falls within the infrastructure address range used for the App Service Environment's front ends. **Don't use source IP addresses in the `172.31.192.0/25` address space when connecting to an ILB App Service Environment**.
84
+
81
85
## Ports and network restrictions
82
86
83
87
For your app to receive traffic, ensure that inbound network security group (NSG) rules allow the App Service Environment subnet to receive traffic from the required ports. In addition to any ports you'd like to receive traffic on, you should ensure that Azure Load Balancer is able to connect to the subnet on port 80. This port is used for health checks of the internal virtual machine. You can still control port 80 traffic from the virtual network to your subnet.
"title": "Access to this resource is governed by a network access policy. The client IP address fails to meet the criteria for access.",
29
+
"title": "Access to this resource is governed by a network access policy. The client IP address fails to meet the criteria for access. See https://aka.ms/appconfig/network-access-errors for more information.",
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-dedicated-sku.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
@@ -57,7 +57,7 @@ Durable Task Scheduler offers two SKU options: Dedicated and Consumption (previe
57
57
58
58
The Dedicated SKU provides performance and pricing through preallocated Capacity Units (CUs). You can purchase up to three CUs.
59
59
60
-
Currently, you're limited to 15 task hubs when using the Dedicated SKU. For more quota, [contact support](https://github.com/Azure/azure-functions-durable-extension/issues).
60
+
Currently, you're limited to 25 task hubs when using the Dedicated SKU. For more quota, [contact support](https://github.com/Azure/azure-functions-durable-extension/issues).
Copy file name to clipboardExpand all lines: articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler.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
@@ -107,7 +107,7 @@ Creating multiple task hubs isolates different workloads that can be managed ind
107
107
- Create task hubs for different teams within your organization.
108
108
- Share the same scheduler instance across multiple apps.
109
109
110
-
Scheduler sharing is a great way to optimize cost when multiple teams have scenarios requiring orchestrations. Although you can create unlimited task hubs in one scheduler instance, they share the same resources; if one task hub is heavily loaded, it might affect the performance of the other task hubs.
110
+
Scheduler sharing is a great way to optimize cost when multiple teams have scenarios requiring orchestrations. Although you can create multiple task hubs in one scheduler instance, they share the same resources; if one task hub is heavily loaded, it might affect the performance of the other task hubs.
111
111
112
112
### Emulator for local development
113
113
@@ -160,7 +160,7 @@ Stale orchestration data should be purged periodically to ensure efficient stora
160
160
161
161
You're limited in how many task hubs you can use depending on your billing SKU.
162
162
163
-
-[When using the Dedicated SKU,](./durable-task-scheduler-dedicated-sku.md#dedicated-sku) task hubs are limited to 15.
163
+
-[When using the Dedicated SKU,](./durable-task-scheduler-dedicated-sku.md#dedicated-sku) task hubs are limited to 25.
164
164
-[When using the Consumption SKU,](./durable-task-scheduler-dedicated-sku.md#consumption-sku-preview) task hubs are limited to 5.
165
165
166
166
For more quota, [contact support](https://github.com/Azure/azure-functions-durable-extension/issues).
0 commit comments