Get Calendar Diagnostic Logs in Exchange Online Using PowerShell (Get-CalendarDiagnosticObjects)

When a user reports that a critical meeting mysteriously vanished from their calendar, changed time zones, or was unexpectedly cancelled, guessing is not an option. Every action taken on a calendar item in Exchange Online—whether triggered by Outlook Desktop, Outlook Mobile (iOS/Android), OWA, a delegate, or the Calendar Repair Assistant (CRA)—is recorded inside the mailbox's hidden Calendar Logging folder (located under Recoverable Items, with a default 6 GB quota).

In earlier versions of Exchange Online PowerShell, administrators used Get-CalendarDiagnosticLog. Microsoft deprecated Get-CalendarDiagnosticLog in the modern ExchangeOnlineManagement (REST v3) module and replaced it with Get-CalendarDiagnosticObjects alongside Get-CalendarDiagnosticAnalysis.


Calendar Diagnostic Logging Architecture

Exchange Online Calendar Diagnostic Investigation Workflow
Step 1: Event Trigger
Client / Delegate Action
Outlook Desktop, OWA, Mobile, Delegate, or CRA modifies item
Step 2: Hidden Store
Calendar Version Store
Recoverable Items\Calendar Logging (6 GB default quota)
Step 3: EXO V3 Extraction
Get-CalendarDiagnosticObjects
Extracts MAPI snapshots, TriggerAction & ClientInfoString
Step 4: Verdict
Root Cause Identified
Pinpoints exact User, Timestamp, Device & Action

Legacy vs. Modern Exchange Online Calendar Cmdlets

If you run the legacy two-step pipeline (Get-CalendarDiagnosticLog | Get-CalendarDiagnosticAnalysis) in the modern Exchange Online PowerShell V3 module, you will hit either a command-not-found error or a type conversion error:

Cannot process argument transformation on parameter 'CalendarLogs'. Cannot convert value "System.Collections.ArrayList" to type "Microsoft.Exchange.Management.StoreTasks..."

Use this reference table to map legacy commands to modern Exchange Online cmdlets:

TaskLegacy Cmdlet (Deprecated)Modern EXO V3 Cmdlet (Recommended)
Fetch raw calendar item snapshotsGet-CalendarDiagnosticLogGet-CalendarDiagnosticObjects
Reconstruct chronological timelineGet-CalendarDiagnosticAnalysis (via object pipe)Get-CalendarDiagnosticObjects (inspecting TriggerAction & ClientInfoString)
Verify Calendar Repair ConfigGet-MailboxCalendarConfigurationGet-Mailbox -Identity <User> \Select CalendarRepairDisabled

Step 1: Extract Calendar Logs for a Specific Meeting

Connect to Exchange Online PowerShell (Connect-ExchangeOnline) and query the affected user's mailbox by Meeting Subject and an optional date window:

POWERSHELL
# Connect to Exchange Online PowerShell V3
Connect-ExchangeOnline -ShowBanner:$false

# Retrieve all diagnostic log versions for a specific meeting subject
$Mailbox = "[email protected]"
$Subject = "Quarterly Architecture Review"

$CalLogs = Get-CalendarDiagnosticObjects -Identity $Mailbox `
    -Subject $Subject `
    -StartDate (Get-Date).AddDays(-30) `
    -EndDate (Get-Date)

# Display chronological history of changes to the meeting
$CalLogs | Sort-Object OriginalLastModifiedTime | Select-Object `
    OriginalLastModifiedTime,
    NormalizedSubject,
    ItemClass,
    TriggerAction,
    ClientInfoString,
    ResponsibleUserName,
    AppointmentState,
    StartTime,
    EndTime | Format-Table -AutoSize

Searching by CleanGlobalObjectId (When the Subject Changed)

If a delegate renamed the meeting or multiple meetings share the same subject, grab the CleanGlobalObjectId from one entry and pull the exact item history across both the organizer and attendee mailboxes:

POWERSHELL
# Get the unique CleanGlobalObjectId from the first matching entry
$GlobalId = ($CalLogs | Select-Object -First 1).CleanGlobalObjectId

# Pull the complete lifecycle of that specific meeting ID
Get-CalendarDiagnosticObjects -Identity $Mailbox -MeetingId $GlobalId |
    Sort-Object OriginalLastModifiedTime |
    Select-Object OriginalLastModifiedTime, TriggerAction, ClientInfoString, ResponsibleUserName

Step 2: Decoding Key Calendar Diagnostic Properties

When reviewing the output of Get-CalendarDiagnosticObjects, focus on these critical properties to pinpoint the root cause:

