Skip to content

Commit c670c36

Browse files
authored
Merge pull request #300426 from MicrosoftDocs/main
5/27/2025 AM Publish
2 parents f39a724 + 40fbaf2 commit c670c36

File tree

71 files changed

+910
-300
lines changed

Some content is hidden

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

71 files changed

+910
-300
lines changed

articles/api-management/set-header-policy.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,10 +67,11 @@ User-Agent: value2
6767
User-Agent: value3
6868
```
6969

70-
The following limitations apply:
70+
#### Limitations
7171

72-
- Removal of `Server` header isn't supported.
73-
- Headers: `Connection`, `ContentLength`, `KeepAlive`, `TransferEncoding` cannot be modified or deleted.
72+
- The following headers can't be appended, overridden, or deleted: `Connection`, `Content-Length`, `Keep-Alive`, `Transfer-Encoding`
73+
- The client IP address value in the `X-Forwarded-For` header can't be deleted
74+
- The `Server` header can't be deleted in responses
7475

7576
## Examples
7677

articles/application-gateway/http-response-codes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ Other reasons for clients receiving 403 responses include:
9797

9898
#### 404 – Page not found
9999

100-
An HTTP 404 response is generated when a request is made to Application Gateway (V2 SKUs) with a hostname that doesn’t corresponds to any of the configured Multi-site listeners, and there is no Basic listener present. Learn more about [types of listeners](application-gateway-components.md#types-of-listeners.
100+
An HTTP 404 response is generated when a request is made to Application Gateway (V2 SKUs) with a hostname that doesn’t corresponds to any of the configured Multi-site listeners, and there is no Basic listener present. Learn more about [types of listeners](application-gateway-components.md#types-of-listeners).
101101

102102
#### 408 – Request Time-out
103103

articles/automation/shared-resources/modules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Manage modules in Azure Automation
33
description: This article tells how to use PowerShell modules to enable cmdlets in runbooks and DSC resources in DSC configurations.
44
services: automation
55
ms.subservice: shared-capabilities
6-
ms.date: 10/01/2024
6+
ms.date: 05/27/2025
77
ms.topic: how-to
88
ms.custom: devx-track-azurepowershell, devx-track-python
99
ms.service: azure-automation

articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ In this tutorial, you learn how to:
2121

2222
> [!div class="checklist"]
2323
> * Set up dynamic configuration refresh for your Azure Functions app.
24-
> * Enable automatic configuration refresh using App Configuraion middleware.
24+
> * Enable automatic configuration refresh using App Configuration middleware.
2525
> * Use the latest configuration in Function calls when changes occur in your App Configuration store.
2626
2727
## Prerequisites

articles/azure-cache-for-redis/cache-how-to-scale.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ az redis update --cluster-name myCache --resource-group myGroup --set "sku.name"
137137
For more information on scaling with Azure CLI, see [Change settings of an existing Azure Cache for Redis](cache-manage-cli.md#scale).
138138

139139
> [!NOTE]
140-
> When you scale a cache up or down programatically (e.g. using PowerShell or Azure CLI), any `maxmemory-reserved` or `maxfragmentationmemory-reserved` are ignored as part of the update request. Only your scaling change is honored. You can update these memory settings after the scaling operation has completed.
140+
> When you scale a cache up or down programmatically (e.g. using PowerShell or Azure CLI), any `maxmemory-reserved` or `maxfragmentationmemory-reserved` are ignored as part of the update request. Only your scaling change is honored. You can update these memory settings after the scaling operation has completed.
141141
>
142142
143143
### [Scale out and in - Premium only](#tab/scale-out-and-in---premium-only)

articles/azure-compute-fleet/faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ sections:
1919
- question: |
2020
How many virtual machines (VMs) can I deploy using Azure Compute fleet?
2121
answer: |
22-
Compute Fleet allows you to deploy up to 10,000 VMs in a singe request, as long as you have enough quota of Spot VMs and Standard VMs.
22+
Compute Fleet allows you to deploy up to 10,000 VMs in a single request, as long as you have enough quota of Spot VMs and Standard VMs.
2323
- question: |
2424
Can I specify target capacity at a Compute Fleet level without specifying Spot and Standard capacity?
2525
answer: |
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: VMware Cloud Director with Azure VMware Solution Networking
3+
description: This article explains how to enable network for VMware Cloud director tenants on Azure VMware Solution
4+
ms.topic: how-to
5+
author: rdutt
6+
ms.service: azure-vmware
7+
ms.date: 4/24/2025
8+
---
9+
10+
# VMware Cloud Director on Azure VMware Solution network scenarios
11+
12+
VMware Cloud Director on Azure VMware Solution offers a robust platform for managing multitenancy, enabling organizations to create secure, isolated virtual data centers. This article provides various network connectivity scenarios for VMware Cloud Director tenants, including connecting to the internet and accessing Azure services. By leveraging the flexibility of VMware Cloud Director and Azure VMware Solution, tenants can achieve seamless integration with external networks and Azure resources, ensuring efficient and scalable operations.
13+
14+
15+
## Connect VMware Cloud Director tenants on Azure VMware Solution to internet
16+
17+
- To achieve internet connectivity, the provider can create organization virtual data center's with an organization edge gateway (Tier-1) router and assign Public IP for NAT configuration.
18+
19+
- Learn about how to [Turn on public IP addresses to an NSX Edge node for VMware NSX](enable-public-ip-nsx-edge.md).
20+
21+
- VMware Cloud Director Tenants can use the public IP address for SNAT configuration to enable Internet access for virtual machine in tenant's organization virtual data center.
22+
23+
:::image type="content" source="media/vmware-cloud-director/vmware-cloud-director-internet-diagram.png" alt-text="Diagram showing how tenants in VMware Cloud Director connects to internet in Azure VMware Solution." border="false" lightbox="media/vmware-cloud-director/vmware-cloud-director-internet-diagram.png":::
24+
25+
- Organization virtual data center Edge gateway has default DENY ALL firewall rule. Virtual datacenter organization administrators need to open appropriate ports to allow access through the firewall by adding a new firewall rule.
26+
27+
> [!Note]
28+
> To manage overlapping IP address, use NAT to prevent conflicts in end-to-end routing scenarios.
29+
30+
31+
## Connect VMware Cloud Director tenants workloads with Azure services
32+
33+
To enable access to Azure services in Azure virtual network, you can create a site to site VPN connection from VMware Cloud Director tenant's organization edge router gateway and Azure VPN gateway.
34+
35+
:::image type="content" source="media/vmware-cloud-director/vmware-cloud-director-azure-services-diagram.png" alt-text="Diagram showing how tenants in VMware Cloud Director connects to Azure services in Azure VMware Solution." border="false" lightbox="media/vmware-cloud-director/vmware-cloud-director-azure-services-diagram.png":::
36+
37+
Follow the steps below to achieve this connectivity:
38+
- Configure Azure virtual network with an Azure VPN gateway.
39+
- Follow this document to create an [Azure virtual network gateway](tutorial-configure-networking.md)
40+
- A site-to-site VPN is established between tenant’s organization virtual data center and Azure virtual network. To achieve this connectivity, the tenant provides a public IP to the organization virtual datacenter. Both source and destination of the tunnel should have identical settings for IKE, SA, DPD etc.
41+
- The organization virtual datacenter administrator can configure IPsec VPN connectivity using VMware Cloud Director.
42+
43+
> [!Note]
44+
> VMware Cloud Director supports a policy-based VPN. Azure VPN gateway configures route-based VPN by default and to configure policy-based VPN policy-based selector needs to be enabled.
45+
46+
- Organization virtual data center edge router firewall denies traffic by default. You need to apply specific rules to enable connectivity. Use the following steps to apply firewall rules.
47+
48+
## Related topics
49+
50+
[How to enable VMware Cloud Director on Azure VMware Solution](enable-vmware-vcd-with-azure.md)
51+
52+
[VMware Cloud Director](https://techdocs.broadcom.com/us/en/vmware-cis/cloud-director/vmware-cloud-director/10-6/overview.html)
53+
54+
[Architecture - Network interconnectivity - Azure VMware Solution](architecture-networking.md)

0 commit comments

Comments
 (0)