Hello @ryosk25 , Thank you for reaching out.
As per the documentation here Virtual Network NAT simplifies outbound Internet connectivity for virtual network. When configured on a subnet, all outbound connectivity uses the Virtual Network NAT's static public IP addresses. A NAT gateway can’t span multiple virtual networks. You can associate multiple subnets in a VNET to Nat Gateway. So as per this FAQ NAT gateway can only be used by a virtual network that the NAT gateway is directly connected to and cannot traverse multiple virtual networks. In a scenario in which virtual network A is peered with virtual network B and NAT gateway is directly associated with virtual network A, virtual network B cannot use NAT gateway to direct outbound traffic. Virtual network B will need its own NAT gateway to make outbound connections. My recommendation in this scenario will be to deploy NAT Gateway to the VNET which requires outbound connectivity to internet.
You can go through this documentation for information on other options for outbound internet connectivity. You can also use Azure Firewall for outbound connectivity as shown in architecture link you shared above, and you can deploy a Azure Firewall with multiple public IP addresses.
Hope this helps! Please let me know if you have any additional questions. Thank you!