v.0.7.0

What's Changed

• Add Azure Devops pipeline sample by @jfaurskov in #183
• update operator for Disk Latency Alerts by @Alboroni in #197
• BICEP to ARM automatic conversion by Github Actions - update-2023-07-10 by @cae-pr-creator in #198
• Remove superfluous parameters from parameters by @jfaurskov in #201
• BICEP to ARM automatic conversion by Github Actions - update-2023-07-14 by @cae-pr-creator in #203
• standard param naming by @arjenhuitema in #204
• added TemplateFile parameter by @arjenhuitema in #208
• Moved description and displayName from metadata by @anwather in #206
• fix rg location, name and tags by @arjenhuitema in #215

Breaking changes

There has been an update to the landing zone initiative related to the VM policies, specifically to the resource group name, location and tag parameters. This change has reduced the number of parameters in the initiative. To update this initiative you will need to:

1. Update your local copy of the repo
2. Remove the initiative assignment for the landing zone initiative
3. Update the landing zone initiative to the current version
4. Reassign the landing zone initiative

New Contributors

• @anwather made their first contribution in #206

Full Changelog: v.0.6.0...v.0.7.0

v.0.6.0

What's Changed

• Created VM Insights table. by @bzabber in #186
• Fixed broken links and renamed ES to ALZ by @paulgrimley in #189
• Log Alert Policies in Landing Zone Inititative by @amillerb in #187
• Moved Feedback header up and added horn emoticon. by @bzabber in #191
• Update whatsnew by @jfaurskov in #194
• Prep for ESLZ move by @jfaurskov in #190

Breaking changes

There has been an update to the management initiative related to the policy used to deploy recovery vault alerting. This change has reduced the number of parameters in the initiative. To update this initiative you will need to:

1. Update your local copy of the repo
2. Remove the initiative assignment for the Management initiative
3. Update the management initiative to the current version
4. Reassign the management initiative

New Contributors

• @amillerb made their first contribution in #187

Full Changelog: v.0.5.0...v.0.6.0

v.0.5.0

What's Changed

• Update telemetry guidance by @jfaurskov in #171
• Fix telemetry doc by @jfaurskov in #172
• Alleviating Parameter confusion by @pkorolo in #167
• VM Insights Scheduled Query alerts by @Alboroni in #142
• PR for fixing relative link errors caused from PR167 by @pkorolo in #176
• Server Health Initiative Metadata deployed_by_alz_monitor by @arjenhuitema in #180
• Recovery services vault alerts by @arjenhuitema in #177
• Deploy individual initiatives guidance by @arjenhuitema in #179
• Updated links to point to working ver guidance by @paulgrimley in #185
• Update README.MD to include Feedback section. by @bzabber in #188

New Contributors

• @pkorolo made their first contribution in #167

Full Changelog: v.0.4.0...v.0.5.0

v.0.4.0

What's Changed

• Convert deploy GH actions to ADO pipelines by @jfaurskov in #157
• Improve remediation experience by @jfaurskov in #165
• Fix Service Health notification by @jfaurskov in #168

Breaking Changes

The following policies had the ALZMonitorActionGroupEmail parameter added:

• [DINE] Deploy Service Health Advisory Alert
• [DINE] Deploy Service Health Incident Alert
• [DINE] Deploy Service Health Maintenance Alert
• [DINE] Deploy Service Health Security Advisory Alert
  If the policies were assigned as recommended through the Service Health policy initiative, policies and initiative can be imported from the new source with no issues. If the policies were assigned individually though, you will have to remove the assignments before the policies can be updated.

Full Changelog: v0.3.0...v.0.4.0

v0.3.0

Bugs/hotfixes

We were made aware that the alert processing rule link to the action group was not correctly deployed. We have therefore fixed this. If you already deployed the alert processing rules and action groups, which are deployed as part of the service health initiative, you should update the policy with the latest changes. This will not, unfortunately change the already deployed alert processing rules, so you will need to change those manually or delete them and re-remediate. Any new subscriptions added to the management group hierarchy will receive the correctly configured alert processing rules. For more details on the exact change to policy please refer to #163.

What's Changed

• Update graphics by @jfaurskov in #145
• Updated Link to Deployment Guide in Alert Details by @bzabber in #146
• Update convert bicep to arm by @arjenhuitema in #148
• fix name secrets app private key by @arjenhuitema in #149
• event trigger changed to push by @arjenhuitema in #152
• Minor updates by @jfaurskov in #155
• fix powershell deployment by @arjenhuitema in #158
• Split out Baseline deployment guide by @arjenhuitema in #160
• Provided a note above tables due for scrolling by @paulgrimley in #161
• Fix alert processing rule defect link to action group by @jfaurskov in #163

Full Changelog: v0.2.0...v0.3.0

v0.2.0

What's Changed

• Update with service health initiative by @jfaurskov in #141

Breaking changes

• Removed service health parameters from connectivity initiative.
• Removed service health parameters from managment initiative.
• Removed service health parameters from identity initiative.
• Removed service health parameters from landing zone initiative

Full Changelog: v0.1.1...v0.2.0

v0.1.1

Initial release