Portal updates

[arjenhuitema]

This pull request introduces several enhancements and improvements across Azure Landing Zones documentation and ARM templates, focusing on greater flexibility, resource naming standardization, and expanded portal capabilities. The most notable changes include the implementation of default naming standards, improved customization options for resource names, updates to policy assignments, and new networking features in the portal accelerator.

Documentation and Portal Experience Updates:

• Added documentation for the implementation of default Cloud Adoption Framework (CAF) naming standards across all resources, with support for custom naming conventions.
• Updated the portal accelerator to support Bastion and Private DNS Resolver as selectable networking options, with guidance for configuring Private DNS Resolver. [1] [2]

Resource Naming and Template Flexibility:

• Standardized resource group naming for Microsoft Defender for Cloud export and Azure Security Center export by introducing or updating parameters and variable logic in multiple templates, allowing for consistent and customizable naming. [1] [2] [3] [4] [5]
• Enhanced prerequisite and route table templates to allow dynamic naming of resource groups, managed identities, deployment scripts, and route tables based on location and management group prefix. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Policy Assignment Improvements:

• Added new parameters and made logic improvements to policy assignment templates for Microsoft Defender for Cloud and Service Health, enabling more flexible configuration of resource group names and improved mapping of role IDs to names. [1] [2] [3] [4]

Template Parameter Additions:

• Introduced topLevelManagementGroupPrefix as a required parameter in the AVNM configuration template to ensure unique and consistent resource naming.

Testing Evidence

Please provide any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate).

Testing URLs

The below URLs can be updated where the placeholders are, look for {YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also} & {YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also}, to allow you to test your portal deployment experience.

Please also replace the curly brackets on the placeholders {}

Azure Public

[](https://portal.azure.com/#blade/Microsoft_Azure_CreateUIDef/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2F{YOUR GITHUB ORG/ACCOUNT HERE - Remove Curly Brackets Also}%2FEnterprise-Scale%2F{YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also}%2FeslzArm%2FeslzArm.json/uiFormDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2F{YOUR GITHUB ORG/ACCOUNT HERE - Remove Curly Brackets Also}%2FEnterprise-Scale%2F{YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also}%2FeslzArm%2Feslz-portal.json)

Azure US Gov (Fairfax)

[](https://portal.azure.us/#blade/Microsoft_Azure_CreateUIDef/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2F{YOUR GITHUB ORG/ACCOUNT HERE - Remove Curly Brackets Also}%2FEnterprise-Scale%2F{YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also}%2FeslzArm%2FeslzArm.json/uiFormDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2F{YOUR GITHUB ORG/ACCOUNT HERE - Remove Curly Brackets Also}%2FEnterprise-Scale%2F{YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also}%2FeslzArm%2Ffairfaxeslz-portal.json)

As part of this Pull Request I have

• Checked for duplicate Pull Requests
• Associated it with relevant issues, for tracking and closure.
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Ensured contribution guidance is followed.
• Updated relevant and associated documentation.
• Updated the "What's New?" wiki page (located: /docs/wiki/whats-new.md)