From 3c566c8648a33a544e79ca1ed66fb02eaf7c9305 Mon Sep 17 00:00:00 2001
From: hansdoerr <50683219+hansdoerr@users.noreply.github.com>
Date: Sat, 6 Jul 2024 13:36:36 -0400
Subject: [PATCH] Update mlz.portal.json

Updated "azureGateSubnetAddressPrefix" in bicep/form/mlz.portal.json to say "azureGatewaySubnetAddressPrefix".  This enables users to deploy the template spec with other than default Gateway subnet settings, because it will error out otherwise, since the deployment will use the mlz.json setting for the Gateway Subnet and the mlz.portal.json entry won't match.
---
 src/bicep/form/mlz.portal.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/bicep/form/mlz.portal.json b/src/bicep/form/mlz.portal.json
index ded687a2d..301be9548 100644
--- a/src/bicep/form/mlz.portal.json
+++ b/src/bicep/form/mlz.portal.json
@@ -1265,7 +1265,7 @@
       "subscriptionId": "[steps('basics').hubSection.hubSubscriptionId]",
       "parameters": {
         "bastionHostSubnetAddressPrefix": "[steps('remoteAccess').azureBastionSection.bastionSubnetAddressCidrRange]",
-        "azureGateSubnetAddressPrefix": "[steps('remoteAccess').azureGatewaySubnetSection.azureGatewaySubnetAddressCidrRange]",
+        "azureGatewaySubnetAddressPrefix": "[steps('remoteAccess').azureGatewaySubnetSection.azureGatewaySubnetAddressCidrRange]",
         "defenderSkuTier": "[if(steps('compliance').defenderSection.deployDefender, 'Standard', 'Free')]",
         "deployDefenderPlans": "[steps('compliance').defenderSection.deployDefenderPlans]",
         "deployIdentity": "[steps('basics').identitySection.deployIdentity]",
@@ -1307,4 +1307,4 @@
       }
     }
   }
-}
\ No newline at end of file
+}