TOP STORIES PRACTICAL GUIDE · CHECKED 15 NOVEMBER 2026

Entra Tenant Governance.....
what does the allowance actually cover?

A guide for customers, First Technology Group (FTG) account managers and implementation teams. Count the configuration items, the repeated checks and the snapshot frequency..... then count the licences.

Worked examples · Capacity calculator · Customer explanation

The missing multiply by four!

The base daily allowance does not mean 800 different policies under continuous monitoring. Microsoft’s technical reference counts a resource again on each six-hour run. There are four runs in a full day. A baseline containing 200 items therefore uses 800 daily resource checks.

“Resource checks” is the explanatory term used in this guide. Microsoft’s licensing table calls the allowance “configuration resources per tenant per day”. The worked examples below apply the technical counting rule to the licence uplifts. Read Microsoft’s counting example ↗

1. What is a resource?

A tenant is a separate Microsoft cloud environment. Start by identifying the tenant being assessed.

Here, a resource is a configuration item: for example, a Conditional Access policy or an Exchange mail-flow rule. A resource type describes the kind of item; an instance is one actual policy or rule. A single item can have many settings. This is not a count of employees, messages, files, gigabytes or every setting within a policy.

A baseline records the approved settings. A monitor compares the selected items against that baseline. A snapshot extracts their current configuration. Keep an owner responsible for deciding whether a reported difference is expected and arranging the fix. Microsoft’s configuration definitions ↗

2. Two separate counters

What each allowance measures
CounterHow to size itBase allowance per eligible tenant
MonitoringAdd the items in all monitor baselines, then multiply by four daily runs.800 resource checks daily
SnapshotsAdd all resource instances extracted in every snapshot during the month.20,000 extracted resource instances monthly

Repeated snapshots consume the monthly allowance again. Capturing 1,000 items once uses 1,000; capturing them on each of 30 days uses 30,000. Monitoring and snapshots are separate operations with separate budgets. Changing snapshot frequency does not change the monitor’s schedule. Microsoft’s monitoring and snapshot limits ↗

For initial sizing, count items each time they appear in a monitor. Do not assume that overlapping baselines are deduplicated. Have the implementation team confirm overlap handling and the actual tenant quota before quoting.

3. What E3, E5 and E7 change

Microsoft 365 E3 includes Entra ID P1; E5 includes P2. Both provide the base Tenant Governance capacity. Buying more E3 or E5 seats does not multiply the base allowance.

E7 includes Entra Suite and its ID Governance entitlement. Qualifying ID Governance, Entra Suite or E7 licences add capacity in that tenant: 10 daily monitoring checks and 35 monthly snapshot resource instances per licence. The extra allowance is pooled; it is not another complete base allowance for each person. Microsoft’s capacity uplifts ↗

First establish which administrators need premium features, such as related-tenant discovery. Then include their qualifying licences in the capacity calculation. A small number of licensed administrators does not establish unlimited monitoring capacity. Conversely, existing eligible seats may already cover the requirement. Feature and administrator licensing ↗

Use a verified count of qualifying seats in the tenant being sized. Do not count E7 and its included Entra Suite and ID Governance components as three separate seats. Confirm assignment requirements, overlapping subscriptions and cross-tenant capacity allocation with Microsoft or the licensing supplier; the published pages do not explain all of those edge cases.

4. Worked examples..... same rules, very different results

Monitoring only, assuming four runs daily and no overlap
Items in the baselinesDaily checksQualifying premium capacity licences needed in total
200200 × 4 = 8000 extra for capacity: the eligible base allowance covers this scope
250250 × 4 = 1,000(1,000 − 800) ÷ 10 = 20
1,0001,000 × 4 = 4,000(4,000 − 800) ÷ 10 = 320

These are planning calculations, not quotations. The final column is the total capacity entitlement required, before subtracting qualifying seats already held. Feature access and administrator coverage still need checking.

A customer already has 100 qualifying E7 seats

Current daily capacity is 800 + (100 × 10) = 1,800 checks. At four checks per item, that supports 450 items in non-overlapping baselines.

Suppose the customer wants to monitor 1,000 items and snapshot those same 1,000 items daily for a 30-day month:

  • Monitoring needs 4,000 daily checks: 320 qualifying licences in total.
  • Snapshots need 30,000 monthly resource instances. The 10,000 above the base allowance requires 10,000 ÷ 35, rounded up: 286 qualifying licences in total.
  • Each qualifying licence increases both allowances. Use the larger requirement, 320..... do not add 320 and 286.
  • Subtract the 100 existing qualifying seats: the indicative gap is 220 additional qualifying capacity licences.

