License
AnomalyGuard is licensed by how many data views you define — not by how many people use the product.
What the license limits (and what it does not)
| Licensed | Not licensed |
|---|---|
| Number of data views you can create | Number of users / seats / named accounts |
| How many people open Home, filters, API, or CLI | |
| How many filters, comments, or API keys you create |
Everyone in the company can use the analyzed data without a per-user license fee. After you sign people in with Microsoft Entra ID and assign them data-view access, the whole organization can consume anomalies on Home, through shared filters, or via API / CLI — under the same Marketplace plan.
You grow the plan when you need more monitoring definitions (more data views), not when more colleagues start reading results.
Plans
Plans come from Azure Marketplace. Each tier sets a maximum number of data views:
| Plan | Max data views |
|---|---|
| Start | 1 |
| Small Team | 5 |
| Growing Team | 20 |
| Enterprise Team | Unlimited |
The limit counts all data views in the system — including drafts that are not yet deployed or enabled. Deleting unused views frees capacity on a limited plan.
The plan is chosen at Marketplace deployment. The data-view cap is not a setting you edit later inside the app (upgrade by changing Marketplace plan / offer).
What “data view” means here
A data view is one monitoring configuration: source query, categories, detectors, and jobs. Example: sales by country and channel is one data view; hotel revenue by region is another. Each consumes one slot toward the plan limit.
Users, filters, and Home screens do not consume license slots.
Enforcement
| Action | License effect |
|---|---|
| Create a new data view | Blocked when you are already at the plan maximum |
| Enable an existing data view | Allowed (not a license gate) |
| Save / update an existing data view | Allowed (not a license gate) |
| Load / process jobs | May show a warning if the current count is somehow above the plan (for example after a plan change); data is not deleted |
If the limit is reached, free a slot by removing a data view you no longer need, or move to a higher Marketplace plan.
Where to see usage
On the Data views list, administrators see a counter when a limit applies, for example 3 from 5.
Check the same information from the CLI or API:
anomalyguard system license --json
| Field | Meaning |
|---|---|
maxActiveDataViews |
Plan maximum (null = unlimited) |
usage.dataViews |
Current total data view count |
usage.activeDataViews |
Same total count (all views) |
Related
- How to start — first rollout path
- Install AnomalyGuard — deployment
- Data Views — create, deploy, enable
- Users — assign access (no seat license)