Fix for #1565: pass userAssignedIdentityResourceGroup to deployment (#1566)

Author: SvenAelterman

docs/wiki/Whats-new.md

@@ -45,6 +45,7 @@ Here's what's changed in Enterprise Scale/Azure Landing Zones:
 
 - Disabled a Policy in the Microsoft Defender for SQL initiative. As it is not required at this stage. See [ALZ AMA FAQ](./ALZ-AMA-FAQ) for more details.
 - Changed enforcementMode of the assignment of Policy "Deploy-UserAssignedManagedIdentity-VMInsights" to Default. This is to ensure that a Resource Group and a User Assigned Managed Identity are created on new subscriptions (subscriptions that are added after the initial deployment).
+- Bug fix for Portal Accelerator. userAssignedIdentityResourceGroup has been added as output for the Portal UI, this fixes deploying the Resource Group with a custom name.
 
 ### AMA Update for the Portal Accelerator
 

eslzArm/eslz-portal.json

@@ -3971,7 +3971,8 @@
                 "auditAppGwWaf": "[steps('landingZones').lzSection.auditAppGwWaf]",
                 "enforceAcsb": "[steps('landingZones').lzSection.enforceAcsb]",
                 "enableDecommissioned": "[steps('decommissionedSandboxZones').decommSection.enableDecommissioned]",
-                "enableSandbox": "[steps('decommissionedSandboxZones').sandboxSection.enableSandbox]"
+                "enableSandbox": "[steps('decommissionedSandboxZones').sandboxSection.enableSandbox]",
+                "userAssignedIdentityResourceGroup": "[steps('management').userAssignedIdentityResourceGroup]"
             },
             "kind": "Tenant",
             "location": "[steps('basics').resourceScope.location.name]"