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/partner-transmit-security.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
@@ -127,7 +127,7 @@ To integrating Transmit DRS into the B2C sign-in page, follow these steps:
127
127
128
128
Azure AD B2C can obtain a risk recommendation from Transmit using a [API connector](./add-api-connector.md). Passing this request through an intermediate web API (such as using [Azure Functions](/azure/azure-functions/)) provides more flexibility in your implementation logic.
129
129
130
-
Follow these steps to create an Azure function that uses the action token from the frontend application to get a recommendation from the [Transmit DRS endpoint](https://developer.transmitsecurity.com/openapi/risk/recommendations/#operation/getRiskRecommendation).
130
+
Follow these steps to create an Azure function that uses the action token from the frontend application to get a recommendation from the [Transmit DRS endpoint](https://developer.transmitsecurity.com/guides/risk/recommendations#operation/getRiskRecommendation).
131
131
132
132
1. Create the entry point of your Azure Function, an HTTP-triggered function that processes incoming HTTP requests.
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.
Copy file name to clipboardExpand all lines: articles/api-center/self-host-api-center-portal.md
+6-6Lines changed: 6 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: How to self-host the API Center portal, a customer-managed website
4
4
author: dlepow
5
5
ms.service: azure-api-center
6
6
ms.topic: how-to
7
-
ms.date: 03/04/2025
7
+
ms.date: 01/13/2026
8
8
ms.author: danlep
9
9
ms.custom:
10
10
# Customer intent: As an API program manager, I want to self-host a portal for developers and other API stakeholders in my organization to discover the APIs in my organization's API center.
@@ -65,20 +65,20 @@ Follow these steps to build and test the API Center portal locally.
65
65
```bash
66
66
git checkout main
67
67
```
68
-
1. To configure the service, copy or rename the `public/config.example` file to `public/config.json`.
69
-
1. Then edit the `public/config.json` file to point to your service. Update the values in the file as follows:
70
-
1. Replace `<service name>` and `<location>` with the name of your API center and the location where it's deployed
68
+
1. To configure the service, copy or rename the `config.example.json` file to `config.json`.
69
+
1. Then edit the `config.json` file to point to your service. Update the values in the file as follows:
70
+
1. Replace `<service name>` and `<region>` with the name of your API center and the location where it's deployed
71
71
1. Replace `<client ID>` and `<tenant ID>` with the **Application (client) ID** and **Directory (tenant) ID** of the app registration you created in the previous section.
72
72
1. Update the value of `title` to a name that you want to appear in the top bar of the portal.
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/app-service-configure-premium-v4-tier.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
@@ -103,9 +103,9 @@ Premium v4 is available in the following regions:
103
103
- Canada Central<sup>*</sup>
104
104
- Central India
105
105
- Central US
106
-
- East Asia
106
+
- East Asia<sup>*</sup>
107
107
- East US
108
-
- East US 2<sup>*</sup>
108
+
- East US 2
109
109
- France Central<sup>*</sup>
110
110
- Germany West Central<sup>*</sup>
111
111
- Indonesia Central<sup>*</sup>
@@ -141,7 +141,7 @@ If your app runs where Premium v4 isn't available (either the deployment or the
141
141
142
142
When creating the plan, select the desired Premium v4 tier. This ensures the plan is in a deployment unit supporting Premium V4. Then, redeploy your application code to the new app. Even if you scale the new plan down to save costs, you can always scale back up to Premium v4 because the deployment unit supports it.
143
143
144
-
- Use the **Development tools** > **Clone app** page to create an App Service plan with Premium v4 in your desired region, specifying the app settings and configuration to clone.
144
+
- Use the **Development tools** > **Clone app** page to create an App Service plan with Premium v4 in your desired region, specifying the app settings and configuration to clone. Refer to the [current restrictions](app-service-web-app-cloning.md#current-restrictions) for app cloning.
145
145
146
146
:::image type="content" source="media/app-service-configure-premium-tier/clone-app.png" alt-text="Screenshot showing how to clone your app.":::
Copy file name to clipboardExpand all lines: articles/app-service/configure-managed-instance.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Configure Managed Instance on Azure App Service (Preview)"
3
3
description: Learn how to configure and deploy a Managed Instance on Azure App Service using Azure CLI and ARM templates. This guide covers general settings, storage mounts, registry keys, and Bastion/RDP access.
4
4
author: msangapu-msft
5
5
ms.author: msangapu
6
-
ms.date: 11/18/2025
6
+
ms.date: 01/15/2026
7
7
ms.service: azure-app-service
8
8
ms.topic: how-to
9
9
keywords:
@@ -220,6 +220,7 @@ To configure Bastion:
220
220
-[My Managed Instance on App Service plan has multiple web applications can I restart a single web application?](#my-managed-instance-on-app-service-plan-has-multiple-web-applications-can-i-restart-a-single-web-application)
221
221
-[Can I assign Managed Identity to my web application within the Managed Instance on App Service plan?](#can-i-assign-managed-identity-to-my-web-application-within-the-managed-instance-on-app-service-plan)
222
222
-[Is there a limitation on number of adapters that I can create for Managed Instance on App Service plan?](#is-there-a-limitation-on-number-of-adapters-that-i-can-create-for-managed-instance-on-app-service-plan)
223
+
-[Which regions have support for Managed Instance on App Service?](#which-regions-have-support-for-managed-instance-on-app-service)
223
224
224
225
### What operating system (os) is running on Managed Instance on Azure App Service?
225
226
@@ -303,6 +304,14 @@ Yes, you can assign a _different_ Managed identity to a web application within t
303
304
304
305
No, there's no limit on the number of storage or registry adapters. You can only create a single configuration (install) script adapter for Managed Instance on App Service plan. The increasing the number of adapters could affect provisioning time for Managed Instance.
305
306
307
+
### Which regions have support for Managed Instance on App Service?
308
+
309
+
Currently support for Managed Instance on App Service is limited to East US, West Central US, East Asia, North Europe, and Australia East. More regions will be added to the preview over time. To get an updated list of regions, you can use the following CLI command (You must be using Azure CLI version 2.82.0 or higher).
310
+
311
+
```azurecli
312
+
az appservice list-locations --managed-instance-enabled --sku <Pv4 or PmV4 sku your require, for example P1v4>
313
+
```
314
+
306
315
## Related content
307
316
308
317
-[Overview of Managed Instance on Azure App Service](overview-managed-instance.md)
0 commit comments