There is no automatic requirement to upgrade all employees to E7. Assess the appropriate qualifying add-on or suite against the customer’s current entitlements and quoted terms.

TRY THE NUMBERS

Capacity calculator

The monitoring schedule is fixed at four runs per full day in this model. Count the items across all monitor baselines. Enter the existing premium-seat count after it has been verified.

1,000 checks required; current allowance 800. Shortfall: 200.

1,000 resource instances required; current allowance 20,000. Within allowance.

20Indicative additional qualifying capacity licences

Capacity needs 20 qualifying licences in total. Subtract 0 existing: 20 additional.

Planning estimate using the published six-hour counting example and licence uplifts. Administrator eligibility, feature access, seat assignment and actual tenant enforcement require separate validation.

5. The calculation to keep with the proposal

  1. Daily requirement: sum of items across monitor baselines × 4.
  2. Monthly snapshot requirement: sum the resource instances in every planned snapshot. For equal-sized snapshots, items per snapshot × snapshots per month.
  3. Premium licences for monitoring: round up (daily requirement − 800) ÷ 10; use zero when the requirement fits the base allowance.
  4. Premium licences for snapshots: round up (monthly requirement − 20,000) ÷ 35; use zero when the requirement fits the base allowance.
  5. Capacity licences required: take the larger of those two results. Subtract existing verified qualifying seats; do not go below zero.

Run the calculation separately for each tenant. Use the actual number of snapshots planned for that month, including any additional audit or troubleshooting extracts. Keep enough headroom for agreed growth.

6. Capacity consumption..... not a published price per check

The current guidance describes licence-based capacity and quota restrictions. It does not publish a pay-as-you-go overage rate for these resource checks. Microsoft says a monitor that would exceed quota cannot be created, and new snapshots cannot be created after the monthly allowance is exceeded. Monitor creation ↗ · Snapshot creation ↗

There are also separate service restrictions, including the monitor count, retained snapshots and snapshot-job limits. Seven-day snapshot retention does not mean a fresh monthly allowance every seven days. Do not promise that deleting old extracts refunds capacity, or how failed and partial jobs are counted, without confirmation.

Agent 365 entitlements and chargeable agent workloads are separate questions. This calculator does not estimate Copilot Credit or agent-runtime costs.

7. What the FTG team needs before quoting

  • Inventory: the tenant, supported workloads, selected configuration items and resource count in each monitor.
  • Purpose: approved baseline, priority controls, who investigates drift and who makes authorised corrections.
  • Usage: repeated monitoring runs, overlapping baselines, snapshot scope and monthly frequency.
  • Entitlements: existing E3/E5/E7 and qualifying add-ons; which administrators use premium features; the tenant’s verified capacity.
  • Confirmation: licence assignment and overlap rules, cross-tenant allocation, quota enforcement, failed-job counting and any discrepancy between the licensing summary and technical reference.
  • Commercials: the incremental quantity, applicable customer pricing, implementation and ongoing reviews. Do not turn an illustrative licence count into a binding quote without validating the assumptions.

A plain-English explanation for the customer

Think of two counters. One counts the repeated checks on your approved configuration; the other counts the items copied into configuration snapshots. Two hundred items checked four times a day uses the base 800 daily checks. Existing qualifying licences can add capacity. FTG’s team needs to measure the scope, check what you already own and calculate any shortfall before recommending more licences.

Count the work before counting the licences..... and count the work four times if Microsoft checks it four times!

Sources

Microsoft documentation checked on 15 November 2026. The licensing summary does not explain repeat-run counting; the stable Microsoft Graph reference does. The scenarios and calculator apply that technical example to the published capacity uplifts and must be validated against the customer’s actual tenant.

  1. Tenant Governance licensing: features, administrator requirements and capacity examples ↗
  2. Microsoft Graph stable reference: four monitoring cycles and cumulative snapshot counting ↗
  3. Configuration management: resources, baselines, monitors and snapshots ↗
  4. Service limits: licence uplifts and operational restrictions ↗
  5. Create a monitor: capacity prerequisites ↗
  6. Create snapshots: monthly quota and included-resource counts ↗
  7. Entra licensing: E3, E5, E7 and suite entitlements ↗