Merge branch 'main' into reliability-spring-apps-remove

Author: anaharris-ms

.openpublishing.redirection.json

@@ -7923,6 +7923,16 @@
       "source_path": "articles/reliability/reliability-spring-apps.md",
       "redirect_url": "/azure/reliability/overview-reliability-guidance",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/iot-hub-device-update/device-update-simulator.md",
+      "redirect_url": "/azure/iot-hub-device-update/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/iot-hub-device-update/device-update-azure-real-time-operating-system.md",
+      "redirect_url": "/azure/iot-hub-device-update/",
+      "redirect_document_id": false
     }
 
 

articles/active-directory-b2c/azure-monitor.md

@@ -69,7 +69,7 @@ In summary, you'll use Azure Lighthouse to allow a user or group in your Azure A
 
 - An Azure AD B2C account with [Global Administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator) role on the Azure AD B2C tenant.
 
--  A Microsoft Entra account with the [Owner](../role-based-access-control/built-in-roles.md#owner) role in the Microsoft Entra subscription. See how to [Assign a user as an administrator of an Azure subscription](../role-based-access-control/role-assignments-portal-subscription-admin.yml). 
+-  A Microsoft Entra account with the [Owner](../role-based-access-control/built-in-roles.md#owner) role in the Microsoft Entra subscription. See how to [Assign a user as an administrator of an Azure subscription](/azure/role-based-access-control/role-assignments-portal-subscription-admin). 
 
 ## 1. Create or choose resource group
 

articles/api-center/import-api-management-apis.md

@@ -199,5 +199,5 @@ After importing APIs from API Management, you can view and manage the imported A
 * [Azure CLI reference for Azure API Center](/cli/azure/apic)
 * [Azure CLI reference for API Management](/cli/azure/apim)
 * [Use the Azure CLI to manage your API inventory](manage-apis-azure-cli.md)
-* [Assign Azure roles to a managed identity](../role-based-access-control/role-assignments-portal-managed-identity.yml)
+* [Assign Azure roles to a managed identity](/azure/role-based-access-control/role-assignments-portal-managed-identity)
 * [Azure API Management documentation](../api-management/index.yml)

articles/api-center/includes/configure-managed-identity-apim-reader.md

@@ -11,7 +11,7 @@ ms.author: danlep
 ms.custom: Include file
 ---
 
-To allow import of APIs, assign your API center's managed identity the **API Management Service Reader** role in your API Management instance. You can use the [portal](../../role-based-access-control/role-assignments-portal-managed-identity.yml) or the Azure CLI.
+To allow import of APIs, assign your API center's managed identity the **API Management Service Reader** role in your API Management instance. You can use the [portal](/azure/role-based-access-control/role-assignments-portal-managed-identity) or the Azure CLI.
 
 #### [Portal](#tab/portal)
 

articles/api-center/includes/configure-managed-identity-kv-secret-user.md

@@ -11,7 +11,7 @@ ms.author: danlep
 ms.custom: Include file
 ---
 
-To allow import of APIs, assign your API center's managed identity the **Key Vault Secrets User** role in your Azure key vault. You can use the [portal](../../role-based-access-control/role-assignments-portal-managed-identity.yml) or the Azure CLI.
+To allow import of APIs, assign your API center's managed identity the **Key Vault Secrets User** role in your Azure key vault. You can use the [portal](/azure/role-based-access-control/role-assignments-portal-managed-identity) or the Azure CLI.
 
 #### [Portal](#tab/portal)
 

articles/api-management/genai-gateway-capabilities.md

@@ -233,7 +233,7 @@ More information:
 
 * [AI gateway reference architecture using API Management](/ai/playbook/technology-guidance/generative-ai/dev-starters/genai-gateway/reference-architectures/apim-based)
 * [AI hub gateway landing zone accelerator](https://github.com/Azure-Samples/ai-hub-gateway-solution-accelerator)
-* [Designing and implementing a gateway solution with Azure OpenAI resources](/ai/playbook/technology-guidance/generative-ai/dev-starters/gemonitoring API Management with Azurenai-gateway/)
+* [Designing and implementing a gateway solution with Azure OpenAI resources](/ai/playbook/technology-guidance/generative-ai/dev-starters/genai-gateway/)
 * [Use a gateway in front of multiple Azure OpenAI deployments](/azure/architecture/ai-ml/guide/azure-openai-gateway-multi-backend)
 
 ## Related content

articles/api-management/get-started-create-service-instance-cli.md

@@ -1,11 +1,11 @@
 ---
-title: Quickstart - Create Azure API Management instance - CLI
+title: Quickstart - Create Azure API Management Instance - CLI
 description: Use this quickstart to create a new Azure API Management instance by using the Azure CLI.
 author: dlepow
 ms.service: azure-api-management
 ms.topic: quickstart
 ms.custom: mode-api, devx-track-azurecli, devdivchpfy22
-ms.date: 12/11/2023
+ms.date: 10/14/2025
 ms.author: danlep 
 ms.devlang: azurecli
 ---
@@ -38,7 +38,7 @@ az group create --name myResourceGroup --location centralus
 
 Now that you have a resource group, you can create an API Management instance. Create one by using the [az apim create](/cli/azure/apim#az-apim-create) command and provide a service name and publisher details. The service name must be unique within Azure.
 
-In the following example, *myapim* is used for the service name. Update the name to a unique value. Also update the name of the API publisher's organization and the email address to receive notifications.
+In the following example, *myapim* is used for the service name. Update the name to a unique value. Also update the name of the API publisher's organization, and to receive notifications update the email address.
 
 ```azurecli-interactive
 az apim create --name myapim --resource-group myResourceGroup \

articles/api-management/powershell-create-service-instance.md

@@ -1,12 +1,12 @@
 ---
-title: Quickstart - Create API Management instance - PowerShell
+title: Quickstart - Create API Management Instance - PowerShell
 description: Use this quickstart to create a new Azure API Management instance by using Azure PowerShell cmdlets.
 services: api-management
 author: dlepow
 ms.service: azure-api-management
 ms.topic: quickstart
 ms.custom: mvc, devx-track-azurepowershell, mode-api, devdivchpfy22
-ms.date: 12/12/2023
+ms.date: 10/14/2025
 ms.author: danlep
 ---
 
@@ -44,7 +44,7 @@ In the following example, *myapim* is used for the service name. Update the name
 By default, the command creates the instance in the Developer tier, an economical option to evaluate Azure API Management. This tier isn't for production use. For more information about the API Management tiers, see [Feature-based comparison of the Azure API Management tiers](api-management-features.md).
 
 > [!TIP]
-> This is a long-running action. It can take between 30 and 40 minutes to create and activate an API Management service in this tier.
+> This command can take between 30 and 40 minutes to create and activate an API Management service in this tier.
 
 ```azurepowershell-interactive
 New-AzApiManagement -Name "myapim" -ResourceGroupName "myResourceGroup" `
@@ -67,7 +67,7 @@ Name                                  : myapim
 Location                              : West US
 Sku                                   : Developer
 Capacity                              : 1
-CreatedTimeUtc                        : 9/9/2022 9:07:43 PM
+CreatedTimeUtc                        : 10/13/2025 9:54:18 PM
 ProvisioningState                     : Succeeded
 RuntimeUrl                            : https://myapim.azure-api.net
 RuntimeRegionalUrl                    : https://myapi-westus-01.regional.azure-api.net

articles/api-management/vscode-create-service-instance.md

@@ -1,11 +1,11 @@
 ---
-title: Quickstart - Create Azure API Management instance - VS Code
+title: Quickstart - Create Azure API Management Instance - Visual Studio Code
 description: Use this quickstart to create an Azure API Management instance with the API Management extension for Visual Studio Code.
 ms.service: azure-api-management
 author: dlepow
 ms.author: danlep
 ms.topic: quickstart
-ms.date: 12/12/2023
+ms.date: 10/14/2025
 ms.custom: mode-api, devdivchpfy22
 ---
 
@@ -21,7 +21,7 @@ This quickstart describes the steps to create a new API Management instance usin
 
 [!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
 
-Also, ensure you've installed the following:
+Also, ensure that you install:
 
 - [Visual Studio Code](https://code.visualstudio.com/)
 
@@ -37,15 +37,15 @@ Select **Sign in to Azure...** to launch a browser window and sign in to your Mi
 
 ## Create an API Management instance
 
-Once you're signed in to your Microsoft account, the *Azure: API Management* Explorer pane will list your Azure subscription(s). You can enable and disable this Explorer pane in the  *Azure API Management Extension Settings*.
+Once you're signed in to your Microsoft account, the *Azure: API Management* Explorer pane lists your Azure subscriptions. You can enable and disable this Explorer pane in the  *Azure API Management Extension Settings*.
 
 Right-click on the subscription you'd like to use, and select **Create API Management in Azure**.
 
 ![Create API Management wizard in VS Code](./media/vscode-create-service-instance/vscode-apim-create.png)
 
 In the pane that opens, supply a name for the new API Management instance. It must be globally unique within Azure and consist of 1-50 alphanumeric characters and/or hyphens. It should also start with a letter and end with an alphanumeric character.
 
-A new API Management instance (and parent resource group) will be created with the specified name. By default, the instance is created in the *West US* region with *Consumption* tier.
+A new API Management instance and parent resource group are created with the specified name. By default, the instance is created in the *West US* region with *Consumption* tier.
 
 > [!TIP]
 > If you enable **Advanced Creation** in the *Azure API Management Extension Settings*, you can also specify an [API Management tier](https://azure.microsoft.com/pricing/details/api-management/), Azure region, and [resource group](../azure-resource-manager/management/overview.md) to deploy your API Management instance.

articles/app-service/app-service-hybrid-connections.md

@@ -4,7 +4,7 @@ description: Learn how to create and use hybrid connections in Azure App Service
 author: seligj95
 ms.assetid: 66774bde-13f5-45d0-9a70-4e9536a4f619
 ms.topic: how-to
-ms.date: 07/07/2025
+ms.date: 10/15/2025
 ms.update-cycle: 1095-days
 ms.author: jordanselig
 #customer intent: As an app developer, I want to understand the usage of Hybrid Connections to provide access to apps in Azure App Service.
@@ -119,7 +119,7 @@ App Service Hybrid Connections are only available in Basic, Standard, Premium, a
 |:----|:----|
 | Basic | 5 per plan |
 | Standard | 25 per plan |
-| Premium (v1-v3) | 220 per app |
+| Premium (v1-v4) | 220 per app |
 | IsolatedV2 | 220 per app |
 
 The App Service plan UI shows you how many Hybrid Connections are being used and by what apps.
@@ -242,6 +242,23 @@ You can also show the details of a specific Hybrid Connection with the `hcm show
 
 :::image type="content" source="media/app-service-hybrid-connections/hybrid-connections-hcm-details-cli.png" alt-text="Screenshot of Hybrid Connection Details in CLI.":::
 
+### Configure proxy server settings
+
+If you need to configure proxy server settings for the Hybrid Connection Manager, edit the `ProxySettings` section in the `appsettings.json` file located at:
+
+- **Windows**: `C:\ProgramData\HybridConnectionManager\`
+- **Linux**: `/usr/share/HybridConnectionManager/`
+
+After you edit the configuration file, restart the Hybrid Connection Manager service to apply the new proxy settings:
+
+- **Windows**: Restart the service through **Services** from the **Start Menu**.
+- **Linux**: Run `systemctl restart hybridconnectionmanager.service`.
+
+Configuring a proxy server routes requests from the Hybrid Connection Manager through the selected proxy server before reaching the destination. Ensure your proxy server supports HTTP/HTTPS traffic so that the Hybrid Connection Manager can communicate with the Azure Relay Service.
+
+> [!NOTE]
+> All addresses set in `appsettings.json` (`ProxyAddress`, `BypassList`) should be in RegEx format if not an exact match.
+
 ### Redundancy
 
 Each Hybrid Connection Manager can support multiple Hybrid Connections. Multiple Hybrid Connection Managers can support any Hybrid Connection. The default behavior is to route traffic across the configured Hybrid Connection Managers for any given endpoint. If you want high availability on your Hybrid Connections from your network, run multiple Hybrid Connection Managers on separate machines. The load distribution algorithm used by the Relay service to distribute traffic to the Hybrid Connection Managers is random assignment.