Skip to content

Commit e610822

Browse files
authored
Merge pull request #300857 from MicrosoftDocs/main
6/4/2025 PM Publish
2 parents 0d51111 + 6fcbd1e commit e610822

File tree

118 files changed

+582
-518
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

118 files changed

+582
-518
lines changed

articles/api-management/configure-service-update-settings.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ ms.author: danlep
1515

1616
This article shows you how to configure *service update* settings (preview) in your API Management instance. Azure periodically applies service updates automatically to API Management instances, using a phased rollout approach. These updates include new features, security enhancements, and reliability improvements.
1717

18-
You can't control exactly when Azure updates each API Management instance, but in select service tiers you can choose an *update group* for your instance so that it receives updates earlier or later than it usually would during an update rollout. You can also configure a *maintenance window* during the day when you want your instance to receive updates.
18+
You can't control exactly when Azure updates each API Management instance, but in select service tiers you can choose an *update group* (also called a *release channel*) for your instance so that it receives updates earlier or later than it usually would during an update rollout. You can also configure a *maintenance window* during the day when you want your instance to receive updates.
1919

2020
* **Update group** - A set of instances that receive API Management service updates during a production rollout, which can take from several days to several weeks to complete.
2121

2222
Choose from:
2323
* **Early** - Receive updates early in the rollout, for testing and early access to new features. This option is not recommended for production deployments.
2424
* **Default** - Receive updates as part of the regular release rollout. This option is recommended for most services, including production deployments.
2525
* **Late** - Receive updates later than the previous groups, typically weeks after the initial rollout. This option is recommended for mission-critical deployments only.
26-
* **AI Gateway Early** (GenAI release) - Get early access to the latest [AI gateway features and updates](genai-gateway-capabilities.md) before they reach other update groups. Receive other service updates as part of the **Late** rollout group.
26+
* **AI Gateway Early** (GenAI release channel) - Get early access to the latest [AI gateway features and updates](genai-gateway-capabilities.md) before they reach other update groups. Receive other service updates as part of the **Late** rollout group.
2727

