JFDI provides Microsoft 365 due diligence for investors, acquirers and boards. Our consultants assess a target’s Microsoft 365, SharePoint and Power Platform estate and tell you, in plain English, what is really in it, what it costs, where the risk sits and what it will take to separate or integrate after the deal.
Most businesses depend on Microsoft 365 more than their IT inventory shows. Years of documents sit in SharePoint and Teams. Power Apps and Power Automate flows that someone built to solve a problem one afternoon now run part of the business. Permissions have drifted, and licences are bought and never reclaimed. None of it is on the balance sheet, but after completion the buyer either inherits it or has to replace it.
JFDI is a Microsoft ISV Success Partner and a Cloud Solution Provider (CSP). We cover Microsoft 365 as part of our technical due diligence, or on its own when the tenant is the main question.
What We Assess
Tenant Security Posture
Identity, administrator roles, MFA, conditional access and external sharing.
Licensing Cost and Waste
What is paid for against what is used, and the cost after the deal.
Shadow Power Apps and Flows
The apps, flows and connectors we can see, and who owns them.
Data Sprawl and Oversharing
Duplicated content, sites with no owner and overshared sensitive data.
Line-of-Business Integration
Connections to finance, CRM, HR and operational systems.
Separation and Migration
What a carve-out, integration or tenant-to-tenant move involves.
How much we can see depends on the access the deal allows. The report says what we examined ourselves and what came from the target.
Tenant configuration and security posture
The defaults in a Microsoft 365 tenant are not always the safe ones. We review how identities and administrator roles are managed, whether multi-factor authentication and conditional access are enforced, how external sharing and guest access are controlled, and how well accounts are protected against compromise. Weaknesses here become yours at completion.
Licensing cost and waste
We compare what the target pays for with what it uses: licences assigned to leavers, inactive accounts, premium plans bought for features nobody uses, and add-ons that overlap.
The deal itself can change the licensing. If the target buys its licences through a parent group’s agreement or a reseller, they may not move with the business, and it may need its own agreement at its own prices. We set out how the target is licensed now, what would have to change and roughly what that would cost.
Shadow Power Apps and flows, and who owns them
Power Platform lets anyone build an app or automate a process, so most estates contain apps and flows IT doesn’t know about. With administrative access, our tooling maps the Power Platform environments: apps, flows, connectors and the data they touch. Our approach to shadow IT then shows which of them matter.
For each one the business relies on, we record who owns it, whose account it runs under and what it would take to move it into the organisation’s ownership. A flow that runs under one employee’s account can stop when that person leaves, so this shows you which processes depend on individuals and need dealing with around completion.
Data sprawl and oversharing
Years of SharePoint, OneDrive and Teams use leave duplicated and outdated content, sites with no owner and permissions far wider than intended. That matters for data protection and for any Copilot rollout, as Permission-Aware Isn’t the Same as Safe explains. We assess how much sensitive data is overshared and how much content is worth migrating at all. If Copilot is planned after the deal, our Copilot readiness assessment goes further.
Integration with line-of-business systems
Flows push data into finance systems, SharePoint lists feed reports, and custom connectors reach into CRM, HR and operational systems. We map these connections and identify which depend on accounts or settings in the target’s tenant, and so would break in a migration or separation.
What a tenant-to-tenant migration or separation involves
After the deal, the tenant usually has to go somewhere: into the acquirer’s tenant, out of a parent group’s, or onto its own. Mailboxes, OneDrive and SharePoint content move with established tools, though identities, domains and permissions need planning. Power Apps, flows and integrations usually need rework rather than a straight copy.
In a carve-out, the business may depend on things the seller owns: the tenant itself, shared domains, a group licensing agreement, shared sites and Teams, integrations run by group IT. We list what the buyer inherits, what has to be replaced and what the seller would need to keep providing for a transitional period.
That affects the deal as well as the integration plan. Months of dependence on the seller’s tenant belong in the transitional arrangements and the price.
What You Receive
After the Deal
We can also do the work the findings lead to: the migration or separation itself, Microsoft 365 modernisation, and moving systems that have outgrown SharePoint or Power Platform.
If the target’s products use AI, see our AI due diligence.
Microsoft 365 Due Diligence FAQs
What is really in the target’s tenant?
Tell us about the deal and your timeline, and we’ll scope a review around it.

