review comments

gitName · gitName · commit 36efd3a0e0f8 · 2025-03-05T16:19:32.000-08:00
diff --git a/articles/api-center/includes/api-center-portal-app-registration.md b/articles/api-center/includes/api-center-portal-app-registration.md
@@ -23,10 +23,6 @@ First configure an app registration in your Microsoft Entra ID tenant. The app r
     * Under **Supported account types**, select **Accounts in this organizational directory (Single tenant)**. 
     * 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`.
-
-        > [!TIP]
-        > If you are self-hosting the portal and what to test it locally before deploying to Azure, you can set the URI to `https://localhost:5173`. 
-
     * Select **Register**.
 1. On the **Overview** page, copy the **Application (client) ID**. You set this value when you publish the portal.
       
diff --git a/articles/api-center/includes/api-center-portal-compare-apim-dev-portal.md b/articles/api-center/includes/api-center-portal-compare-apim-dev-portal.md
@@ -13,30 +13,24 @@ ms.custom: Include file
 
 ## Which portal to use: API Management's or API Center's?
 
-The [Azure API Management](../../api-management/api-management-key-concepts.md) service and the [Azure API Center](../overview.md) service both offer portals for developers and other API users to discover and consume an organization's APIs:
+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:
 
-* In API Management, the *developer portal* is where developers and API consumers can discover the APIs managed APIs, learn how to use them, request access, and try them out. 
+* 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* enables users to discover and filter the API inventory.
 
-* In API Center, the *API Center portal* is where developers and API consumers can discover and filter the API inventory and review API definitions and documentation.  
+While the two portals share some features, they also have distinct differences. The following table compares key capabilities to help determine which portal to use. Some organizations may prefer one portal, while others may need both.
 
-The portals have some common features, but also some distinct differences. Especially in organizations that adopt both services, the question arises: *Which portal should I use?* The following table compares key capabilities of the two portals. For some organizations, one portal may be preferable; for some, both may be needed.
-
-| Feature | API Management portal | API Center portal |
+| Feature | API Management developer portal | API Center portal |
 | --- | --- | --- |
-| Browse APIs in API Management instance | Yes | Yes<sup>1</sup> |
-| Browse APIs in entire inventory | No | Yes<sup>1</sup> |
+| Audience| External and internal developers | Internal developers |
+| API inventory | API Management instance only | All APIs |
 | Search and filter APIs | No | Yes |
 | View API details and definitions | Yes | Yes |
 | View API documentation | Yes | Yes |
-| Configure basic branding | Yes | Yes |
+| Customize with branding | Yes | Name only |
 | Add custom widgets | Yes | No |
-| Self-host | Yes | Yes |
 | Customize with WordPress | Yes | No |
 | Integrate with Microsoft Entra | Yes | Yes |
-| Access publicly | Yes | No |
 | Test APIs in test console | Yes | No |
 | Subscribe to APIs | Yes | No |
-| View API usage analytics | Yes | No |
-
-<sup>2</sup> Depends on import or integration of APIs from API sources. 
-
+| View API usage analytics | Yes | No |
diff --git a/articles/api-center/media/set-up-api-center-portal/add-visibility-condition.png b/articles/api-center/media/set-up-api-center-portal/add-visibility-condition.png
diff --git a/articles/api-center/self-host-api-center-portal.md b/articles/api-center/self-host-api-center-portal.md
@@ -17,7 +17,7 @@ This article shows how to self-host the *API Center portal*, a website that deve
 :::image type="content" source="media/self-host-api-center-portal/api-center-portal-signed-in.png" alt-text="Screenshot of the API Center portal after user sign-in.":::
 
 > [!TIP]
-> You can also set up an Azure-managed version of the API Center portal. For more information, see [Set up the API Center portal](set-up-api-center-portal.md).
+> New! You can now set up an Azure-managed version of the API Center portal. For more information, see [Set up the API Center portal](set-up-api-center-portal.md).
 
 ## About self-hosting the portal
 
@@ -30,7 +30,7 @@ The API Center portal reference implementation provides:
 * Flexibility to host on different infrastructures, including deployment to services such as Azure Static Web Apps.  
 
 > [!NOTE]
-> When you self-host the API Center portal, you become its maintainer and you're responsible for its upgrades.
+> When you self-host the API Center portal, you become its maintainer and you're responsible for its upgrades. Azure support is limited.
 
 [!INCLUDE [api-center-portal-prerequisites](includes/api-center-portal-prerequisites.md)]
 
@@ -41,6 +41,9 @@ The API Center portal reference implementation provides:
 
 [!INCLUDE [api-center-portal-app-registration](includes/api-center-portal-app-registration.md)]
 
