Quick answer: Get-CalendarDiagnosticObjects returns the calendar diagnostic logs (CDLs) for a mailbox in Exchange Online: every change to a meeting, when it happened, and which client made it. To see the history of one meeting, sorted oldest first:
$logs = Get-CalendarDiagnosticObjects -Identity "ayla@contoso.com" -Subject "Budget Review" -ExactMatch $true
$logs | Select-Object *,@{n='OLMT'; e={[DateTime]::Parse($_.OriginalLastModifiedTime.ToString())}} | Sort-Object OLMT | Format-Table OriginalLastModifiedTime,CalendarLogTriggerAction,ItemClass,ClientInfoString
Exchange Online keeps these logs for 31 days. After that, the history of a change is gone.
Three ways to get calendar logs
| Method | Best for | Output |
|---|---|---|
| Microsoft's summary script | Most investigations | Excel file with a timeline per person |
| Get-CalendarDiagnosticObjects | Quick checks, custom filters | Raw log entries in PowerShell |
| Microsoft 365 admin center | Admins who don't use PowerShell | Collected logs, no setup |
All three read the same logs. The steps below come from Microsoft's Get calendar diagnostic logs guide and the cmdlet reference.
Before you start
The cmdlet runs in Exchange Online PowerShell, and you need Exchange admin permissions. Connect first:
Install-Module -Name ExchangeOnlineManagement
Connect-ExchangeOnline -UserPrincipalName admin@contoso.com
On-premises Exchange uses Get-CalendarDiagnosticLog instead. Microsoft says that cmdlet only works on-premises, even though it exists in Exchange Online.
1. Use Microsoft's summary script (recommended)
Microsoft recommends the Get-CalendarDiagnosticObjectsSummary.ps1 script over the raw cmdlet. It calls Get-CalendarDiagnosticObjects for you and turns the output into a readable timeline.
Download the script from aka.ms/CalLogSummary.
Install the Excel module it needs:
Install-Module -Name ImportExcelRun it for one meeting. List the organizer, any delegate and the affected attendee:
.\Get-CalendarDiagnosticObjectsSummary.ps1 -Identity "tony@contoso.com","chris@contoso.com","ayla@contoso.com" -MeetingId "040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55" -TrackingLogs -Exceptions -ExportToExcel
The script writes CalLogSummary_<short meeting ID>.xlsx. Each person gets a _TimeLine sheet, an enhanced log sheet and a _Raw sheet. Start with the timeline.
Don't have the meeting ID? Search by subject instead. This mode takes one mailbox and writes a file for each matching meeting:
.\Get-CalendarDiagnosticObjectsSummary.ps1 -Identity "ayla@contoso.com" -Subject "Budget Review" -ExportToExcel
The meeting ID is in the CleanGlobalObjectId column of that file. Microsoft recommends the meeting ID: it gives more detailed logs, and only for that meeting.
2. Use the cmdlet directly
Syntax
Get-CalendarDiagnosticObjects
[-Identity] <UnifiedGroupOrUserMailboxIdParameter>
[-AnalyzeExceptionWithOriginalStartDate <ExDateTime>]
[-AutoRequeryOnMeetingId <Boolean>]
[-ConfigurationName <String>]
[-CustomPropertyNames <String[]>]
[-EndDate <ExDateTime>]
[-EntryId <String>]
[-EwsId <String>]
[-ExactMatch <Boolean>]
[-ItemClass <String[]>]
[-ItemIds <String[]>]
[-MaxResults <Int32>]
[-MeetingId <String>]
[-ODataId <String>]
[-ResultSize <Unlimited>]
[-ShouldBindToItem <Boolean>]
[-ShouldDecodeEnums <Boolean>]
[-ShouldFetchAttendeeCollection <Boolean>]
[-ShouldFetchRecurrenceExceptions <Boolean>]
[-ShouldResolveParticipants <Boolean>]
[-StartDate <ExDateTime>]
[-Subject <String>]
[<CommonParameters>]
The parameters that matter
| Parameter | What it does |
|---|---|
-Identity |
The mailbox or Microsoft 365 group. Required. A $null value returns every mailbox's objects, so check your variables. |
-Subject |
Matches the subject. Not case sensitive, no wildcards. By default it's a partial match over at most 1,000 items. |
-ExactMatch $true |
Matches the subject exactly and searches every item. Use it: partial matches can miss logs. |
-MeetingId |
The meeting's CleanGlobalObjectId, which never changes. Overrides -Subject and -ExactMatch. |
-StartDate, -EndDate |
Filter by when the item was last modified, not when it was created. Use your computer's short date format. |
-ItemClass |
Only return one type of item, such as IPM.Schedule.Meeting.Request. |
-ShouldBindToItem $true |
Returns large properties in full instead of truncated. |
-ShouldFetchRecurrenceExceptions $true |
Includes changes to single occurrences of a recurring meeting. Needs -ItemIds. |
-ResultSize |
Number of results. The maximum is 1000. |
Examples
Logs for one meeting, by subject:
Get-CalendarDiagnosticObjects -Identity "ayla@contoso.com" -Subject "Budget Review" -ExactMatch $true
Find a meeting's ID. This is Microsoft's own method. Copy the CleanGlobalObjectId for the right start time:
$cdls = Get-CalendarDiagnosticObjects -Identity "ayla@contoso.com" -Subject "Budget Review" -ExactMatch $true
$cdls | Sort-Object -Unique CleanGlobalObjectId | Format-List SubjectProperty,CleanGlobalObjectId,StartTime
Logs for one meeting, by ID:
Get-CalendarDiagnosticObjects -Identity "ayla@contoso.com" -MeetingId "040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55"
Only meeting requests:
Get-CalendarDiagnosticObjects -Identity "ayla@contoso.com" -MeetingId "040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55" -ItemClass IPM.Schedule.Meeting.Request
Export a date range to CSV:
Get-CalendarDiagnosticObjects -Identity "ayla@contoso.com" -Subject "Team Lunch" -ExactMatch $true -StartDate 11/1/2026 -EndDate 11/18/2026 | Export-Csv "C:\Temp\Team Lunch.csv" -NoTypeInformation
Add extra properties to the output:
Get-CalendarDiagnosticObjects -Identity "ayla@contoso.com" -Subject "Budget Review" -ExactMatch $true -CustomPropertyNames ClientIntent,FreeBusyStatus,From,SendMeetingMessagesDiagnostics,Sensitivity
3. Use the Microsoft 365 admin center
No PowerShell needed:
- In the Microsoft 365 admin center, go to Troubleshoot > Collect Logs > Calendar > Calendar Logs.
- Enter the calendar owner's email address and the meeting subject.
- Select Start.
How to read the output
Each row is one change to one item. These columns answer most questions:
| Column | What it tells you |
|---|---|
OriginalLastModifiedTime |
When the change happened |
CalendarLogTriggerAction |
What happened: Create, Update, Move, MoveToDeletedItems, SoftDelete or HardDelete |
ItemClass |
What the item was, such as IPM.Appointment or IPM.Schedule.Meeting.Canceled |
ClientInfoString |
Which app made the change, such as Client=OWA (Outlook on the web) or Client=WebServices |
ResponsibleUserName |
Who made the change, as an Exchange legacy address |
AppointmentState |
1 meeting, 2 received, 4 cancelled, 8 forwarded (values add up) |
ResponseType |
0 none, 1 organizer, 2 tentative, 3 accepted, 4 declined, 5 not responded |
MeetingRequestType shows what kind of update was sent: 1 new request, 65536 full update, 131072 informational update, 262144 silent update, 524288 outdated, 1048576 forwarded to a delegate.
Microsoft's Analyze calendar diagnostic logs guide suggests cutting the noise first: keep the entries the summary script marks Core, remove attendee responses and forwards, and limit to the time the problem happened.
Find who cancelled or deleted a meeting
- Get the logs from the organizer's mailbox, sorted by time (the quick answer command).
- Find the row where
CalendarLogTriggerActionisMoveToDeletedItems,SoftDeleteorHardDelete, orItemClassisIPM.Schedule.Meeting.Canceled. - Read
ResponsibleUserNameandClientInfoStringon that row. A delegate's name withClient=OWAmeans the delegate did it in Outlook on the web.
If the change is older than 31 days, the logs won't show it.
FAQ
How long are calendar diagnostic logs kept?
31 days in Exchange Online.
Does Get-CalendarDiagnosticObjects work on-premises?
No. It's for Exchange Online. On-premises, use Get-CalendarDiagnosticLog.
Why doesn't my subject search find the meeting?
Without -ExactMatch $true, the search checks at most 1,000 items. Add -ExactMatch $true, or search by -MeetingId.
What is Get-CalendarDiagnosticObjectsSummary.ps1?
Microsoft's script that runs Get-CalendarDiagnosticObjects and builds an Excel timeline from the results. Download it from aka.ms/CalLogSummary.
Meeting room problems often start with a booking that changed without anyone noticing. Meeting Room 365 shows each room's live schedule on a display outside the door.