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

Author: gitName

.openpublishing.redirection.json

@@ -1,5 +1,15 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/storsimple/index.yml",
+      "redirect_url": "/previous-versions/azure/storsimple/index",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/storsimple/storsimple-overview.md",
+      "redirect_url": "/previous-versions/azure/storsimple/storsimple-overview",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/expressroute/expressroute-troubleshooting-arp-classic.md",
       "redirect_url": "/previous-versions/azure/expressroute/expressroute-troubleshooting-arp-classic",
@@ -6998,11 +7008,15 @@
       "source_path": "articles/reliability/migrate-sql-database.md",
       "redirect_url": "/azure/azure-sql/database/enable-zone-redundancy",
       "redirect_document_id": false
-    },
+    },    
     {
       "source_path": "articles/reliability/migrate-app-gateway-v2.md",
       "redirect_url": "/azure/reliability/reliability-application-gateway-v2",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/reliability/migrate-storage.md",
+      "redirect_url": "/azure/storage/common/redundancy-migration",
     }
   ]
 }

articles/active-directory-b2c/stringcollection-transformations.md

@@ -28,7 +28,7 @@ Adds a string claim to a new unique values stringCollection claim. Check out the
 
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
-| InputClaim | Element | string | The ClaimType to be added to the output claim. |
+| InputClaim | item | string | The ClaimType to be added to the output claim. |
 | InputClaim | collection | stringCollection | The string collection to be added to the output claim. If the collection contains items, the claims transformation copies the items, and adds the item to the end of the output collection claim. |
 | OutputClaim | collection | stringCollection | The ClaimType that is produced after this claims transformation has been invoked, with the value specified in the input claim. |
 
@@ -63,7 +63,7 @@ Adds a string parameter to a new unique values stringCollection claim. Check out
 | Element | TransformationClaimType | Data Type | Notes |
 | ---- | ----------------------- | --------- | ----- |
 | InputClaim | collection | stringCollection | The string collection to be added to the output claim. If the collection contains items, the claims transformation copies the items, and adds the item to the end of the output collection claim. |
-| InputParameter | Element | string | The value to be added to the output claim. |
+| InputParameter | item | string | The value to be added to the output claim. |
 | OutputClaim | collection | stringCollection | The ClaimType that is produced after this claims transformation has been invoked, with the value specified in the input parameter. |
 
 ### Example of AddParameterToStringCollection

articles/api-center/TOC.yml

@@ -74,7 +74,9 @@
   items:
   - name: Enable API Center portal
     href: set-up-api-center-portal.md
-  - name: Enable API Center portal - VS Code extension
+  - name: Customize API Center portal
+    href: customize-api-center-portal.md
+  - name: Enable API Center portal view - VS Code extension
     href: enable-api-center-portal-vs-code-extension.md
   - name: Self-host Azure API Center portal
     href: self-host-api-center-portal.md

articles/api-center/authorize-api-access.md

@@ -174,7 +174,7 @@ You can manage access by specific users or groups in your organization to an API
 You can use the API Center portal to test an API that you configured for authentication and user access. 
 
 > [!TIP]
