Sacha Narinx

@glsutter it may be that you're concerned about the "location" parameter in several DeployIfNotExists policies, that we default to "northeurope". This value is required for those deployments, but resources are...

@glsutter yes, this is correct. Deployment metadata would be stored in the associated region, but has no impact on deployed resources, their operation or management thereof. This is purely to...

@jtracey93 @stalejohnsen I agree that it would make sense to address this in the overall diagnostic settings migration stream, and to include this in the Q2CY23 policy refresh cycle as...

Closing this as we've deprecated all our diagnostic settings policies and shifted to the PG owned initiative to do the same. Please review https://aka.ms/alz/whatsnew for details.

@sshockley I'm not sure how you are going about this. You should be able to clone the repo and work from the `main` branch, as is and deploy the policies...

Just one point to note, the initiatives.json file REQUIRES a parameter to be provided (topLevelManagementGroupPrefix), which would be the intermediate root management group id. If you provide that as default...

And I just noticed that you mentioned you're deploying to US Gov, which is currently not validated in this repo. We do have it on our backlog to remediate missing...

Yes, that is correct. The initiatives bicep build does require the topLevelManagementGroupPrefix as it is used in several initiatives.

@sshockley thanks for raising this issue. This is a sovereign cloud issue, which has been difficult for us to triage as getting access to those environments is challenging. We now...

@arjenhuitema @jtracey93 this isn't AMBA related. This error is an issue with ESLite deployment, which is trying to deploy the DiagSettings initiative to Management, Identity and Connectivity MGs even though...