You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/upgrade-hcx-azure-vmware-solutions.md
+43-6Lines changed: 43 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Upgrade HCX on Azure VMware Solution
3
3
description: This article explains how to upgrade HCX on Azure VMware Solution.
4
4
ms.topic: how-to
5
-
ms.date: 02/26/2025
5
+
ms.date: 05/23/2025
6
6
ms.custom: engagement-fy23
7
7
---
8
8
@@ -21,15 +21,15 @@ You can update HCX Connector and HCX Cloud systems during separate maintenance w
21
21
22
22
- For more information about the upgrade path, see the [Product Interoperability Matrix](https://interopmatrix.broadcom.com/Upgrade?productId=660).
23
23
- For information regarding VMware product compatibility by version, see the [Compatibility Matrix](https://interopmatrix.broadcom.com/Interoperability?col=660,&row=0,).
24
-
- Review VMware Software Versioning, Skew and Legacy Support Policies [here](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-support-and-lifecycle-policies-4-10/software-versioning-skew-and-legacy-support-policies.html).
24
+
- Review VMware Software Versioning, Skew, and Legacy Support Policies [here](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-support-and-lifecycle-policies-4-10/software-versioning-skew-and-legacy-support-policies.html).
25
25
26
26
- Ensure HCX manager and site pair configurations are healthy.
27
27
28
28
- As part of HCX update planning, and to ensure that HCX components are updated successfully, review the service update considerations and requirements. For planning HCX upgrade, see [Planning for HCX Updates](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/updating-vmware-hcx/planning-for-hcx-updates.html).
29
29
30
30
- Ensure that you have a backup and snapshot of HCX connector in the on-premises environment, if applicable.
31
31
- For more information, see the [HCX support policy for legacy vSphere environment](https://knowledge.broadcom.com/external/article?legacyId=82702).
32
-
- Check that you are using the [latest VMware HCX version validated with Azure VMware Solution](introduction.md#vmware-software-versions).
32
+
- Check that you're using the [latest VMware HCX version validated with Azure VMware Solution](introduction.md#vmware-software-versions).
@@ -81,8 +81,45 @@ While Service Mesh appliances are upgraded independently to the HCX Manager, the
81
81
- No VM migrations should be in progress during this upgrade.
82
82
83
83
**Procedure**
84
-
85
-
To follow the Service Mesh appliances upgrade process, see [Upgrading the HCX Service Mesh Appliances](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/updating-vmware-hcx/hcx-service-update-procedures/upgrade-the-hcx-service-mesh-appliances.html)
84
+
85
+
To follow the Service Mesh appliances upgrade process, see [Upgrading the HCX Service Mesh Appliances](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/updating-vmware-hcx/hcx-service-update-procedures/upgrade-the-hcx-service-mesh-appliances.html)
86
+
87
+
## HCX 4.11.0 Upgrade and what it means for current HCX users
88
+
89
+
### Overview
90
+
91
+
Broadcom has announced the end-of-support (EOS) for VMware HCX version 4.10.x, effective July 27, 2025. To proactively address this change and ensure continued support, Microsoft will begin upgrading all Azure VMware Solution customers using HCX Manager to HCX version 4.11.0.
92
+
The upgrade process will commence in June 2025. Each customer will receive a notification at least one week prior to their scheduled upgrade window.
93
+
94
+
### What changes are introduced as part of HCX 4.11.0?
95
+
96
+
Refer to [HCX 4.11.0 release notes](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-11/hcx-4-11-release-notes/vmware-hcx-411-release-notes.html) for more information on what’s new with HCX 4.11. Some noteworthy changes are listed below:
97
+
98
+
#### Local Mode
99
+
100
+
From HCX 4.11.0 onwards, only HCX local mode is available. This means that HCX systems running 4.11.0 or later will no longer receive upgrade notifications under the System Updates section from Broadcom. Connected Sites that upgrade to 4.11.0 using offline bundles will operate in Local Mode after the upgrade.
101
+
102
+
#### Connection to VMware & Hybridity Depot
103
+
104
+
Activation Keys-based licensing is deprecated as of HCX 4.11.0. Activation Keys in HCX 4.11.0 will stop working 450 days after the upgrade to HCX 4.11.0 takes place. HCX systems running older versions that are currently using Activation Keys will stop working when connect.hcx.vmware.com is decommissioned.
105
+
106
+
- <ins>hybridity-depot.vmware.com</ins> and <ins>connect.hcx.vmware.com</ins> endpoints for licensing, activation, and updates are removed post-activation or upgrade to HCX 4.11.0. HCX services of <ins>hybridity-depot.vmware.com</ins> and <ins>connect.hcx.vmware.com</ins> will be decommissioned.
107
+
- All connected systems automatically transition to local licensing mode as part of upgrade to 4.11.0.
108
+
109
+
Moving forward, until customers are upgraded to HCX 4.11.0, they'll need to submit a Support Request to receive the requested upgrade bundle for their chosen HCX connection version. After the upgrade has taken place, customers will find previous and current versions of HCX Connector bundles, including HCX 4.11.0, in their vSAN datastores under a folder named _"AVS_Official_HCX_Connector_Binaries"_.
110
+
111
+
>[!NOTE]
112
+
> The following HCX functionality is **deprecated** in HCX 4.11.0 and will be **removed** in a future release. HCX 4.11.0 will no longer be supported as of December 24, 2025. Customers should plan to migrate to an alternative solution at the earliest if they use any of the following features:
113
+
> - HCX V2T Migration
114
+
> - HCX WAN Optimization
115
+
> - HCX Disaster Recovery
116
+
> - vCenter Server Plug-in for HCX
117
+
> - HCX UI - Tracking page in Migration interface
118
+
119
+
120
+
### What actions will the customer need to take?
121
+
122
+
To ensure smooth migration, customers are required to upgrade any paired HCX connectors and service mesh appliances to HCX 4.11.0. Furthermore, customers may be required to execute a resync operation on each HCX service mesh on both the source and connector sides to ensure that no errors have occurred due to the upgrade.
86
123
87
124
## FAQ
88
125
@@ -100,6 +137,6 @@ The HCX Service Mesh can be upgraded once all paired HCX Manager systems are upd
100
137
See [Rolling Back an Upgrade Using Snapshots](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/updating-vmware-hcx/hcx-service-update-procedures/rolling-back-an-upgrade-using-snapshots.html) to roll back the upgrade.
101
138
102
139
## Next steps
103
-
[Software Versioning, Skew and Legacy Support Policies](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-support-and-lifecycle-policies-4-10/software-versioning-skew-and-legacy-support-policies.html)
140
+
[Software Versioning, Skew, and Legacy Support Policies](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-support-and-lifecycle-policies-4-10/software-versioning-skew-and-legacy-support-policies.html)
0 commit comments