Smart Buildings - Meeting subjects not being shown in Smart Buildings

Created by Tim Kefford, Modified on Mon, 18 Aug at 1:25 PM by Tim Kefford

A summary of the issue. You're:

  • Using Exchange 365 Room Mailboxes.
  • Booking meetings by inviting the Room as a Participant/Room Resource.
  • Seeing only the Organiser’s name as the Subject on the Door Panel.
  • When creating meetings directly in the Room mailbox calendar, the Subject appears correctly.
This is expected behaviour due to default mailbox settings in Exchange Online that restrict what is shown in meeting requests for Room mailboxes. Microsoft hides the subject and replaces it with the organiser's name by default, for privacy reasons.

Exchange Resource Mailboxes (like Room mailboxes) have these default settings:
  • AddOrganizerToSubject: True
  • DeleteSubject: True
This means:
  • The original Subject is deleted.
  • The Organiser's name is inserted as the Subject.
Attached are two PowerShell scripts that will resolve this (you can rename them from .txt to .ps1). These scripts do the following:
  • Update_a_Room_Resource_to_show_Subjects - this will allow you to run the script against a specific Room Resource for testing. You will need to update the variable 'roomname@yourdomain.com' to the room to be changed.
  • Bulk_update_Room_Resources_to_show_Subjects - this script will update all Room Resources to share the Subject of their bookings.
Please note that in both the scrips you will see 'youradmin@yourdomain.com'. You will need to change this to the Exchange Administrator user who will run the updates.

Please have these scripts reviewed by your technical team first before implementing them. All the changes can be easily reversed by simply changing $true to $false, and $false to $true in the scripts.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article