Merge branch 'main' of https://github.com/microsoftdocs/azure-docs-pr into dtl3

Author: v-thepet

.openpublishing.redirection.json

@@ -5450,6 +5450,11 @@
       "redirect_url": "/azure/virtual-wan/virtual-wan-about",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/virtual-wan/azure-vpn-client-optional-configurations-windows.md",
+      "redirect_url": "/azure/virtual-wan/azure-vpn-client-optional-configurations",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/virtual-wan/openvpn-azure-ad-client.md",
       "redirect_url": "/azure/virtual-wan/point-to-site-entra-vpn-client-windows",

articles/active-directory-b2c/openid-connect-technical-profile.md

@@ -89,7 +89,7 @@ The technical profile also returns claims that aren't returned by the identity p
 | HttpBinding | No | The expected HTTP binding to the access token and claims token endpoints. Possible values: `GET` or `POST`.  |
 | ValidTokenIssuerPrefixes | No | A key that can be used to sign in to each of the tenants when using a multi-tenant identity provider such as Microsoft Entra ID. |
 | UsePolicyInRedirectUri | No | Indicates whether to use a policy when constructing the redirect URI. When you configure your application in the identity provider, you need to specify the redirect URI. The redirect URI points to Azure AD B2C, `https://{your-tenant-name}.b2clogin.com/{your-tenant-name}.onmicrosoft.com/oauth2/authresp`.  If you specify `true`, you need to add a redirect URI for each policy you use. For example: `https://{your-tenant-name}.b2clogin.com/{your-tenant-name}.onmicrosoft.com/{policy-name}/oauth2/authresp`. |
-| MarkAsFailureOnStatusCode5xx | No | Indicates whether a request to an external service should be marked as a failure if the Http status code is in the 5xx range. The default is `false`. |
+| MarkAsFailureOnStatusCode5xx | No | Indicates whether a request to an external service should be marked as a failure if the HTTP status code is in the 5xx range. The default is `false`. |
 | DiscoverMetadataByTokenIssuer | No | Indicates whether the OIDC metadata should be discovered by using the issuer in the JWT.If you need to build the metadata endpoint URL based on Issuer, set this to `true`.|
 | IncludeClaimResolvingInClaimsHandling  | No | For input and output claims, specifies whether [claims resolution](claim-resolver-overview.md) is included in the technical profile. Possible values: `true`, or `false` (default). If you want to use a claims resolver in the technical profile, set this to `true`. |
 |token_endpoint_auth_method| No | Specifies how Azure AD B2C sends the authentication header to the token endpoint. Possible values: `client_secret_post` (default), and `client_secret_basic`, `private_key_jwt`. For more information, see [OpenID Connect client authentication section](https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication). |

articles/api-center/TOC.yml

@@ -68,12 +68,14 @@
         href: set-up-notification-workflow.md
 - name: API discovery and consumption
   items:
+      - name: Enable API Center portal
+        href: set-up-api-center-portal.md
+      - name: Self-host Azure API Center portal
+        href: self-host-api-center-portal.md
       - name: Discover and consume APIs - VS Code extension
         href: discover-apis-vscode-extension.md
       - name: Enable platform API catalog - VS Code extension
         href: enable-platform-api-catalog-vscode-extension.md
-      - name: Self-host Azure API Center portal
-        href: enable-api-center-portal.md
       - name: Check API calls use minimal permissions with Dev Proxy
         href: check-minimal-api-permissions-dev-proxy.md
 - name: API center management and operations

articles/api-center/enable-api-center-portal.md

@@ -0,0 +1,36 @@
+---
+title: Include file
+description: Include file
+services: api-center
+author: dlepow
+
+ms.service: azure-api-center
+ms.topic: include
+ms.date: 03/04/2025
+ms.author: danlep
+ms.custom: Include file
+---
+
+## Create Microsoft Entra app registration
+
+First configure an app registration in your Microsoft Entra ID tenant. The app registration enables the API Center portal to access data from your API center on behalf of a signed-in user.
+
+1. In the [Azure portal](https://portal.azure.com), navigate to **Microsoft Entra ID** > **App registrations**.
+1. Select **+ New registration**. 
+1. On the **Register an application** page, set the values as follows:
+    
+    1. Set **Name** to a meaningful name such as *api-center-portal*
+    1. Under **Supported account types**, select **Accounts in this organizational directory (Single tenant)**. 
+    1. In **Redirect URI**, select **Single-page application (SPA)** and set the URI. 
+        Enter the URI of your API Center portal deployment, in the following form: `https://<service-name>.portal.<location>.azure-api-center.ms`. Replace `<service name>` and `<location>` with the name of your API center and the location where it's deployed, Example: `https://myapicenter.portal.eastus.azure-api-center.ms`.
+    1. Select **Register**.
+1. On the **Overview** page, copy the **Application (client) ID**. You set this value when you publish the portal.
+      
+1. On the **API permissions** page, select **+ Add a permission**. 
+    1. On the **Request API permissions** page, select the **APIs my organization uses** tab. Search for and select **Azure API Center**. You can also search for and select application ID `c3ca1a77-7a87-4dba-b8f8-eea115ae4573`. 
+    1. On the **Request permissions** page, select **user_impersonation**.
+    1. Select **Add permissions**. 
+
+    The Azure API Center permissions appear under **Configured permissions**.
+
+    :::image type="content" source="media/api-center-portal-app-registration/configure-app-permissions.png" alt-text="Screenshot of required permissions in Microsoft Entra ID app registration in the portal." lightbox="media/api-center-portal-app-registration/configure-app-permissions.png":::

articles/api-center/includes/api-center-portal-app-registration.md

@@ -0,0 +1,36 @@
+---
+title: Include file
+description: Include file
+services: api-center
+author: dlepow
+
+ms.service: azure-api-center
+ms.topic: include
+ms.date: 03/05/2025
+ms.author: danlep
+ms.custom: Include file
+---
+
+## API Management and API Center portals
+
+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:
+
+* The *API Management developer portal* allows users to find managed APIs, learn how to use them, request access, and test them.
+* The *API Center portal* (preview) is a multi-gateway portal where  users can discover and filter the organization's complete API inventory.
+
+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.
+
+| Feature | API Management developer portal | API Center portal (preview) |
+| --- | --- | --- |
+| Search and filter API inventory | API Management instance only | All APIs<sup>1</sup> |
+| View API details and definitions | ✔️ | ✔️ |
+| View API documentation | ✔️ | ✔️ |
+| Customize with branding | ✔️ | Name only |
+| Integrate with Microsoft Entra ID | ✔️ | ✔️ |
+| Add custom widgets | ✔️ | ❌ |
+| Customize with WordPress | ✔️ | ❌ |
+| Test APIs in test console | ✔️ | ❌ |
+| Subscribe to APIs | ✔️ | ❌ |
+| View API usage analytics | ✔️ | ❌ |
+
+<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.

articles/api-center/includes/api-center-portal-compare-apim-dev-portal.md

@@ -0,0 +1,18 @@
+---
+title: Include file
+description: Include file
+services: api-center
+author: dlepow
+
+ms.service: azure-api-center
+ms.topic: include
+ms.date: 03/04/2025
+ms.author: danlep
+ms.custom: Include file
+---
+
+## Prerequisites
+
+* An API center in your Azure subscription. If you haven't created one already, see [Quickstart: Create your API center](../set-up-api-center.md).
+
+* Permissions to create an app registration in a Microsoft Entra tenant associated with your Azure subscription, and permissions to grant access to data in your API center.