The Azure Landing Zones (Enterprise-Scale) architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture
Azure Landing zone guidance for networking include usage of this party NVA . In the event when a certain region has capacity issue, such NVA product would have issue deploying due to their underlying nature of using virtual machine/compute . Constraint in compute resources prevent deployment of such product during capacity limitation timeframe.
*[following are suggestions for possible solution]
I would like to a solution where networking is not dependent on NVA but this might not be possible due to customer using NVA for novel features.
Another possible solution would be to suggest and document alternative solution for NVA in enterprise scale. Such solution might include deploying NVA to pair region or deploying it to alternative region where network data routing is not subjected to regulatory compliance.
Temporary alternative to NVA and then reverting to NVA solution for networking in enterprise scale in the event of capacity limitation
Azure Landing zone guidance for networking include usage of this party NVA . In the event when a certain region has capacity issue, such NVA product would have issue deploying due to their underlying nature of using virtual machine/compute . Constraint in compute resources prevent deployment of such product during capacity limitation timeframe.
*[following are suggestions for possible solution]