Skip to content

Commit 9c601d3

Browse files
authored
Update vmware-software-update-frequency.md
1 parent 854bc2d commit 9c601d3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-vmware/includes/vmware-software-update-frequency.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: VMware software update frequency
33
description: Supported VMware software update frequency for Azure VMware Solution.
44
ms.topic: include
55
ms.service: azure-vmware
6-
ms.date: 09/17/2022
6+
ms.date: 12/12/2022
77
author: suzizuber
88
ms.author: v-szuber
99
---
@@ -13,7 +13,7 @@ ms.author: v-szuber
1313
One benefit of Azure VMware Solution private clouds is that the platform is maintained for you. Microsoft is responsible for the lifecycle management of VMware software (ESXi, vCenter Server, and vSAN). Microsoft is also responsible for the lifecycle management of the NSX-T Data Center appliances and bootstrapping the network configuration, like creating the Tier-0 gateway and enabling North-South routing. You’re responsible for the NSX-T Data Center SDN configuration: network segments, distributed firewall rules, Tier 1 gateways, and load balancers.
1414

1515
> [!NOTE]
16-
> A T0 gateway is created and configured as part of a private cloud deployment. Any modification to that logical router or the NSX-T Data Center edge node VMs could affect connectivity to your private cloud.
16+
> A T0 gateway is created and configured as part of a private cloud deployment. Any modification to that logical router or the NSX-T Data Center edge node VMs could affect connectivity to your private cloud and should be avoided.
1717
1818
Microsoft is responsible for applying any patches, updates, or upgrades to ESXi, vCenter Server, vSAN, and NSX-T Data Center in your private cloud. The impact of patches, updates, and upgrades on ESXi, vCenter Server, and NSX-T Data Center is different.
1919

0 commit comments

Comments
 (0)