Exchange, Entra ID, SharePoint and Teams Testimony
One Microsoft 365 Event, Every Log That Recorded It
A compromised mailbox, a departing executive's OneDrive or a disputed Teams message is never a single event in Microsoft 365; it is a sign in, a mailbox action, a file event and a permission, each recorded in a different log with a different retention. We test every entry against Microsoft’s own audit definitions and the tenant’s actual settings, then connect the entries into one account of what happened and who did it. Our email practice has analyzed hundreds of compromised accounts, and our examiners have testified in federal and state courts.
The Mailbox Is Only Where the Dispute Starts
Most engagements begin with a mailbox question: whether a message was sent, whether an account was taken over, whether an instruction was genuine. The answer almost always lives in the tenant around the mailbox. Entra ID records the sign ins, Exchange Online records the mailbox actions, SharePoint and OneDrive record the files, and Teams records the conversations, and we examine them together so the opinion describes the whole event rather than one view of it.
We define the tenant, the accounts, the services and the period around counsel’s questions, including the shared documents and permissions that an email dispute tends to drag in. Then we establish what has already been supplied, what still exists on the platform and what needs to be preserved before retention policies quietly close the window. Our email practice has analyzed hundreds of compromised accounts, and the first week is usually when preservation decides what the case can later prove.
If the first week is now, call (800) 868-8189 and we will tell you which tenant records to preserve before the retention window closes.
Exchange, Entra ID and File Records, Read as One
Depending on scope and what the tenant retained, the examination can draw on Exchange Online, Entra ID, SharePoint, OneDrive and Teams records together with application permissions and audit configuration. The work separates permissions from observed actions and separates an authentication event from evidence that content was actually accessed, because those are the distinctions a cross examination turns on.
In a departure matter we examine the file activity, the access rights and the routine synchronization that may explain recorded movement before anyone calls it exfiltration. A successful sign in establishes that a credential was used at a time and from a place. The actions that followed, and the person responsible for them, each require their own supporting evidence, and the report keeps those three findings apart.
Litigators who have been handed a sign in record as proof of exfiltration can ask us what the surrounding records would need to show before the argument is made in a filing.
Test the Disputed Activity Against Microsoft’s Own Event Definitions
We test the proposed timeline against the actual definitions of the audit activities: whether a record supports a download, a sharing change, a mailbox rule or some other action, and whether an application identity explains activity that has been attributed to a user. This is where most Microsoft 365 opinions are weakest, because the labels are easy to read and hard to read correctly.
We reconcile time formats, identifiers and retention across the relevant services and identify the accounts, applications and resources behind each event. Every gap is logged by service and date, and each event is read for exactly what it records and nothing more, which keeps the timeline sound for whichever side relies on it.
Bring the disputed timeline to a free initial consultation and we will tell you which events it relies on and which definitions they have to meet.
Show the Records and the Tenant Settings Behind the Opinion
Findings cite the source records, the relevant tenant settings and the collection coverage. We assess licensing, retention and audit configuration because they decide how much the tenant ever recorded, and the report shows the evidence behind the opinion alongside the configuration that produced it. Before the opinion is formed we confirm the examiner’s relevant experience, conflicts and availability for the schedule.
We explain which events establish the sequence and where the chronology depends on inference. Exhibits distinguish account access, mailbox activity and document events, with the meaning and source of each entry clear enough for a judge, a juror and an opposing examiner to follow, and the examiner who built them is the one who explains them under oath.
To learn which examiner would sign the report and whether the schedule works, send us the service list and the key dates.
How Your Microsoft 365 Expert Witness Examines the Case
Define the disputed tenant activity
We discuss the disputed Microsoft 365 activity, the expertise it requires, conflicts and the reporting and testimony deadlines with counsel, and we identify what must be preserved immediately.
Examine the available service records
We examine the Exchange, Entra ID, SharePoint, OneDrive and Teams records the tenant retained, document the correlation and interpretation methods and record the coverage of each source.
Explain the findings and prepare the exhibits
We prepare findings and exhibits that keep observation and technical opinion distinct for the court, then prepare for the declaration, deposition or hearing where they will be tested.
For matters where the tenant is only one of the disputed systems, the full practice, from source code to mobile devices, is described under digital forensics and expert witness services.
Microsoft 365 Evidence Your Expert Examines
Exchange Online and Entra ID records supply the mail and identity context, while SharePoint, OneDrive and Teams records connect the shared content and collaboration activity to the accounts involved. Application permissions, audit settings, licensing and retention configuration establish the access model and tell us how complete the recorded coverage can be for the period in dispute.
Expert Reports Built on the Tenant Record
Technical findings identify the supporting records and the tenant conditions relevant to each opinion, and timelines and exhibits connect the service events to the specific questions in the case. Opposing opinion review tests the stated methods and conclusions against the available tenant evidence, and the agreed assignment can include expert reports, declarations and testimony on the examined Microsoft 365 questions.
Not every matter needs every one of these, so tell us the stage the case has reached and we will scope the report and testimony to it.
Reconstruct the Event Across the Whole Tenant
A sign in, a mailbox event and a file download can describe three stages of one incident or three unrelated moments, and only the surrounding record tells you which. We compare records for the scoped accounts, applications, resources and period, including the shared resources the account could reach, so the opinion addresses the connected tenant activity rather than a single log read in isolation.
We interpret audit activities using Microsoft’s own definitions, the event fields and the actual tenant settings. A sharing event may show a permission change while a separate record is needed to establish that the recipient opened the file, and a successful sign in does not identify every item accessed afterward. Those distinctions are small on the page and decisive in the courtroom.
In a departure dispute, counsel may ask whether documents were copied before access ended. We compare the retained identity and file events, the application permissions and any relevant endpoint records, and we distinguish the files the account could reach from the files the records show it accessed or transferred, so the finding presented is the finding the evidence can carry.
If a departure dispute is already on your desk, ask us to read the retained identity and file events before anyone equates the files the account could reach with the files it took.
Separate What the Account Could Reach From What It Did
- Identity
We establish the accounts, applications and sign in context behind the activity.
- Mail and files
We examine the relevant Exchange, OneDrive, SharePoint and Teams records.
- Event sequence
We reconcile time bases, identifiers and resource events to connect the sequence.
- Scope opinion
We explain the observed actions and the records that support each one.
Technical Reference
Meet the Examiners Who Testify About Microsoft 365 Evidence
Robert Knudsen, Computer Forensics and Cybersecurity Specialist, holds the CISSP and Certified Computer Examiner credentials together with Microsoft Certified Professional status, and has conducted hundreds of computer and mobile device examinations supporting federal and state court matters across the United States over eighteen years of forensic work, following twenty years with the New York City Police Department. Joseph Caruso, founder, CEO and CTO, was accepted by a federal court as an expert in computer forensics and computer science in COMLAB v. Kal Tire, a matter in which the court found the disputed emails fabricated.
Veronica Perez, Senior Computer Forensic Specialist, has been designated as a digital forensics expert witness in California, Oklahoma and South Carolina state courts and in federal court in Chicago and brings the mobile device side of a Microsoft 365 account into the examination. Meet the GDF team and ask for a current CV. The examiner assigned depends on the services and the questions in the matter, and selection, conflicts and availability are confirmed during scoping.
Conflicts and availability can be checked in one call; (800) 868-8189 reaches us around the clock, and the first consultation is free. Attorneys new to the subject can start with the digital forensics FAQ.
Shared Files, Applications and Missing Logs
Did the account access shared files as well as email?
We compare the available Exchange, SharePoint, OneDrive, Teams and identity records. The opinion separates the permissions the account held from the activity recorded against particular files, so possible reach and supported access stay distinct and the argument rests on the stronger ground.
Was that action taken by a user or an application?
We examine the identity and event records alongside delegated and application permissions to assess how an action occurred, including synchronization clients and third party integrations. The opinion sets out the evidence for attributing the activity to an application, to an account or to a person.
What can we establish if some logs are missing?
Retained records can still carry much of a chronology. We explain the conclusions they support and identify the further sources that can close a gap, such as endpoint records, mailbox exports or provider preservation, so the timeline rests on evidence rather than on the absence of it.
Talk with an examiner
Plan the Microsoft 365 opinion your case needs
Bring the tenant services involved, the disputed events and the case deadline to a free initial consultation. We will review relevant expertise, conflicts and the records needed for the proposed opinion with counsel before anything is engaged.
Hundreds of compromised account analyses and email related testimony engagements, a 24/7 hotline and a firm in practice since 1992.
Talk with an examiner
Put a Microsoft 365 Expert on the Tenant Record
Tell us which services, licenses and audit settings the tenant runs. We identify the sign in, mailbox and file records still inside their retention window and what to preserve this week, and the consultation costs nothing.
24/7 hotline: (800) 868-8189
GDF does not accept pro se litigation cases, and GDF may decline matrimonial or family law cases at our discretion.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .