- DATE:
- AUTHOR:
- The folks at Scrut
Choose which Azure Subscriptions to connect with Scrut
What's new?
You can now customize the scope of your Azure integration by selecting exactly which subscriptions should be monitored in Scrut, giving you finer control over what's tracked, tested, and shown.
Why it matters
This enhancement helps:
Minimize noise: Keep out irrelevant or sensitive environments
Precise mapping: Improve test coverage and audit accuracy
Cleaner reporting: All downstream modules, like asset management, risk-linked assets, and evidence tasks, now reflect only scoped subscriptions.
How it works
When connecting a new Azure tenant (or editing an existing one), you can now:
Choose which subscriptions to bring into scope.
Add nicknames to identify environments like “production” or “staging”.
Update the scope anytime from the same configuration screen. This ensures that only relevant Azure resources show up in your dashboards, tests, asset inventory, and evidence tasks.
Following this enhancement, you must reconfigure your Azure integration to select the scope. Refer to this guide for detailed step-by-step instructions.
Note
Changes to the integration scope are reflected in near real-time.
Removing a subscription from scope will hide related resources and cancel scheduled scans.
Re-adding a subscription brings it in as new (fresh discovery).
All changes are audit-logged for traceability.
Need help?
Your Customer Success Manager (CSM) is always ready to help if you need assistance. Explore all recent product updates → View now.