Azure Advisor Recommendation Suppressions with Bicep and PowerShell - Series

• Intro
• Series navigation
• Reference links

Intro

In this series I show how to work with Azure Advisor recommendation suppressions by using the Microsoft.Advisor/recommendations/suppressions resource type, Bicep, and PowerShell/az CLI.

Suppressions let you “snooze” or “dismiss” an Advisor recommendation for a resource, resource group, or subscription for a period of time - useful when a recommendation is a known false positive, or when the recommended action is intentionally deferred (for example accepted business risk, or a planned change later in the quarter).

This series walks through the practical patterns I use to make this manageable from a pipeline: how to inventory current suppressions, how to create and update them with Bicep, how to remove them, and the limitations you need to design around.

Series navigation

Read the articles in this order:

1. Part 1 - Known limitations
2. Part 2 - Get current Advisor suppressions and export to Markdown
3. Part 3 - Create a suppression with Bicep
4. Part 4 - Update a suppression with Bicep
5. Part 5 - Delete a suppression

Reference links

• ARM/Bicep reference: Microsoft.Advisor/recommendations/suppressions
• REST API list operation: Suppressions - List
• REST API create operation: Suppressions - Create
• REST API delete operation: Suppressions - Delete
• REST API recommendations list operation: Recommendations - List
• Azure Advisor permissions
• Get started with Azure Advisor

Final remark: this series uses the 2023-01-01 Advisor API version throughout - a stable, generally available (non-preview) version, though not the newest one; 2025-01-01 is also GA and, per the change log, carries no schema changes over 2023-01-01. Check the change log before pinning to a different version (GA or preview) in your own pipeline.