Single subscription scenario fails

[jdrepo]

Describe the bug

Tried to rollout single subscription scenario and got a deplyoment error in the "alz-MonitorPolicyLite" deployment. Seems to me that there are two management groups "-identity" and "-connectivity" expected to exist but they are not deployed.

Error messages

The management group 'trey-identity' cannot be found. (Code: ManagementGroupNotFound)

The management group 'trey-connectivity' cannot be found. (Code: ManagementGroupNotFound)

Steps to reproduce

1. Deploy with the attached parameter.json file

parameters.trey.json

Screenshots

[Springstone]

Hi @jdrepo, can you please share where you are deploying from? (the page specifically). Is there a specific scenario you are testing? (I see most options are disabled) The single subscription model is not regularly tested as this isn't the recommended deployment architecture, however, understand there are scenarios where this is the only option.

[jdrepo]

Hi @Springstone, I was deploying directy from the GitHub Repo ( https://github.com/Azure/Enterprise-Scale/#deploying-azure-landing-zones-enterprise-scale-architecture-in-your-own-environment ) I only disabled all the MDfC and Connectivity stuff, all the other options are enabled. I know that a single sub deployment is not the recommended way, I would like to use it to understand the ALZ concepts and workflows without the need to have minimum of 3 subs.

[Springstone]

@jdrepo confirm the issue, which is related to AMBA. We'll investigate how to resolve the issue, but as a workaround on the "Baseline alerts..." section, if you set the top two options to no, it should deploy fine:

[arjenhuitema]

Hi @jdrepo, thank you for reporting the problem. I have pinpointed the issue, and a solution is now in a pull request.

[jdrepo]

Hi @arjenhuitema , thanks for fixing, looking forward to the new version...