Idle resources
Unattached disks, public IPs and network cards, empty App Service plans, old snapshots, stopped-but-billed VMs, load balancers or gateways with nothing behind them, and private endpoints that lead nowhere or duplicate each other.
For Azure teams without a FinOps department
SistaGuard reviews your Azure subscriptions with read-only access. It finds idle resources, oversized VMs, missed licence savings and backup gaps, and calculates each saving from your real costs. AI explains the findings in plain language. It never invents the numbers.
Top actions
How it works
Sign in with Microsoft and give SistaGuard the Reader role on the subscriptions you choose. It can look, never change. Then prove each subscription is yours: add a sistaguard-verify tag with the code SistaGuard shows you and choose Verify access. You can remove the tag afterwards.
Run your first scan with one click. Every resource is checked against fixed rules, using 30 days of usage, your actual costs and Azure Advisor's findings. After that, scans run on a schedule.
Get one prioritised list with calculated savings and a clear next step for each item. Mark items as in progress or resolved as your team works through them.
What it checks
Unattached disks, public IPs and network cards, empty App Service plans, old snapshots, stopped-but-billed VMs, load balancers or gateways with nothing behind them, and private endpoints that lead nowhere or duplicate each other.
30 days of CPU and memory usage per VM. Idle machines and oversized ones get a concrete smaller size, priced from Azure's public price list.
Windows VMs, scale sets and SQL workloads that could use the Azure Hybrid Benefit licences you may already own.
Failed or outdated backups, paused protection and VMs with no backup at all. Geo-redundant vaults you may not need.
Too many or too few subscription owners, over-privileged service principals, wildcard custom roles, open Key Vaults, and secrets, keys or certificates about to expire.
This month's spend so far, Azure's month-end forecast against your budgets, and days when a service cost far more than usual.
Beyond Azure's own tools
Azure's tools are good, and SistaGuard works alongside them. Each one answers a different question and expects someone with the time and expertise to put the answers together. SistaGuard does that for you.
General best-practice recommendations, with savings estimated from list prices.
SistaGuard imports Advisor's cost recommendations into the same list and marks where both agree. It adds its own checks, such as backup retention against your limits and gateways with nothing behind them, and calculates savings from what each resource actually cost you.
Shows what you spend, forecasts the month and tracks budgets.
It tells you how much. SistaGuard tells you which resources to fix and what each fix is worth, and shows the forecast, your budgets and unusual cost days next to those fixes.
A full security posture and threat protection product.
SistaGuard doesn't replace it. It adds a few access and governance checks that often fall between teams, such as subscription owners, over-privileged service principals and expiring Key Vault items, and puts them in the same list as your costs.
Enforces rules that you write and maintain.
Policy needs someone to decide the rules, write them and keep them current. SistaGuard tells you which basic policies are missing, which resources break the ones you have, and which exceptions never end. Its checks work from the first scan with no setup, and only report. They never block or change anything.
Numbers you can defend
Every finding comes from a fixed, testable rule, and every saving shows how it was calculated. When there isn't enough data to put a number on it, SistaGuard says so instead of guessing.
Security
You sign in with Microsoft Entra ID and give SistaGuard the built-in Reader role on the subscriptions you choose, and only those. Reader can list and read. It cannot create, change, start, stop or delete anything. SistaGuard reaches Azure through a federated identity, so there is no password or client secret to leak.
Before the first scan, you add a sistaguard-verify tag with a one-time code to the subscription. Only someone who can change the subscription can add it, so nobody else can connect your subscription by typing its ID.
In Microsoft Azure, West Europe region. The database sits on a private network with no public access and is encrypted with a customer-managed key. The plain-language explanations are written by Anthropic's Claude, which receives resource names, types, sizes and the facts behind a finding, never tags, IP addresses or secret values.
After step 1, SistaGuard can no longer read your subscription, usually within minutes. You don't need to ask us first.
Pricing
Plans differ only in how much you connect and how often it's checked. Start with a 14-day free trial, no card needed.
Prices exclude VAT. Run a scan by hand at any time on every plan. More than 50 subscriptions? Email support@sistaguard.com.
FAQ
No. It only has the Reader role, which can't create, change, start, stop or delete resources. Every fix is yours to make.
SistaGuard includes Advisor's cost recommendations, adds its own checks for backups, idle networking and licensing, and calculates savings from your actual costs instead of list prices. Everything appears in one prioritised list.
In Azure West Europe, in an encrypted database on a private network. Only the people you invite to your organisation can see it in SistaGuard.
It turns a finding into a plain-language explanation. It receives resource names, types, sizes and the facts behind the finding, never tags, IP addresses or secret values. It doesn't decide what's wrong or how much you save. Fixed rules do that.
Usually a few minutes for a typical subscription.
Scan history and findings for 12 months, daily cost data for 13 months, the history of resource changes (created, modified, deleted) for 13 months, records of resources deleted in Azure for 13 months, the audit log for 2 years, and team invitations for 30 days after they are used or expire; the newest scan of each subscription is always kept. If a trial or subscription ends, everything is deleted 90 days later. An admin can delete it all at once at any time, and backups are overwritten within 7 days.
Remove SistaGuard's Reader role from the subscription and delete the SistaGuard enterprise application in Entra ID. Then delete your data in Billing → Delete organization, or email us. See "How to revoke access" above.
Connect with read-only access and get your first results in minutes.
Run your first scan