PropertyWhat It Tells YouCommon Values / Examples
OriginalLastModifiedTimeExact UTC timestamp when the calendar action occurred2026-11-06T14:22:10Z
TriggerActionThe specific operation performed on the calendar itemCreate, Update, SoftDelete, HardDelete, MoveToDeletedItems
ClientInfoStringThe application, protocol, or background assistant that made the changeClient=OutlookService (Outlook Mobile), Client=REST; CalendarRepairAssistant, Client=MSExchangeRPC (Outlook Desktop), Client=OWA
ResponsibleUserNameThe LegacyExchangeDN or UPN of the user/delegate who triggered the edit/o=ExchangeLabs/ou=Exchange Administrative Group.../cn=User
ItemClassWhether the record is the calendar appointment itself or a meeting messageIPM.Appointment (Calendar item), IPM.Schedule.Meeting.Request, IPM.Schedule.Meeting.Canceled
AppointmentStateBitmask of the meeting state1 = Meeting, 2 = Received, 3 = Meeting+Received, 4 = Cancelled (5 or 7 = Cancelled Meeting)

Step 3: Production Script — Export Full Calendar Audit Report to CSV

Because Get-CalendarDiagnosticObjects returns deeply nested MAPI properties, this production-ready PowerShell function extracts, flattens, and exports a clean chronological audit trail to CSV so you can filter it in Excel or share it with the ticket requester.

POWERSHELL
function Export-ExchangeCalendarDiagnosticReport {
    [CmdletBinding()]
    param (
        [Parameter(Mandatory = $true)]
        [string]$MailboxIdentity,

        [Parameter(Mandatory = $true)]
        [string]$MeetingSubject,

        [Parameter(Mandatory = $false)]
        [int]$DaysBack = 30,

        [Parameter(Mandatory = $false)]
        [string]$OutputCsvPath = ".\CalendarDiagnosticReport_$(Get-Date -Format 'yyyyMMdd_HHmmss').csv"
    )

    Write-Host "[*] Querying Calendar Diagnostic Objects for '$MailboxIdentity' (Subject: '$MeetingSubject')..." -ForegroundColor Cyan

    $StartDate = (Get-Date).AddDays($DaysBack)
    $EndDate   = (Get-Date).AddDays(1)

    $RawLogs = Get-CalendarDiagnosticObjects -Identity $MailboxIdentity `
        -Subject $MeetingSubject `
        -StartDate $StartDate `
        -EndDate $EndDate `
        -ResultSize Unlimited

    if (-not $RawLogs) {
        Write-Warning "No calendar diagnostic logs found for subject '$MeetingSubject' in '$MailboxIdentity' over the last $DaysBack days."
        return
    }

    $Report = foreach ($Entry in ($RawLogs | Sort-Object OriginalLastModifiedTime)) {
        [PSCustomObject]@{
            ModifiedTimeUTC      = $Entry.OriginalLastModifiedTime
            Subject              = $Entry.NormalizedSubject
            TriggerAction        = $Entry.TriggerAction
            ItemClass            = $Entry.ItemClass
            ClientApplication    = $Entry.ClientInfoString
            ResponsibleUser      = $Entry.ResponsibleUserName
            SenderEmailAddress   = $Entry.SenderEmailAddress
            StartTime            = $Entry.StartTime
            EndTime              = $Entry.EndTime
            IsCancelled          = ($Entry.AppointmentState -band 4) -eq 4
            ResponseType         = $Entry.ResponseType
            CleanGlobalObjectId  = $Entry.CleanGlobalObjectId
            ParentDisplay        = $Entry.ParentDisplay
        }
    }

    $Report | Export-Csv -Path $OutputCsvPath -NoTypeInformation -Encoding UTF8
    Write-Host "[+] Exported $($Report.Count) calendar log events to: $OutputCsvPath" -ForegroundColor Green
    return $Report
}

# Example Usage:
# Export-ExchangeCalendarDiagnosticReport -MailboxIdentity "[email protected]" -MeetingSubject "Weekly CAB Sync" -DaysBack 14

Common Root Causes Found in Calendar Logs

  1. Client=ActiveSync or Client=OutlookService with TriggerAction = SoftDelete: A mobile device (frequently native iOS Mail/Calendar app) synced an outdated state and deleted or declined the meeting.
  2. ResponsibleUserName differs from the Mailbox Owner: A calendar delegate deleted the invite from their own Deleted Items or moved it, unintentionally syncing the deletion to the principal's calendar.
  3. Client=TBA;Action=CalendarRepairAssistant: Exchange Online's automated Calendar Repair Assistant detected a mismatch between the organizer's master copy and the attendee's copy and updated or removed the item to match the organizer.