Alert Suppression (Muting)
Not every finding requires action. Some are accepted risks, known exceptions, or not applicable to your environment. Amnify’s muting feature lets you suppress these findings so they don’t inflate your failure counts or clutter your views.
Muting levels
You can mute a finding at three different levels of granularity:
| Level | Scope | Example |
|---|
| Tenant | Entire cloud account/tenant | Mute “storage encryption with CMK” across all Azure subscriptions |
| Subscription | Specific subscription or project | Mute it only in the development subscription |
| Resource | Individual resource | Mute it only for one specific storage account |
Start with the narrowest scope that makes sense. Muting at the resource level keeps your visibility high while suppressing the specific exception.
How to mute a finding
- Navigate to the Findings page
- Click a finding to open its details
- Click “Mute”
- Select the muting level (tenant, subscription, or resource)
- The finding is immediately suppressed
Muted findings are excluded from:
- The Findings table
- The Security Posture dashboard metrics
- Compliance pass/fail calculations
- PDF exports
Managing muted items
The Mute List page (accessible from the sidebar) shows all currently muted items:
- What was muted (check name)
- At which level (tenant, subscription, or resource)
- Who muted it
- When it was muted
You can unmute any item to restore it to active findings.
Best practices
- Document your rationale — Make sure your team knows why something was muted
- Review regularly — Periodically check the mute list to ensure suppressed findings are still valid exceptions
- Use the narrowest scope — Prefer resource-level muting over tenant-level to maintain visibility