-> In addition to enabling specific users to test specific APIs in the API Center portal, you can configure [visibility settings](set-up-api-center-portal.md#api-visibility) for APIs. Visibility settings in the portal control the APIs that appear for all signed-in users.
+> In addition to enabling specific users to test specific APIs in the API Center portal, you can configure [visibility settings](customize-api-center-portal.md#api-visibility) for APIs. Visibility settings in the portal control the APIs that appear for all signed-in users.
 
 1. In the [portal](https://azure.microsoft.com), navigate to your API center.
 1. In the left menu, under **API Center Portal**, select **Portal settings**.

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

@@ -0,0 +1,89 @@
+---
+title: Customize the API Center Portal
+description: Learn about settings you can customize in your Azure API Center portal.
+author: dlepow
+ms.service: azure-api-center
+ms.topic: how-to
+ms.date: 08/07/2025
+ms.update-cycle: 180-days
+ms.author: danlep 
+ms.custom: 
+ms.collection: ce-skilling-ai-copilot
+# Customer intent: As an API program manager, I want to customize the Azure-managed portal for developers and other API stakeholders in my organization.
+---
+
+# Customize your API Center portal
+
+This article explains settings that you can customize in the API Center portal (preview). The API Center portal is an Azure-managed website that developers and other stakeholders in your organization use to discover the APIs in your [API center](overview.md). 
+
+To set up the API Center portal for initial use and sign-in, see [Set up the API Center portal](set-up-api-center-portal.md).
+
+> [!NOTE]
+> The API Center portal is currently in preview.
+
+## Portal settings page
+
+Configure API Center portal settings in the Azure portal. To access the settings page:
+
+1. Navigate to your API center in the Azure portal.
+1. Under **API Center portal**, select **Settings**. 
+1. Click on the tabs to view and customize the settings.
+1. Select **Save + publish** to apply your changes.
+
+:::image type="content" source="media/customize-api-center-portal/configure-portal-settings.png" alt-text="Screenshot of API Center portal settings in the Azure portal." lightbox="media/customize-api-center-portal/configure-portal-settings.png":::
+
+> [!IMPORTANT]
+> Select **Save + publish** each time that you make changes to the settings. Until you publish, your changes aren't visible in the API Center portal.
+
+## Site profile
+
+On the **Site profile** tab, optionally provide a custom name that appears in the top bar of the published portal.
+
+:::image type="content" source="media/customize-api-center-portal/custom-name.png" alt-text="Screenshot of custom name in API Center portal.":::
+
+## API visibility
+
+On the **API visibility** tab, control which APIs are discoverable (visible) to API Center portal users. Visibility settings apply to all users of the API Center portal.
+
+The API Center portal uses the [Azure API Center data plane API](/rest/api/dataplane/apicenter/operation-groups) to retrieve and display APIs in your API center, and by default shows all APIs for signed-in users with Azure RBAC permissions. 
+
+To make only specific APIs visible, add filter conditions for APIs based on built-in properties. For instance, choose to display APIs only of certain types (like REST or GraphQL) or based on certain specification formats (such as OpenAPI).
+
+:::image type="content" source="media/customize-api-center-portal/add-visibility-condition.png" alt-text="Screenshot of adding API visibility conditions in the portal.":::
+
+## Anonymous access
+
+On the **API visibility** tab, optionally enable anonymous read access to the [Azure API Center data plane API](/rest/api/dataplane/apicenter/operation-groups), which allows unauthenticated users to discover the API inventory by direct API calls. For example, enable this setting to make APIs discoverable to unauthenticated users when you [self-host](self-host-api-center-portal.md) the API Center portal.
+
+> [!CAUTION]
+> When enabling anonymous access, take care not to expose sensitive information in API definitions or settings.
+
+## Semantic search
+
+If enabled on the **Semantic search** tab, the API Center portal supplements basic name-based API search with AI-assisted *semantic search* built on API names, descriptions, and optionally custom metadata. Semantic search is available in the **Standard** plan only.
+
+Users can search for APIs using natural language queries, making it easier to find APIs based on their intent. For example, if a developer searches for "I need an API for inventory management," the portal can suggest relevant APIs, even if the API names or descriptions don't include those exact words.
+
+> [!TIP]
+> When using the **Free** plan of Azure API Center, you can [upgrade easily](frequently-asked-questions.yml#how-do-i-upgrade-my-api-center-from-the-free-plan-to-the-standard-plan) to the **Standard** plan to enable full service features including semantic search in the API Center portal.
+
+To use AI-assisted search when signed in to the API Center portal, click in the search box, select **Search with AI**, and enter a query.
+
+:::image type="content" source="media/customize-api-center-portal/semantic-search.png" alt-text="Screenshot of semantic search results in API Center portal.":::
+
+## Custom metadata
+
+On the **Metadata** tab, optionally select [custom metadata](metadata.md) properties that you want to expose in API details and semantic search.
+
+## Enable access to test console for APIs
+
+You can configure user settings to granularly authorize access to APIs and their specific versions in your API center. For example, configure certain API versions to use API keys for authentication, and create an access policy that permits only specific users to authenticate using those keys. 
+
+Access policies also apply to the "Try this API" capability for APIs in the API Center portal, ensuring that only portal users with the appropriate access policy can use the test console for those API versions. [Learn more about authorizing access to APIs](authorize-api-access.md)
+
+## Related content
+
+* [Set up the API Center portal](set-up-api-center-portal.md)
+* [Enable and view Azure API Center portal in Visual Studio Code](enable-api-center-portal-vs-code-extension.md)
+* [Self-host the API Center portal](self-host-api-center-portal.md)
+

articles/api-center/enable-api-analysis-linting.md

@@ -119,7 +119,7 @@ To deploy the Azure Functions app that runs the linting function on API definiti
 1. Clone the [GitHub repository](https://github.com/Azure/APICenter-Analyzer/) and open it in Visual Studio Code.
 1. In the `resources/rulesets` folder, you can find an `oas.yaml` file. This file reflects your current API style guide and can be modified based on your organizational needs and requirements.
 1. Optionally, run the function app locally to test it. For details, see the [README](https://github.com/Azure/APICenter-Analyzer/tree/preview#-configure--run-your-function-locally) file in the repository.
-1. Deploy the function app to Azure. For steps, see [Quickstart: Create a function in Azure with TypeScript using Visual Studio Code](../azure-functions/create-first-function-vs-code-typescript.md#sign-in-to-azure).
+1. Deploy the function app to Azure. For steps, see [Quickstart: Create a function in Azure with TypeScript using Visual Studio Code](../azure-functions/how-to-create-function-vs-code.md?pivot=programming-language-typescript#sign-in-to-azure).
 
     > [!NOTE]
     > Deploying the function app might take a few minutes.

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

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 05/28/2025
+ms.date: 08/08/2025
 ms.author: danlep
 ms.custom: Include file
 ---
@@ -22,18 +22,20 @@ To set up the app registration automatically, follow these steps:
 1. In the [Azure portal](https://portal.azure.com), navigate to your API center.
 1. In the left-hand menu, select **API Center portal** > **Settings**.
 1. On the **Identity provider** tab, select **Start set up**.
-1. Select **Save + publish**.
+1. On the **Quick setup** tab, select **Save + publish**.
+
+If you need to access the app registration later, you can find it in the portal under **App registrations**. The application is named with the following format: **\<api-center-name>-apic-aad**. 
 
 #### Set up the app registration manually
 
 If you want to create the app registration manually, follow these steps:
 
-1. In the [Azure portal](https://portal.azure.com), navigate to **Microsoft Entra ID** > **App registrations**.
+1. In the [Azure portal](https://portal.azure.com), navigate to **Microsoft Entra ID** > **Manage** > **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. Under **Supported account types**, select **Accounts in this organizational directory only (\<Directory name> - 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-apicenter.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-apicenter.ms`.
     1. Select **Register**.

articles/api-center/includes/api-center-portal-user-sign-in.md

@@ -6,15 +6,15 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 03/04/2025
+ms.date: 08/05/2025
 ms.author: danlep
 ms.custom: Include file
 ---
 
-To enable sign-in, assign the **Azure API Center Data Reader** role to users or groups in your organization, scoped to your API center.
+To enable sign-in to the API Center portal to access APIs, assign the **Azure API Center Data Reader** role to users or groups in your organization, scoped to your API center.
 
 > [!IMPORTANT]
-> By default, you and other administrators of the API center don't have access to APIs in the API Center portal. Be sure to assign the **Azure API Center Data Reader** role to yourself and other administrators.  
+> By default, you and other administrators of the API center must sign-in to access APIs in the API Center portal. Be sure to assign the **Azure API Center Data Reader** role to yourself and other administrators.  
 
 For detailed prerequisites and steps to assign a role to users and groups, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml). Brief steps follow: