-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question/Feedback]: Create deployable Policy Initiatives from Azure Resources templates for Landing Zones #214
Comments
Hello @nekdima , Let us know if this helps. Thanks, |
Hey @Brunoga-MS , Thank you for the prompt reply. I'm aware of this initiative, however it's covering just a few resources like VM, AGW, PIP & KeyVault. What about all the other resources one can have? There are many Azure Alerts (including auto generated ones) which are listed in the spreadsheet but aren't part of the initiative and exist only in the form of ARM/BICEP template. My customer had the expectation that all of these will be a part of the LZ Initiative. |
Hey @nekdima , Thanks, |
Hey @Brunoga-MS, You might consider concentrating on the items listed under "Azure Resources" on the AMBA website. Although they are all currently listed, there is no scalable method to deploy them as a policy. |
@nekdima thanks for your feedback on this, I'm tagging @JoeyBarnes who owns AMBA all up to provide a response. @Brunoga-MS, @arjenhuitema and myself manage the ALZ Pattern which includes Policies. |
Check for previous/existing GitHub issues
Description
Hello Team,
The AMBA website currently offers a variety of templates for Azure Alerts creation as ARM and BICEP templates. However, these are challenging to implement on a large scale. It would be beneficial to create an Azure Policy Initiative for "Landing Zones"(there is already one for "Platform") to ensure that Azure Alerts are automatically deployed when a policy identifies the presence of a resource within its scope.
Tagging for visibility: @arjenhuitema
The text was updated successfully, but these errors were encountered: