TrueState
TrueState goes beyond a one-time scan. It locks your secure configuration once as a baseline, then watches every change in your environment and catches drift on its own.
Two stages
First you turn on monitoring. At this stage your configuration is visible but not yet protected. Then you lock TrueState. The configuration you approved is frozen as the baseline. From that point every addition, removal or change is reported with its before and after.
Without a baseline, no workload shows as "Protected". As long as you have not locked it, the state is shown honestly as "Monitored".
What it watches
Conditional Access policies, privileged roles, device and app settings, sensitivity labels, Defender configuration and more. Every drift is written to a permanent record with a Ticket ID, and an email goes to the alert recipients.
Monitoring frequency
Monitoring runs continuously, but not every check shares the same rhythm. Deviations from your locked baseline are checked hourly, and an alert goes out without delay when a change is caught. The full scan of all 233 controls refreshes every four hours. This interval balances the load on Microsoft Graph and keeps the control results you see in the dashboard at most four hours old. Critical VIP identity events (a new admin assignment, a change to an MFA method) are watched separately in near real time, roughly every 15 minutes.
Living configuration and the "Flexible" exception
Some fields change by design. An automation might add a user to a Conditional Access exclusion list, for example. So that this does not raise a constant false alarm, you can mark that policy's exclusion list as "Flexible". Only that inner field drops out of monitoring; the rest of the policy stays watched.
Cross-tenant (partner) role assignments
A reseller, distributor or partner can hold an admin role in your tenant through a group that lives in their own tenant; that is how Microsoft's delegated administration works, and how licence assignment and support tickets are handled. This is not a deviation: nothing has moved outside your approved configuration — it is a normal operating fact of your tenant.
Controlio therefore does not treat partner access as a TrueState deviation. It appears in its own Partner delegated access card on the TrueState page: which partner tenant, which roles, and when the access was first and last seen. Highly privileged roles (Global Administrator, for example) are marked separately.
We state the limit of the measurement plainly: because the principal behind such an assignment is not in your directory, Microsoft Graph does not list it reliably — Microsoft itself says a customer cannot find these assignments through the Entra admin center, PowerShell or Graph. Controlio reports what it observed and never claims absence; an empty card does not mean there is no partner access. The authoritative list is Microsoft 365 admin center → Settings → Partner relationships.
A notification is sent only on a material change: once, when a new partner tenant is seen or a new role is added for a known partner. Access becoming invisible produces no notification.
How a deviation closes
There are three ways to close an open deviation:
- Revert. If you undo the change on the Microsoft 365 side, the deviation closes on its own at the next hourly check; no action is needed in the panel.
- Accept into baseline. If the change is one you intended, you make the item's current state the new baseline. Monitoring continues; the next change to that item raises a deviation again. Needs dual approval.
- Exception. You take the item (or a single field, with "Flexible") out of monitoring. No alarm is raised for that item any more. Needs dual approval; the exception can later be removed, again with dual approval.
"Accept into baseline" freezes the item's current live state as the new reference, and the second approver sees and approves that same state. A deleted item has no live state left to approve, so the panel offers "Accept removal" instead: with dual approval the item is dropped from the baseline, monitoring continues, and if the item ever comes back it is caught as an "added" deviation. If the item has returned while the request was pending, the approval is refused by design; the open deviation clears on its own at the next hourly check. The exception path remains available, but choose it knowingly: an excepted item raises no alarm even if it returns. A re-lock is always the third path and folds every open deviation at that moment into the new baseline.
Dual control
Any change to the secure baseline needs approval from at least two administrators, and one of them must be a Global Administrator. A drift cannot be quietly folded into the baseline, and every change stays auditable.
Trend: your posture over time
TrueState shows not only your current state but how your security posture moves over time. The "Trend" tab charts your overall security score across months in a single view, answering the question "where were you six months ago, and where are you today?".
You can pick two dates and compare what changed between them: which controls improved and which regressed. Alongside the chart are summary indicators for open drift, VIP deviations and baseline status. For the detail behind each change (who, when, before and after) you drill into the Security Movements records.
The trend is derived from daily posture snapshots kept server-side. These accumulate in the background even when you do not open the app; they hold only counts and status, never user or VIP identity. That keeps them privacy-safe and suitable for long retention. History starts accumulating from the moment you turn on monitoring.