Add Regulatory Compliance Policy Assignment Flexibility Feature

[jtracey93]

Overview/Summary

This pull request introduces changes to the eslzArm/eslzArm.json file to incorporate Regulatory Compliance policies. The changes primarily involve the addition of new parameters and deployment configurations to support these policies.

Key changes include:

New Parameters:

• Added multiple new parameters related to Regulatory Compliance policies, including regulatoryComplianceInitativesToAssign, regCompPolParAusGovIsmRestrictedVmAdminsExclude, regCompPolParMPAAApplicationName, and others. These parameters are used to configure and control the application of the Regulatory Compliance policies.

Deployment Configuration:

• Added a new deployment configuration for Regulatory Compliance policies. This includes defining the deployment name (regulatoryComplianceInitativesToAssignDeploymentName) and the deployment URI (regulatoryComplianceInitaitves). [1] [2]

Deployment Resource:

• Added a new deployment resource for assigning Regulatory Compliance policies to desired management groups. This includes setting up the condition for deployment, defining the scope, dependencies, and properties for the deployment, and passing the necessary parameters.

Breaking Changes

None

Testing Evidence

Testing URLs

Azure Public

As part of this Pull Request I have

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