How to detect and reclaim idle Microsoft 365 licenses. Every month, organizations quietly pay for Microsoft 365 licenses no one's using. Disabled accounts, departed employees, and forgotten add-ons all add up. The good news is that reclaiming those licenses isn't complicated. We'll show you how to do it in this video. Before we begin, be sure to subscribe to NinjaOne's IT Video Hub and our YouTube channel for more tech content like this. Prerequisites to reclaiming idle Microsoft 365 licenses. First, let's talk about what you need to have ready. Admin consent for Microsoft Graph API and a service principle scoped to license operations, access to Microsoft 365 usage reports and sign-in activity, a documented off-boarding process with handoffs to HR or ITS, role-based access that separates build, review, and approval steps, a shared repository for scripts, runbooks, and the license cleanup register. Once all these prerequisites are met, you can begin reclaiming unused Microsoft 365 licenses across your environment, starting with defining inactivity. How to detect and reclaim idle Microsoft 365 licenses. Step one, define what inactive actually means. Before you touch a license, define what inactive means for your organization, whether it's 30 days without a sign-in or 60 days. Set those thresholds by role. Standard users might have a 30-day window. Contractors might only receive seven. Then identify your protected categories, such as executives, legal hold users, or service accounts, and decide in advance what action to take for each scenario: a full license removal, an SKU downgrade, or a move to a review group. Step two, find the idle licenses with data. Next, head into the Microsoft 365 admin center and look at the facts. Sign-in activity, last interactive sign-ins, workload usage across Exchange, SharePoint, Teams, and OneDrive. You're basically looking for disabled or blocked users who still have active licenses. When you find them, flag them. Then export a CSV with the following information: user, SKU, last activity date, any exceptions, your proposed action. Step three, automate removals and downgrades. Once you know who's inactive, it's time to act. Use Microsoft Graph and PowerShell to remove or downgrade licenses with pre-checks built in. Always run a dry run first and sequence your operations thoughtfully by downgrading first when retention is required and fully removing licenses only when appropriate. More importantly, log everything: the timestamp, the operator, the reason code, and the SKUs before and after the change. And apply a short grace window for possible reversals. Step four, restructure to group-based licensing. To stop sprawl from returning, shift from per-user assignments to group-based licensing in Microsoft Entra ID. Additionally, sync group membership with your HRIS or ITSM workflows so that whenever staff changes happen, licenses follow the role automatically. Step five, tie license management to off-boarding and role changes. Next, add a license removal step to every off-boarding checklist. When someone changes roles, move them between licensing groups so entitlements follow the job, not the person. Track each completed off-boarding in a register so you always have a clear, auditable record of license changes and approvals. Step six, prove the savings and pass the audits. Finally, maintain a license cleanup register listing the following information: reclaimed seats, downgraded SKUs, approvals, dollars saved. Publish a monthly scorecard for each client or business unit and keep your runbooks, scripts, logs, and evidence folders ready for any audit that comes your way. Overall, when you make license reclamation a monthly discipline, defining inactivity, detecting waste, automating removals, and anchoring it all to off-boarding, license sprawl stops being a surprise cost and starts operating as a controlled, measurable process. For more information, check out our official blog post on detecting and reclaiming idle Microsoft 365 licenses, linked in the description below. Be sure to subscribe to NinjaOne's IT Video Hub and our YouTube channel for more tech content like this.