Auto Adjust is a sync control that automatically updates tracked license quantity to match what the connected integration reports from the vendor side. It protects against stale counts when seats are added or removed outside the internal system. When disabled, quantity changes require manual correction to remain accurate.
What Auto Adjust Does in a License Sync Workflow
Auto Adjust keeps the tracked license count aligned with what the connected vendor integration reports, so the internal record reflects additions and removals that happen outside the local system. In practice, it turns license quantity into a synchronized field rather than a manually curated one, which matters when seats move frequently or when multiple administration paths can change entitlement counts.
The control is only as accurate as the integration feed it trusts. If the connected system is delayed, incomplete, or disconnected, Auto Adjust can preserve consistency with the wrong source of truth for a period of time, so teams still need to understand which system owns the authoritative quantity at any given moment.
Why Auto Adjust Exists
Without automatic quantity reconciliation, license data can drift from reality when users are added, removed, or reassigned outside the internal workflow. That drift creates wasted spend, false shortages, and avoidable administrative cleanup. Auto Adjust exists to reduce that manual correction burden by continuously matching recorded quantity to the vendor-reported count.
This matters most in environments where licensing is event-driven and shared across procurement, IT, and SaaS administration. If one team updates access while another team tracks consumption, a manual-only process can leave the organisation believing it has more or fewer seats than it actually does.
Where Auto Adjust Can Be Useful
Auto Adjust is most useful when the vendor integration is dependable and the organisation wants the tracked quantity to follow real usage as closely as possible. It supports operational accuracy for renewals, true-ups, and internal chargeback or allocation models that depend on current seat counts.
It also helps when license changes happen often enough that manual review would lag behind the business. In that situation, the feature reduces administrative friction and helps prevent stale counts from becoming the default state of the record.
What Auto Adjust Does Not Solve
Auto Adjust is a synchronization control, not a governance substitute. It does not decide whether a license should exist, whether a user is properly approved, or whether the vendor integration is trustworthy. It simply updates the tracked quantity to reflect the reported count.
That means organisations still need a way to validate the integration source, review unusual quantity changes, and investigate discrepancies when the reported count looks implausible. If those checks are absent, automation can make inaccurate data update faster rather than making it correct.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, NIST SP 800-53 Rev 5, CIS Controls v8 and CSA Cloud Controls Matrix set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | ID.AM-02 — Software, hardware, data, and external services are inventoried | Auto Adjust depends on keeping license inventory aligned with vendor-reported quantities. |
| Recommendation — Maintain an accurate license inventory and reconcile it with vendor-reported counts. | ||
| NIST SP 800-53 Rev 5 | CM-8 — System Component Inventory | Tracked licenses are an inventory-control problem because counts must stay current and attributable. |
| Recommendation — Keep an authoritative inventory of licensed assets and reconcile it to external reports. | ||
| ISO/IEC 27001:2022 | A.5.9 — Inventory of information and other associated assets | License quantities are an asset-management record that needs controlled reconciliation. |
| Recommendation — Define ownership for license records and reconcile them when external counts change. | ||
| CIS Controls v8 | CIS-1 — Inventory and Control of Enterprise Assets | Auto Adjust supports asset-count accuracy by reducing stale license records. |
| Recommendation — Use inventory control to keep license counts current and remove stale records. | ||
| CSA Cloud Controls Matrix | IAM — Identity & Access Management | License tracking is part of access governance when seat counts map to entitlement use. |
| Recommendation — Align license counts with entitlement governance and review mismatches promptly. | ||
Practitioner Guidance
Governance implication: Treat Auto Adjust as an accuracy mechanism with an ownership question attached, not as a business-policy decision. The team responsible for licensing, procurement, or SaaS operations should know which system is authoritative and when manual intervention is required.
What to watch for: Pay attention to abrupt quantity swings, repeated mismatches, or integrations that stop reporting cleanly. Those are the moments when a synced count may no longer reflect the real operational state and should be reviewed before renewals, audits, or provisioning decisions depend on it.
Practitioner takeaway: Enable Auto Adjust when the integration is trusted and the business wants low-friction count hygiene, but keep a review path for exceptions so automation does not hide bad input data.
Related resources from NHI Mgmt Group
- How does OneDrive auto-sync create secrets exposure in SharePoint?
- How should organisations stop auto-sync from turning desktops into repositories of credentials?
- Should security teams disable OneDrive auto-sync by default?
- What breaks when remote images are auto-fetched inside AI assistant responses?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org