Build Advisor alert configs with category-based alert rules, weekly digest emails, recommendation suppressions, and thresholds.
Build Advisor alert configs with category-based alert rules, weekly digest emails, recommendation suppressions, and threshold settings.
Required Fields
configurationNamescopealertRulesalertRules[0].namealertRules[0].categoryalertRules[0].enabledOutput will appear here...Build Azure Advisor alert configuration routing new recommendations by category (HighAvailability, Security, Cost, Performance) and impactLevel to different action groups, plus a weekly digestConfiguration email and time-bound suppressions for known, accepted exceptions. A suppression's ttl (P90D in the example) is a real expiration, not a permanent dismissal, once the TTL elapses, the recommendation resumes surfacing normally (including triggering any matching alertRules again), which is deliberate, a suppression justified today (a dev VM intentionally oversized for load testing) may no longer be a valid reason in 90 days, and the TTL forces a periodic re-justification rather than a suppression silently hiding a recommendation forever.
No, ttl (like P90D, 90 days) is a real expiration, once it elapses, the suppression lapses and the recommendation resumes normal visibility and alerting for that resource. This is deliberate, forcing periodic re-justification of an exception rather than letting a suppression become permanent, unreviewed, and eventually forgotten as the reason it was originally granted.
impactLevel on an alertRule filters which severity of new recommendations trigger a notification for that category (only alerting on High/Medium, for instance, not Low), it's a broad, ongoing filter across all resources. A suppression is a specific, targeted, time-bound exception for one particular recommendationId on one particular resourceId, they operate at different scopes and for different purposes, one about alert noise reduction generally, the other about a specific accepted exception.
It's generally intended to scope which resources Advisor generates and surfaces recommendations for going forward, existing recommendations already generated for excluded resource groups may persist until Advisor's next evaluation cycle recalculates recommendations under the updated configuration scope, don't expect instantaneous retroactive disappearance of already-existing recommendations the moment the exclusion is configured.
The builder validates that configurationName, scope, alertRules, and the first alert rule's name/category/enabled all resolve before accepting the JSON as a valid combined Advisor alerting, digest, and suppression configuration; it can't verify the referenced action group IDs exist or that specific recommendationId/resourceId pairs in suppressions are currently valid, active recommendations, those are only confirmed against the live Advisor API.
Treat every suppression's ttl as a genuine forcing function for re-review, don't set an unnecessarily long TTL just to avoid the interruption of periodic re-justification, a shorter TTL matched to how long the underlying justification is actually expected to remain valid keeps suppressions honest.
Route different recommendation categories to the team actually responsible for acting on them, a single shared action group receiving every category regardless of relevance dilutes signal and increases the odds a genuinely actionable recommendation for the right team gets lost in noise meant for someone else.
Use wildcard-based excludeResourceGroups patterns for entire classes of non-production infrastructure rather than suppressing recommendations one-by-one across many similar sandbox resource groups, it's both less maintenance and clearer about the actual governance intent.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.