Skip to content
Sondeon

For the CIO, the head of security and the CFOOn request

Microsoft 365 and Azure audit: a health check of accounts, permissions and licenses Every new hire, guest and app adds permissions to your tenant. Who removes them?

We review the state of your tenant (your company's organization in Microsoft's cloud) and tell you which accounts and permissions are a risk and which licenses are paid for and not used.

You get the risky accounts and permissions by priority and the licenses you can adjust. Scope and timeline are in writing before we start.

White interior atrium of an office building, with a triangular lattice roof and glass walls

Updated on

Who it is for

  • You don't know how many administrators there are or whether they use MFA (a second factor)
  • There are external guests and connected apps nobody goes over
  • You pay for Microsoft 365 licenses on accounts no longer in use

You don't need it if your company has few accounts, no guests or connected apps, and someone already goes over them.

A forgotten account is an open door

The tenant is the key to your email, your documents and your cloud. An account without MFA or one permission too many gives no warning until the day someone uses it, and the licenses are billed every month all the same. Across the companies Zylo measures (SaaS Management Index 2026), 36% of SaaS licenses sit below recommended usage on average. That figure covers all subscription software, and Zylo sells license management.

36 %

of SaaS licenses sit below recommended usage, on average across the companies Zylo measures

Zylo, SaaS Management Index 2026

What we review in the Microsoft 365 audit: the health check of your tenant

  • Entra ID: MFA, conditional access and administrator accounts
  • Inactive users and external guests
  • Apps with excessive permissions
  • External sharing in SharePoint, OneDrive and Teams
  • Email forwarding rules in Exchange Online
  • Unused Microsoft 365 licenses and idle Azure resources
  • Secure Score: which pending actions are worth doing

The control points of these five reviews are not counted yet, so we publish no figure: the scope is agreed in writing for each case.

Technologies covered

  • Microsoft 365
  • Azure

Trademarks and logos belong to their respective owners. Their use here is descriptive only and implies no commercial relationship or sponsorship.

What we review, area by area

  • People and accounts (Entra ID)

    • Users: department, job title, country and company, creation date, whether the account is enabled and whether it is a member or a guest
    • Last sign-in of every account, interactive and background, and how many days it has gone unused
    • Licenses of each person and the services they include
    • Company licenses: purchased, assigned and available, by type
    • External guests: which domain they come from, who invited them and whether they have ever signed in
    • MFA registration: who has it, with which method (app, SMS or security key) and who has not set it up
    • Administrators: who holds each role, from Global Admin to Exchange Admin, and whether they use it
    • Conditional Access: active policies, who they apply to, their exclusions and trusted locations
    • Groups: members, owners, dynamic groups and security groups
  • Devices and activity

    • Devices in Entra ID: operating system and version, corporate or personal, whether they are managed and compliant, last check-in and owner
    • Sign-ins: who, when, to which application, from which system, browser, IP and country, whether they passed MFA and, if it failed, why
    • Real use of Outlook, Teams, OneDrive and Copilot, including background use without an interactive sign-in
    • Activity of administrator accounts
    • Intune: serial number, model, encryption, disk and primary user of each device, and the installed software with its version
    • Microsoft 365 usage per person: emails sent and read, Teams meetings, OneDrive files and storage
    • Purview logs: which files each person opens, downloads or shares
  • Applications and permissions

    • Enterprise applications in the tenant, their publisher and whether anyone in the organization can access them
    • Who has access to each application, directly or through which group, and with which role
    • Applications with Microsoft Graph permissions able to read all mail, all files or change the directory
    • Consents an employee granted on their own for an application to access their data
    • Application secrets and certificates that have expired or are about to
  • Power Platform

    • Environments: type (production, sandbox or developer), region, whether they have Dataverse and who created them
    • Inventory of the agents, flows and apps in the tenant, with their owner, environment and dates
    • Flows: whether they are on, suspended or off, what triggers them, which connectors they use and who owns them
    • Flow runs: failures, the exact error and how often it repeats
    • Connections of each person (SharePoint, SQL, Gmail, Dropbox…) and the ones that have expired
    • Data loss prevention (DLP) policies: which connectors are allowed or blocked and which environments are left uncovered
    • Agent usage: conversations per agent and the agents nobody uses
    • Agent configuration: authentication, channels, who they are shared with, web search and the credentials they use
    • Dataverse tables and records in each environment
  • Azure

    • Everything deployed, by subscription and resource group: virtual machines, databases, storage and applications
    • Permissions (RBAC): who is Owner or Contributor of each subscription and resource
    • Internet exposure: public IPs and open storage
    • Cost by resource, group and tag, and how it evolves
    • Compliance with Azure Policy and best practices
    • Azure Advisor recommendations on cost, security and performance
    • Activity log (who created or deleted what) and Log Analytics
  • AI and data

    • Azure AI Foundry: accounts, projects, agents, models, versions that failed and network exposure
    • Fabric and Power BI: workspaces, including personal ones and those without an owner, reports, semantic models, lakehouses, pipelines and capacities
    • Microsoft Forms: the organization's forms and their responses

