Updates

Author: msmbaldwin

articles/payment-hsm/deployment-scenarios.md

@@ -21,7 +21,7 @@ Thales doesn't provide PayShield SDK to customers, which supports HA over a clus
 
 > [!IMPORTANT]
 > - Virtual network peering does not support cross-region communication between payment HSM instances. A payment HSM instance in one region cannot communicate with a payment HSM instance in another region.  
-> - NSGs are not supported for payment HSM subnet.
+> - Network Security Groups and User Defined Routes are not not supported for payment HSM subnets.
 > - Customers can allocate a maximum of two payment HSMs from each stamp in one region under same subscription.
 > - If customer does not have a High Availability setup in their production environment, the customer will not be able to receive S2 support from Microsoft side.
 > - Please ensure your Microsoft Cloud Solution Architect has reviewed your payment HSM deployment architecture design and readiness before production launch.
@@ -41,6 +41,7 @@ This scenario caters to regional-level failure. The usual strategy is to complet
 ## Next steps
 
 - Learn more about [Azure Payment HSM](overview.md)
+- See the Azure Payment HSM [Solution design](solution-design.md)
 - Find out how to [get started with Azure Payment HSM](getting-started.md)
 - Learn how to [Create a payment HSM](create-payment-hsm.md)
 - Read the [frequently asked questions](faq.yml)

articles/payment-hsm/solution-design.md

@@ -1,6 +1,6 @@
 ---
-title: Solution design
-description: Learn about topologies and constraints for NC2 on Azure. 
+title: Solution design for Azure Payment HSM
+description: Learn about topologies and constraints for Azure Payment HSM
 ms.topic: conceptual
 ms.subservice: baremetal-nutanix
 ms.custom: engagement-fy23
@@ -9,43 +9,44 @@ ms.date: 10/13/2022
 
 # Solution design
 
-This article identifies topologies and constraints for NC2 on Azure.
+This article identifies topologies and constraints for Azure Payment HSM.
 
 ## Supported topologies
 
 The following table describes the network topologies supported by each network features configuration of NC2 on Azure.
 
 |Topology |Basic network features |
 | :------------------- |:---------------:|
-|Connectivity to BareMetal (BM) in a local VNet| Yes |
-|Connectivity to BM in a peered VNet (Same region)|Yes |
-|Connectivity to BM in a peered VNet (Cross region or global peering)|No |
-|Connectivity to a BM over ExpressRoute gateway |Yes|
-|ExpressRoute (ER) FastPath |No |
-|Connectivity from on-premises to a BM in a spoke VNet over ExpressRoute gateway and VNet peering with gateway transit|Yes |
-|Connectivity from on-premises to a BM in a spoke VNet over VPN gateway| Yes |
-|Connectivity from on-premises to a BM in a spoke VNet over VPN gateway and VNet peering with gateway transit| Yes |
-|Connectivity over Active/Passive VPN gateways| Yes |
-|Connectivity over Active/Active VPN gateways| No |
-|Connectivity over Active/Active Zone Redundant gateways| No |
-|Connectivity over Virtual WAN (VWAN)| No |
+|Connectivity to BareMetal (BM) in a local VNet | Yes |
+|Connectivity to BM in a peered VNet (Same region) | Yes |
+|Connectivity to BM in a peered VNet (Cross region or global peering) | No |
+|Connectivity to a BM over ExpressRoute gateway | Yes|
+|ExpressRoute (ER) FastPath | No |
+|Connectivity from on-premises to a BM in a spoke VNet over ExpressRoute gateway and VNet peering with gateway transit | Yes |
+|Connectivity from on-premises to a BM in a spoke VNet over VPN gateway | Yes |
+|Connectivity from on-premises to a BM in a spoke VNet over VPN gateway and VNet peering with gateway transit | Yes |
+|Connectivity over Active/Passive VPN gateways | Yes |
+|Connectivity over Active/Active VPN gateways | No |
+|Connectivity over Active/Active Zone Redundant gateways | No |
+|Connectivity over Virtual WAN (VWAN) | No |
 
 ## Constraints
 
 The following table describes what’s supported for each network features configuration:
 
 |Features |Basic network features |
 | :------------------- | -------------------: |
-|Delegated subnet per VNet |1|
-|[Network Security Groups](../../../virtual-network/network-security-groups-overview.md) on NC2 on Azure-delegated subnets|No|
-|[User-defined routes (UDRs)](../../../virtual-network/virtual-networks-udr-overview.md#user-defined) on NC2 on Azure-delegated subnets|No|
-|Connectivity to [private endpoints](../../../private-link/private-endpoint-overview.md)|No|
-|Load balancers for NC2 on Azure traffic|No|
-|Dual stack (IPv4 and IPv6) virtual network|IPv4 only supported|
+|Delegated subnet per VNet | 1 |
+|[Network Security Groups](../virtual-network/network-security-groups-overview.md) on NC2 on Azure-delegated subnets | No |
+|[User-defined routes (UDRs)](../virtual-network/virtual-networks-udr-overview.md#user-defined) on NC2 on Azure-delegated subnets | No |
+|Connectivity to [private endpoints](../private-link/private-endpoint-overview.md) | No |
+|Load balancers for NC2 on Azure traffic | No |
+|Dual stack (IPv4 and IPv6) virtual network | IPv4 only supported |
 
 ## Next steps
 
-Learn more:
-
-> [!div class="nextstepaction"]
-> [Architecture](architecture.md)
+- Learn more about [Azure Payment HSM](overview.md)
+- See Azure Payment HSM [Deployment Scenarios](deployment-scenarios.md)
+- Find out how to [get started with Azure Payment HSM](getting-started.md)
+- Learn how to [Create a payment HSM](create-payment-hsm.md)
+- Read the [frequently asked questions](faq.yml)

articles/payment-hsm/toc.yml

@@ -55,6 +55,8 @@
   items:
   - name: High availability & disaster recovery
     href: deployment-scenarios.md
+  - name: Solution design
+    href: solution-design.md
 
 - name: Support
   items: