Microsoft 365 room mailboxes show organizer names or fail to parse third-party meetings

If you see any of the following in VCA Room Calendar:

• the meeting title is replaced by the organizer name
• Zoom still works, but Feishu, DingTalk, or Tencent Meeting links no longer parse
• the room mailbox event body is empty or reduced to blank HTML

the root cause is usually not the VCA parser itself.

In most cases, Microsoft 365 room resource mailbox processing rules are trimming the subject and the invitation body when the room auto-accepts the meeting.

Why this happens

Microsoft 365 room mailboxes may be configured with rules such as:

• AddOrganizerToSubject = $true
• DeleteSubject = $true
• DeleteComments = $true

This causes two direct problems:

1. The room mailbox replaces the original meeting title with the organizer name.
2. The room mailbox removes the invitation body.

For Zoom, this may look less obvious because Zoom links are often also stored in the location field.
But Feishu, DingTalk, Tencent Meeting, and many other third-party platforms depend more heavily on the invitation body. Once the body is removed, VCA can no longer parse the meeting details reliably.

When this article applies

This article is relevant if:

• you use Microsoft 365 / Exchange Online room resource mailboxes
• VCA connects to Microsoft 365 calendars through browser-based authorization
• you want VCA to show the real meeting title and parse third-party meeting links correctly

Recommended fix

The root fix is not to patch VCA first.
The correct fix is to change the Calendar Processing settings on the room mailbox so that the mailbox keeps the original subject and invitation body.

Recommended configuration:

Set-CalendarProcessing -Identity "[email protected]" `
  -AutomateProcessing AutoAccept `
  -AddOrganizerToSubject $false `
  -DeleteSubject $false `
  -DeleteComments $false `
  -ProcessExternalMeetingMessages $true `
  -RemovePrivateProperty $false

Before you start

Please confirm:

• you have Microsoft 365 Global Administrator or Exchange Administrator permissions
• you know the room mailbox address, for example [email protected]
• your computer can connect to Exchange Online PowerShell

Where to open Exchange Online PowerShell on Windows

You do not need a separate desktop application called “Exchange Online PowerShell”.

On Windows, you can simply open:

• PowerShell
• or Windows Terminal

Then load the Exchange Online module inside it.

If PowerShell blocks script execution, run:

Set-ExecutionPolicy -Scope CurrentUser RemoteSigned

Step-by-step instructions

Install-Module -Name ExchangeOnlineManagement -Scope CurrentUser

Connect-ExchangeOnline -UserPrincipalName your-[email protected]

How to verify after the change

Recommended verification steps:

1. Create a new Feishu, DingTalk, Tencent Meeting, or other third-party meeting invite.
2. Invite the room mailbox.
3. Wait for the room mailbox to auto-accept the meeting.
4. In VCA, confirm:
   • the original meeting title is displayed
   • the room calendar detects the meeting platform correctly
   • the join link can be parsed and shown correctly

Important notes

Existing meetings may not repair themselves

Changing CalendarProcessing does not guarantee that already-processed historical events will recover their original subject and body.

The safest validation method is:

• create a brand-new test meeting
• or resend / recreate the existing invitation

Why Zoom may still appear to work

This does not mean the mailbox is configured correctly.

In many cases, Zoom also stores the join link in the location field, so VCA may still find it even when the body is removed.
Feishu, DingTalk, Tencent Meeting, and other third-party providers usually depend more heavily on the invitation body, so they are affected sooner when DeleteComments is enabled.

Why organizer mailbox fallback should only be a fallback

In some environments, VCA can use iCalUId to look for the same meeting in the organizer mailbox and read the original body as a fallback.

That should not be the primary path because:

• organizer mailbox access may not always be available
• permissions may be incomplete
• the organizer copy may not remain accessible forever

The recommended long-term fix is always to keep the room mailbox copy intact.

References