/

ConversIA

Microsoft 365 Audit: Optimizing Licenses and Access

How to properly make an auditing on Microsoft 365

7

Microsoft 365 Audit

IN THIS ARTICLE

Section

Share

How can you identify underused Microsoft 365 licenses (formerly Office 365)? By cross-checking three data points
already available in your environment: the licenses you pay for versus those assigned, each user’s activity by
application, and their last sign-in date. Comparing these data points reveals unassigned licenses, licenses
assigned to people who have left the company, and plans that exceed a role’s actual needs.
The same review can uncover something more important than cost savings: former employees’ accounts that
remain active, external guests with access to internal documents, or administrators without multifactor
authentication. A Microsoft 365 audit is therefore not just about optimizing licenses and costs; it is also about
reducing security risks.
This guide explains what to review, where to find each data point, and how to prioritize your findings, with a
checklist you can apply across your organization

What a Microsoft 365 Audit Is (and Is Not)

A Microsoft 365 audit is a structured review of your environment: which licenses the company has, who uses them,
which accounts exist, what permissions they have, and which security settings are enabled. The outcome is a list
of findings, owners, and recommended actions.
It is important not to confuse it with two other activities:

  • Searching the audit log. Microsoft Purview includes an audit log that records thousands of user and administrator
    actions (who opened a file, changed a permission, or accessed a mailbox). By default, Audit (Standard) logs are
    retained for 180 days. This tool is useful for investigating specific events, not for reviewing the overall state of the
    environment. The audit described here can use these logs, but it is not the same thing.

  • A security audit or penetration test. Reviewing Microsoft 365 settings can identify access risks, but it does not
    replace a comprehensive cybersecurity assessment of your infrastructure.

This is not about cutting tools for the sake of it. The goal is to ensure that every license meets a real business need
and every access permission has a valid reason.

1. License Inventory and Optimization

Start in the Microsoft 365 admin center under Billing > Licenses. For each subscription, you can see how many
licenses have been purchased, how many are assigned, and how many remain available. Use this information to
answer four questions:

  • Are you paying for unassigned licenses? These offer the most direct savings, although you should check
    whether they are reserved for upcoming hires.

  • Are licenses assigned to blocked accounts or former employees? This is a common finding when IT is not
    included in the employee offboarding process.

  • Does each plan match the role? A user who only needs email and Teams may not need the same plan as an
    analyst who works with all desktop applications.

  • Are shared mailboxes licensed? Shared mailboxes generally do not require a license, except in specific cases,
    such as exceeding 50 GB of storage or requiring archiving or litigation hold. Check each case against Microsoft’s
    current documentation before removing a license.

Also record renewal dates and the commitment type for each subscription. Many plan changes can only be made
at renewal, so it is best to audit well in advance.

2. Activity Analytics and App Usage Reports

An assigned license does not necessarily mean it is being used. To assess usage, go to the admin center’s
Reports > Usage section. These reports show user activity and adoption metrics over 7-, 30-, 90-, and 180-day
periods:

  • Active users: Activity by service, including Exchange, OneDrive, SharePoint, Teams, and Microsoft 365 Apps.

  • Microsoft 365 Apps usage: Which users work with desktop, web, or mobile applications.

  • Email, OneDrive, SharePoint, and Teams activity: Service-level usage details.

Interpret this data carefully. No activity over 90 days may indicate that a user no longer needs the license, but it
could also mean they are on leave, on vacation, or using another system for a valid reason. Reports also hide user
names by default for privacy, and updates can take 24 to 72 hours. Decide who is authorized to view identifiable
data before starting.

3. Account, Access, and Security Permission Controls

This is the part of the audit with the greatest security impact. Review at least the following areas:

Inactive accounts

Microsoft Entra ID (formerly Azure Active Directory or Azure AD) records each user’s last sign-in date. Microsoft
does not provide a dedicated “inactive accounts” report, so your organization must define and document its own
threshold (for example, 90 days without signing in). Retrieving this information through Microsoft Graph requires
Microsoft Entra ID P1 or P2 licenses. Before blocking an account, confirm with the department owner that the
person has left the company and that the account is not being used for another purpose.

Service and shared accounts

Accounts used by systems, printers, or integrations do not sign in like people do and may appear inactive. Identify
these accounts and assign an owner to each before making any changes.

Administrators

