Step 3 — Calendar processing defaults

New room mailboxes already arrive with AutomateProcessing: AutoAccept, so auto-accept usually needs no change. Two other defaults do, and both are destructive in a way nobody notices until a customer asks why their booking lost its name.

Check first:

Get-CalendarProcessing -Identity "pod01@yourdomain.com" | Format-List AutomateProcessing, AllowConflicts, DeleteSubject, AddOrganizerToSubject

DeleteSubject and AddOrganizerToSubject both default to $true on a room mailbox. Together they erase the event's subject and replace it with the organiser's name. Any booking arriving as a meeting request loses its title.

Set-CalendarProcessing -Identity "pod01@yourdomain.com" ` -AutomateProcessing AutoAccept ` -AllowConflicts $false ` -DeleteSubject $false ` -AddOrganizerToSubject $false ` -DeleteComments $false

AllowConflicts $false is the one that matters commercially: it is what stops two customers holding the same pod for the same half hour.

A caveat worth knowing before spending time here. Auto-accept only fires when a room receives an invitation. If the adapter writes bookings by posting directly into the room's calendar, the room is the organiser rather than an invitee, and none of these settings apply to those events — they are only relevant to meetings people book through Outlook.