AVD Pattern - Unable to deploy because policy blocks Automation Accounts with Public Access Enabled

[shawntmeyer]

I've reviewed the underlying templates and realize that you enable public access to the automation account because you don't collect this parameter or the PrivateEndpoints array parameter. If access to the automation account is needed, please provide an option to submit the private endpoint Subnet ResourceId and PrivateDNS Zones for automation accounts.

[JCoreMS]

Thanks @shawntmeyer, valid security concern that was overlooked early on that we'll try to address. Ultimately, we want to get away from an automation account with some revised queries for KQL. Stay tuned.

[JCoreMS]

@shawntmeyer this is unfortunately still on the backlog as we wait for a feature to be released in the US Gov cloud to move away from Automation Accounts.