Count how many people have the Global Administrator role. Microsoft recommends keeping this number below five
and requiring multifactor authentication for all of them. Also review administrative roles assigned to personal
accounts used for day-to-day work.

Guests and external sharing

Review guest users and the SharePoint and OneDrive sharing settings. Public “Anyone” links to sensitive
documents and guest accounts from completed projects are common risks that often go unchecked.
Multifactor authentication (MFA)
Check which accounts have multifactor authentication enabled.

Microsoft 365 Audit Checklist

Use this table as a working template. Each row lists the data to review, its source, a potential finding, who should validate it, and the recommended action.

Data to review

Source

Potential Finding

Owner

Action

Purchased, assigned, and available licenses

Billing > Licenses 

Paid unassigned licenses

IT and Finance

Reassign or reduce upon renewal

Licenses on blocked accounts

Active users + account status 

Former employees with an active license

IT and HR 

Remove license and close the offboarding process

Plan by role

Microsoft 365 Apps usage report 

Plan higher than actual usage

IT and Department Head

Evaluate plan downgrade/change

Shared mailboxes

Exchange admin center

Mailboxes with unnecessary licenses

IT

Validate requirements and remove license 

Last login

Microsoft Entra ID

Accounts with no activity within the defined threshold

IT and Department Head

Confirm and block or delete

Service accounts

Entra ID + systems inventory

Accounts without a responsible owner

IT

Assign a responsible owner and document

Global administrators

Roles in the admin center

Too many administrators or lacking MFA

IT Manager

Reduce roles and enforce MFA

Guest users

Entra ID > Users

Guests from closed projects 

Project Owner

Review and delete

External sharing

SharePoint admin center

Open links in sensitive documents

Site Owner

Restrict links and permissions

Multi-factor authentication

Entra ID > Authentication methods

Accounts without MFA

IT

Enable MFA for all users

llustrative Example

This hypothetical example is for educational purposes and does not describe a real client.

A distribution company with several branches reviews its environment before renewing its licenses. The inventory reveals unassigned licenses purchased for an expansion that was delayed.

Cross-checking with Entra ID identifies accounts belonging to people who left the company months ago but still have licenses and access to customer folders. In SharePoint, the team finds open links to price lists shared with a supplier that no longer works with the company.

None of these findings required special tools. They only required comparing data that was already available.

How to Prioritize Findings

An audit often uncovers more issues than can be resolved in a week. Sort them into four levels:

  1. Immediate risk. Former employees with access, administrators without multifactor authentication, and sensitive documents shared through open links. Address these first, even if they do not generate savings.

  2. Quick savings. Unassigned licenses and licenses on blocked accounts. These are low-effort changes with a direct impact on the bill.

  3. Optimization. Plan changes by role. Validate the tools each department needs, review the cost of changes, and schedule them for the renewal date.

  4. Data and access governance. Define who reviews what and how often, and connect HR onboarding and offboarding processes with IT so the same findings do not recur.

This last point makes the difference in the long run. If employee onboarding and offboarding depend on someone remembering to notify IT, the next audit will uncover the same problems. Automating this workflow is one of the improvements with the strongest return.

If you are not sure your company is getting the most out of the tools it pays for, start with this blog.

If you are considering Copilot, reviewing permissions is a mandatory first step. Learn more in our newest article.

Request a Microsoft 365 Audit

A well-executed audit can pay for itself: it frees up licenses, closes access points that no one was monitoring, and gives you the data you need to negotiate your next renewal with confidence.

At DITESA IT Solutions, we review your Microsoft 365 environment end to end: license inventory, application activity, accounts, permissions, and security settings. We provide prioritized findings, manage licensing adjustments, and, if needed, keep your environment under control with managed support.

To help prevent the same issues from returning, ConversIA automates processes such as employee onboarding and offboarding, and helps you establish access governance before deploying Copilot or other artificial intelligence solutions.

Schedule a call with our team to discover how a Microsoft 365 audit can help your company save money and improve security.

SCHEDULE A CALL

READY TO STOP PUTTING OUT FIRES?

Book a free Discovery Session

We analyze your current infrastructure, identify risks and present you with a concrete proposal. No jargon. No commitment.

Book your Discovery Session →

Ready to take your operation to the next level?

Book your free diagnostic session. We identify your company's most relevant technology risks and show you the path to resolve them.