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/faq.yml
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ metadata:
4
4
description: "Get answers to common questions about Azure VMware Solution."
5
5
ms.topic: faq
6
6
ms.service: azure-vmware
7
-
ms.date: 2/29/2024
7
+
ms.date: 5/24/2024
8
8
title: Common questions about Azure VMware Solution
9
9
summary: This article answers commonly asked questions about Azure VMware Solution.
10
10
@@ -136,6 +136,9 @@ sections:
136
136
137
137
- question: Is NSX Identity Firewall and distributed IDS/IPS supported with Azure VMware Solution?
138
138
answer: Yes with an add-on license. Azure VMware Solution supports distributed IDFW and distributed IDS/IPS with add-on firewall license. This add-on license needs to be bought from VMware and Microsoft will apply that license to the Azure VMware Solution private cloud with a support request.
139
+
140
+
- question: Is NSX Service Insertion supported with Azure VMware Solution?
141
+
answer: No.
139
142
140
143
- question: Is VMware Horizon 8 2012 compatible with Azure VMware Solution?
141
144
answer: Yes.
@@ -232,7 +235,7 @@ sections:
232
235
233
236
- question: Why can't I reach the Azure VMware Solution vCenter Server Appliance and NSX Manager from on-premises or Azure Virtual Network?
234
237
answer: |
235
-
By design, you won't be able to reach NSX Manager and vCenter Server Appliance (vCSA) from on-premises when only 0.0.0.0/0 (default route) is being advertised over ExpressRoute Global Reach between Azure VMware Solution and your on-premises ExpressRoute or through Azure Virtual Network to Azure VMware Solution. You need to advertise specific networking routes/subnets to access NSX-T Manager and vCSA.
238
+
By design, you won't be able to reach NSX Manager and vCenter Server Appliance (vCSA) from on-premises when only 0.0.0.0/0 (default route) is being advertised over ExpressRoute Global Reach between Azure VMware Solution and your on-premises ExpressRoute or through Azure Virtual Network to Azure VMware Solution. You need to advertise specific networking routes/subnets to access NSX Manager and vCSA.
0 commit comments