Johan Dahlbom

I agree with @jtracey93 that it would add value as long as we provide guidance on where it can/should be assigned to ensure that the alert will be received by...

Looping in @krnese for visibility.

@pkorolo - I have done some investigation and this is related to the shift to built-in policies for this that was done in our July update, where blob is not...

We already provide a custom policy to deny creation of [Micosoft.Network/privateDnsZones](https://github.com/Azure/Enterprise-Scale/blob/main/eslzArm/managementGroupTemplates/policyDefinitions/policies.json#L7564), but I do agree that we should provide an option to assign it as part of the reference implementations....

Thank you for the input. Currently, we recommend assigning this policy at the [Landing Zones or Landing Zones/Corp management group](https://github.com/Azure/Enterprise-Scale/blob/main/docs/ESLZ-Policies.md) since that is where we host all the subscriptions targeted...

That's what I thought, thank you for confirming! :)

@SimonWahlin can you please take a look at this one?

I have tested the functionality and it works as expected - awesome job! 😄 Do you think it makes sense to externalize the script as it becomes quite cumbersome to...

> Sure, I can put the code in a scripts folder. How about .pipelines/.script/customSortOrder.ps1? > > Or maybe have a generic location for both GitHub and ADO? Maybe .scripts/customSortOrder.ps1? Sounds...

Can you share the details of the errors? Same as before or something else?