diff --git a/docs/wiki/Whats-new.md b/docs/wiki/Whats-new.md index ad127c11fc..ce3cfc44f4 100644 --- a/docs/wiki/Whats-new.md +++ b/docs/wiki/Whats-new.md @@ -46,6 +46,7 @@ Here's what's changed in Enterprise Scale/Azure Landing Zones: - Added virtual hub routing preference support to Portal Accelerator for scenarios where you need to influence routing decisions in virtual hub router towards on-premises. For existing ALZ customers please visit [Configure virtual hub routing preference](https://learn.microsoft.com/azure/virtual-wan/howto-virtual-hub-routing-preference) for details on how to configure virtual hub routing preference settings. - Added virtual hub capacity option to Portal Accelerator which provides an option to select the number of routing infrastracture units. Please visit [Virtual hub capacity](https://learn.microsoft.com/azure/virtual-wan/hub-settings#capacity) for more details on Azure vWAN Virtual Hub Capacity configuration. +- Fixed a bug in the portal accelerator experience when deploying with single platform subscription and selecting virtual WAN networking topology - Invalid Template error. #### Docs - Fixed in ALZ Azure Setup the bash command to assign at root scope _Owner_ role to a Service Principal. diff --git a/eslzArm/eslzArm.json b/eslzArm/eslzArm.json index d94df04956..b056838135 100644 --- a/eslzArm/eslzArm.json +++ b/eslzArm/eslzArm.json @@ -4395,6 +4395,21 @@ }, "vpnGateWayScaleUnit": { "value": "[parameters('vpnGateWayScaleUnit')]" + }, + "enablevWANRoutingIntent":{ + "value":"[parameters('enablevWANRoutingIntent')]" + }, + "internetTrafficRoutingPolicy":{ + "value":"[parameters('internetTrafficRoutingPolicy')]" + }, + "privateTrafficRoutingPolicy":{ + "value":"[parameters('privateTrafficRoutingPolicy')]" + }, + "vWANHubRoutingPreference":{ + "value":"[parameters('vWANHubRoutingPreference')]" + }, + "vWanHubCapacity":{ + "value":"[parameters('vWANHubCapacity')]" } } }