Use the AVS Interconnect feature to connect private clouds in different availability zones
Impact:HighCategory:High Availability
APRL GUID:726abfe3-adae-4a6d-8eb8-4b27a7214ca1
Description:
Use the Interconnect feature for direct communication between private clouds in different availability zones, enabling connectivity between the private clouds management and workload networks.
Click the Azure Resource Graph tab to view the query
//cannot-be-validated-with-arg
Integrate LDAPS Identity with dual sources for enhanced NSX and vCenter security
Impact:HighCategory:Security
APRL GUID:c2794660-ffd7-4da3-96ba-5d546b70b1c6
Description:
Ensure two external identity sources are configured for NSX and vCenter Server. The VMware vCenter Server and NSX Manager use these for authentication with external identities.
Click the Azure Resource Graph tab to view the query
//cannot-be-validated-with-arg
Use HCX Network Extension High Availability
Impact:HighCategory:High Availability
APRL GUID:bce16eee-0933-4baa-ab4d-8d1bb5653fc2
Description:
Enable Network Extension High Availability for appliance failure tolerance in HCX service. It pairs selected appliances for Active Standby configuration, ensuring high availability and quick recovery, keeping configurations in-service despite failures.
Click the Azure Resource Graph tab to view the query
//cannot-be-validated-with-arg
Verify vSAN FTT configuration aligns with the cluster size
Impact:HighCategory:High Availability
APRL GUID:0943aa90-e3db-4c61-aef1-782b6a6a3881
Description:
The Azure VMware Solution's service SLA is influenced by vSAN storage policies, which change based on cluster size. For clusters over 6 hosts, an FTT-2 policy (RAID-1 or RAID-6) is advised. FTT refers to the Fault Tolerance feature.
Click the Azure Resource Graph tab to view the query
//cannot-be-validated-with-arg
Align ExpressRoute configuration with best practices for circuit resilience
Impact:HighCategory:High Availability
APRL GUID:6f573d60-be93-4f18-8016-42e923e3c05e
Description:
Microsoft suggests using two or more ExpressRoute circuits at distinct peering locations for critical workloads. Connect these circuits and your Azure VMware Solutions private clouds using Global Reach.
Click the Azure Resource Graph tab to view the query
//cannot-be-validated-with-arg
Deploy two or more circuits in different peering locations when using stretched clusters
Impact:HighCategory:High Availability
APRL GUID:91c84596-1c41-48fe-8d5e-3f817e6a273b
Description:
Azure VMware Solution vSAN stretched clusters cover 2 Availability Zones plus a third for witness. Use ExpressRoute for added resilience by deploying two circuits in different locations. With Global Reach, create a mesh topology by connecting on-premises circuits to Azure's managed circuits.
Click the Azure Resource Graph tab to view the query
//cannot-be-validated-with-arg
Deploy dual Azure VMware Solution clouds in different regions for disaster recovery
Impact:HighCategory:Disaster Recovery
APRL GUID:bdac462a-2eda-4a67-887d-46d58f141afe
Description:
Two Azure VMware Solution private clouds can be deployed in different regions for business continuity, implementing a mesh network topology based on ExpressRoute Gateway Connections and Global Reach Connections.