+> [!NOTE]
+> When you're self-hosting the portal and want to test it locally before deploying to Azure, set the redirect URI in the app registration to `https://localhost:5173`. 
+
 ## Configure local environment
 
 Follow these steps to build and test the API Center portal locally.
diff --git a/articles/api-center/set-up-api-center-portal.md b/articles/api-center/set-up-api-center-portal.md
@@ -12,12 +12,12 @@ ms.custom:
 
 # Set up your API Center portal
 
-This article shows you how to set up the *API Center portal*, an Azure-managed website that developers and other stakeholders in your organization can use to discover the APIs in your [API center](overview.md). Signed-in users can browse and filter APIs and view API details such as API definitions and documentation. User access to API information is based on Microsoft Entra ID and Azure role-based access control.
+This article shows you how to set up the *API Center portal* (preview), an Azure-managed website that developers and other stakeholders in your organization can use to discover the APIs in your [API center](overview.md). Signed-in users can browse and filter APIs and view API details such as API definitions and documentation. User access to API information is based on Microsoft Entra ID and Azure role-based access control.
 
 :::image type="content" source="media/self-host-api-center-portal/api-center-portal-signed-in.png" alt-text="Screenshot of the API Center portal after user sign-in.":::
 
-> [!TIP]
-> If you want capabilities to customize the portal, you can self-host the API Center portal. For more information, see [Self-host the API Center portal](self-host-api-center-portal.md).
+> [!NOTE]
+> The API Center portal is currently in preview.
 
 [!INCLUDE [api-center-portal-prerequisites](includes/api-center-portal-prerequisites.md)]
 
@@ -27,9 +27,6 @@ This article shows you how to set up the *API Center portal*, an Azure-managed w
 
 After you create the API Center portal app registration, you need to configure and publish the API center portal. Complete the following steps in the Azure portal. 
 
-> [!IMPORTANT]
-> After publishing the API center portal, you can't unpublish it. If you need to stop using the portal, you can delete the app registration in Microsoft Entra ID.
-
 1. In the [Azure portal](https://portal.azure.com), navigate to your API center.
 1. In the left menu, under **API Center portal**, select **Portal settings**.
     :::image type="content" source="media/set-up-api-center-portal/configure-portal-settings.png" alt-text="Screenshot of API Center portal settings in the Azure portal.":::
@@ -38,9 +35,20 @@ After you create the API Center portal app registration, you need to configure a
     1. Confirm that the **Redirect URI** is the value you configured in the app registration. 
     1. Select **Save + publish**.
 1. On the **Site profile** tab, enter a website name that you want to appear in the top bar of the API Center portal. Select **Save + publish**.
-1. On the **API visibility** tab, optionally configure filters for the APIs you want to make visible in the portal. Select **Save + publish**.
+1. On the **API visibility** tab, optionally add filters for APIs that you want to make discoverable in the portal. Select **Save + publish**. [Learn more about API visibility](#api-visibility).
+
+You can now access the API Center portal:
+* On the **Portal settings** page, select **View API Center portal** to open the portal in a new tab. 
+* Or, enter the following URL in your browser, replacing `<service-name>` and `<location>` with the name of your API center and the location where it's deployed:<br/><br/>
+    `https://<service-name>.portal.<location>.azure-api-center.ms`
+
+### API visibility
 
-You can now access the API Center portal. On the **Portal settings** page, select **View API Center portal** to open the portal in a new tab.
+API visibility settings control which APIs are discoverable (visible) to API Center portal users. The API Center portal uses the data plane API to retrieve and display APIs, and by default retrieves all APIs in your API center.
+
+To make only specific APIs visible, go to the **API visibility** tab in the API Center portal settings. Here, add filter conditions for APIs based on built-in or custom API [metadata](metadata.md) properties. For instance, you can choose to display APIs only of certain types (like REST or GraphQL) or based on certain specification formats (such as OpenAPI). Additionally, you can select values of custom metadata properties that categorize your APIs.
+
+:::image type="content" source="media/set-up-api-center-portal/add-visibility-condition.png" alt-text="Screeshot of adding API visibility conditions in the portal.":::
 
 [!INCLUDE [api-center-portal-user-sign-in](includes/api-center-portal-user-sign-in.md)]
 
@@ -49,5 +57,4 @@ You can now access the API Center portal. On the **Portal settings** page, selec
 
 ## Related content
 
-* [Self-host the API Center portal](self-host-api-center-portal.md)
-
+* [Enable and view Azure API Center platform API catalog](design-api-github-copilot-azure.md)