2828
> [!NOTE]
2929
> Azure deploys all updates using a [safe deployment practices (SDP) framework](https://azure.microsoft.com/blog/advancing-safe-deployment-practices/). Updates released early in a rollout might be less stable and replaced later by stable releases. All instances are eventually updated to the most stable release builds.

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,7 @@ To help safeguard users from harmful, offensive, or misleading content, you can
126126
## Labs and samples
127127

128128
* [Labs for the AI gateway capabilities of Azure API Management](https://github.com/Azure-Samples/ai-gateway)
129+
* [AI gateway workshop](https://aka.ms/ai-gateway/workshop)
129130
* [Azure API Management (APIM) - Azure OpenAI Sample (Node.js)](https://github.com/Azure-Samples/genai-gateway-apim)
130131
* [Python sample code for using Azure OpenAI with API Management](https://github.com/Azure-Samples/openai-apim-lb/blob/main/docs/sample-code.md)
131132

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

Lines changed: 21 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: Hybrid connections in Azure App Service
33
description: Learn how to create and use hybrid connections in Azure App Service to access resources in disparate networks.
4-
author: madsd
4+
author: seligj95
55
ms.assetid: 66774bde-13f5-45d0-9a70-4e9536a4f619
66
ms.topic: article
7-
ms.date: 05/06/2025
8-
ms.author: madsd
7+
ms.date: 06/04/2025
8+
ms.author: jordanselig
99
ms.custom:
1010
- "UpdateFrequency3, fasttrack-edit"
1111
- build-2025
@@ -56,7 +56,7 @@ Things you can't do with Hybrid Connections include:
5656

5757
## Add and Create Hybrid Connections in your app
5858

59-
To create a Hybrid Connection:
59+
To create a Hybrid Connection in the Azure portal:
6060

6161
1. In the [Azure portal], select your app. Select **Settings** > **Networking**.
6262
1. Next to **Hybrid connections**, select the **Not configured** link. Here you can see the Hybrid Connections that are configured for your app.
@@ -84,6 +84,23 @@ When a Hybrid Connection is added to your app, you can see details on it simply
8484

8585
:::image type="content" source="media/app-service-hybrid-connections/hybrid-connections-properties.png" alt-text="Screenshot of Hybrid connections details.":::
8686

87+
### Create a Hybrid Connection in ARM/Bicep
88+
89+
To create a Hybrid Connection using an ARM/Bicep template, add the following resource to your existing template. You must include the `userMetadata` to have a valid Hybrid Connection. If you don't include the `userMetadata`, the Hybrid Connection doesn't work. If you create the Hybrid Connection in the Azure portal, this property is automatically filled in for you.
90+
91+
The `userMetadata` property should be a string representation of a JSON array in the format `[{"key": "endpoint", "value : "host:port"}]`. The following Bicep template has a sample for this property. For more information, see [Microsoft.Relay namespaces/hybridConnections](/azure/templates/microsoft.relay/namespaces/hybridconnections).
92+
93+
```bicep
94+
resource hybridConnection 'Microsoft.Relay/namespaces/hybridConnections@2024-01-01' = {
95+
parent: relayNamespace
96+
name: hybridConnectionName
97+
properties: {
98+
requiresClientAuthorization: true
99+
userMetadata: '[{"key": "endpoint", "value : "<HOST>:<PORT>"}]'
100+
}
101+
}
102+
```
103+
87104
### Create a Hybrid Connection in the Azure Relay portal
88105

89106
In addition to the portal experience from within your app, you can create Hybrid Connections from within the Azure Relay portal. For a Hybrid Connection to be used by App Service, it must:
Loading

articles/application-gateway/quick-create-portal.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,10 @@ Create the application gateway using the tabs on the **Create application gatewa
4545
- **Application gateway name**: Enter *myAppGateway* for the name of the application gateway.
4646
- Use the default selections for other settings.
4747

48-
![Screenshot of create new application gateway: basics.](./media/application-gateway-create-gateway-portal/application-gateway-create-basics.png)
48+
![Screenshot of create new application gateway: basics.](./media/application-gateway-create-gateway-portal/application-gateway-create-zone-redundant.png)
49+
50+
> [!NOTE]
51+
> Application Gateways are zone-redundant by default in regions that support multiple availability zones.
4952
5053
2. For Azure to communicate between the resources that you create, a virtual network is needed. You can either create a new virtual network or use an existing one. In this example, you'll create a new virtual network at the same time that you create the application gateway. Application Gateway instances are created in separate subnets. You create two subnets in this example: One for the application gateway, and another for the backend servers.
5154

8.34 KB
Loading

articles/azure-vmware/tutorial-scale-private-cloud.md

Lines changed: 24 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Tutorial - Scale clusters in a private cloud
33
description: In this tutorial, you use the Azure portal to scale an Azure VMware Solution private cloud.
44
ms.topic: tutorial
55
ms.service: azure-vmware
6-
ms.date: 6/7/2024
6+
ms.date: 6/4/2025
77
ms.custom: engagement-fy23
88

99
#Customer intent: As a VMware administrator, I want to learn how to scale an Azure VMware Solution private cloud in the Azure portal.
@@ -39,14 +39,9 @@ We do not allow the mixing of AV36, AV36P, or AV52 SKUs within the same cluster.
3939

4040
2. The deployment of the new cluster will begin.
4141

42-
## Scale a cluster
42+
## Scale a cluster - Host Addition
4343

44-
> [!NOTE]
45-
> Scaling down a cluster successfully requires all objects (VM/vmdk/iso/etc) on a vSAN datastore to be configured with a storage policy below or equal to [RAID level requirements](configure-storage-policy.md).
46-
> Scaling down a cluster will place requested host(s) into maintenance mode prior to actual removal of host from vCenter inventory.
4744

48-
> [!CAUTION]
49-
> Deleting a cluster terminates all running workloads and components and is an irreversible operation. Once you delete a cluster, you cannot recover the data.
5045

5146
1. In your Azure VMware Solution private cloud, under **Manage**, select **Clusters**.
5247

@@ -63,6 +58,28 @@ We do not allow the mixing of AV36, AV36P, or AV52 SKUs within the same cluster.
6358
>[!NOTE]
6459
>The hosts will be added to the cluster in parallel.
6560
61+
## Scale a cluster - Host Removal
62+
> [!CAUTION]
63+
> Deleting a cluster terminates all running workloads and components and is an irreversible operation. Once you delete a cluster, you cannot recover the data.
64+
65+
> [!NOTE]
66+
> Scaling down a cluster successfully requires all objects (VM/vmdk/iso/etc) on a vSAN datastore to be configured with a storage policy below or equal to [RAID level requirements](configure-storage-policy.md).
67+
> Scaling down a cluster will place requested host(s) into maintenance mode prior to actual removal of host from vCenter inventory.
68+
> Clusters cannot be scaled down past the minimum requirement of 3 hosts per cluster.
69+
70+
1. In your Azure VMware Solution private cloud, under **Manage**, select **Clusters**.
71+
72+
2. Select the cluster you want to scale down, select **More** (...), then select **Edit**.
73+
74+
:::image type="content" source="media/tutorial-scale-private-cloud/ss4-select-scale-private-cloud-2.png" alt-text="Screenshot showing where to edit an existing cluster." lightbox="media/tutorial-scale-private-cloud/ss4-select-scale-private-cloud-2.png" border="true":::
75+
76+
3. Select the host you want to remove, select **More** (...), select **Delete**, then select **Save**.
77+
78+
:::image type="content" source="media/tutorial-scale-private-cloud/remove-host-from-cluster.png" alt-text="Screenshot showing how to remove a host from an existing cluster." lightbox="media/tutorial-scale-private-cloud/remove-host-from-cluster.png" border="true":::
79+
80+
The removal of a host from the cluster begins.
81+
82+
6683
## Next steps
6784

6885
If you require another Azure VMware Solution private cloud, [create another private cloud](tutorial-create-private-cloud.md) following the same networking prerequisites, cluster, and host limits.

articles/baremetal-infrastructure/concepts-baremetal-infrastructure-overview.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ description: Provides an overview of the BareMetal Infrastructure on Azure.
66
ms.custom: references_regions
77
ms.topic: concept-article
88
ms.date: 08/15/2024
9+
# Customer intent: As a systems architect, I want to evaluate BareMetal Infrastructure options in Azure, so that I can determine if they meet the requirements for my mission-critical, specialized workloads and ensure optimal performance and control for my enterprise applications.
910
---
1011

1112
# What is BareMetal Infrastructure on Azure?

articles/baremetal-infrastructure/connect-baremetal-infrastructure.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ description: Learn how to identify and interact with BareMetal instances in the
66
ms.topic: how-to
77
ms.custom: devx-track-azurecli
88
ms.date: 08/15/2024
9+
# Customer intent: As an infrastructure administrator, I want to register and manage BareMetal instances in Azure using the portal or CLI, so that I can effectively deploy, monitor, and maintain high-performance applications on dedicated hardware.
910
---
1011

1112
# Connect BareMetal Infrastructure instances in Azure

articles/baremetal-infrastructure/know-baremetal-terms.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ ms.author: jacobjaygbay
55
description: Know the terms of Azure BareMetal Infrastructure.
66
ms.topic: concept-article
77
ms.date: 08/15/2024
8+
# Customer intent: "As an IT architect, I want to understand the key terms related to BareMetal Infrastructure, so that I can effectively plan and manage our deployment and utilization of these resources within our cloud architecture."
89
---
910

1011
# Know the terms for BareMetal Infrastructure

0 commit comments

Comments
 (0)