How it works

  1. Meeting and written scope

    In 30 minutes we look at the size of your tenant and which Azure subscriptions are included. Then you get the scope and timeline in writing.

  2. Read-only health check

    We look at and measure accounts, permissions, apps and licenses. We change nothing in your tenant unless you ask.

  3. Report and results meeting

    You get the risky accounts and permissions by priority and the licenses you can adjust. We go through it with your IT team.

What we need from you

  • Read-only permissions in your Microsoft 365 and Azure tenant
  • The Azure subscriptions you want included
  • One person on your IT team to answer questions

How we work

What you get

  1. Risky accounts and permissions, by priority
  2. Licenses and Azure resources you can adjust
  3. List of external access nobody needs
  4. One-page executive summary for leadership

How a finding arrives

Priority: High

Global administrator account without MFA

Where
Entra ID, global administrator role
Evidence
The authentication methods report shows the account with no second factor and with recent sign-ins
Impact
One leaked password gives control of the whole tenant

An example of the report format, not a client's.

Shall we talk about your case?

A 30-minute meeting to see what you have and what to review first.

Book a free meeting

Expert review, automated tool or the AI itself

All three are useful, each for one thing. AI brings the volume and people bring the judgment: that is why our review uses an automated AI tool and senior developers supervise it.

See the full comparison

Hands drawing a diagram of screens joined by arrows with a marker on a small whiteboard, next to white headphones

Who reviews

The review is done by a team of senior developers, with many hours of development and of finding the mistakes AI makes when it codes. We know more than 1,200 review points. The automated AI tool goes through them, and people verify, direct and review.

Team of senior developers

José María Salido, founder of Sondeon, answers for it

  • AI brings the volume: it goes through the known review points
  • People bring the judgment: they verify every finding before it goes into the report
  • The result is explained in a meeting with your team
Who answers for it: José María Salido, on LinkedIn

Frequently asked questions

What is a Microsoft tenant?

It is your company's organization in Microsoft's cloud: Entra ID users, Microsoft 365 licenses, email, SharePoint, Teams and Azure subscriptions all hang from it. Whoever controls an administrator account controls all of that.

What is Microsoft Secure Score, and what is a good score?

It is the score Microsoft uses to summarize your tenant's security. There is no single good number: it depends on which licenses you have and which controls you can turn on. We look at which of the pending actions are worth doing in your tenant, and in what order.

What do you need, and do you change anything in our tenant?

We need read-only permissions and one person on your IT team to answer questions. We change nothing unless you ask: the health check looks and measures.

Can we apply the changes ourselves, or do you do it?

Either works. The diagnosis comes first: each risky account and permission with its evidence and its priority. The fix is separate and only happens if you request it: your team applies it with the list in hand, or we do if you ask us to.

How much does a Microsoft 365 audit cost?

The 30-minute meeting is free. The rest depends on the size of your tenant: how many accounts, apps and Azure subscriptions are included. We go over it in that meeting, and you get the scope and timeline of our health check in writing before we start.

What is a Microsoft 365 audit for, and what does it review?

It tells you how your tenant stands today, which is different from turning on the Microsoft 365 audit log. Our health check reviews accounts without MFA, guests and apps with excess permissions, and unused licenses, and delivers every finding with its evidence.

Do you also review Power BI and Microsoft Fabric?

Yes. We review Power BI, Microsoft Fabric, Databricks, Microsoft 365 and Microsoft agents. Power BI and Microsoft Fabric each have their own health check and their own page: data that arrives stale or broken, and licenses or capacity paid for and not used.

Other services

  • Salesforce health check

    Automations that fail silently, users who have left and unused licenses you keep paying for in your Salesforce org.

  • Microsoft Fabric health check

    Pipelines that feed reports with stale or broken data, and capacity that is paid for but not used.

  • Databricks health check

    Jobs that fail without warning, clusters that cost more than they deliver and users who no longer need access.

  • Power BI health check

    Reports built on stale or broken data, refreshes that fail and licenses assigned to people who no longer use them.

Data platformsAll services

Request your free meeting

Fill in the form and we email you to set a day and a time. It is 30 minutes to see what you have and what to review first.

What should we control?

We use your details to answer your request, to be able to prove we received it and to protect the form. The privacy policy explains it in detail.