Skip to content

Commit 6c9bf21

Browse files
authored
Merge pull request #276301 from rvandenbedem/patch-2
Update faq.yml
2 parents 37bc195 + ce27236 commit 6c9bf21

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/azure-vmware/faq.yml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ metadata:
44
description: "Get answers to common questions about Azure VMware Solution."
55
ms.topic: faq
66
ms.service: azure-vmware
7-
ms.date: 2/29/2024
7+
ms.date: 5/24/2024
88
title: Common questions about Azure VMware Solution
99
summary: This article answers commonly asked questions about Azure VMware Solution.
1010

@@ -136,6 +136,9 @@ sections:
136136

137137
- question: Is NSX Identity Firewall and distributed IDS/IPS supported with Azure VMware Solution?
138138
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.
139142

140143
- question: Is VMware Horizon 8 2012 compatible with Azure VMware Solution?
141144
answer: Yes.
@@ -232,7 +235,7 @@ sections:
232235

233236
- question: Why can't I reach the Azure VMware Solution vCenter Server Appliance and NSX Manager from on-premises or Azure Virtual Network?
234237
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.
236239
237240
238241
- name: Storage

0 commit comments

Comments
 (0)