Why some Display features require the Application Impersonation Role

Note: This article applies to Microsoft Exchange Server (on-premises and hybrid setups) only. Exchange Online customers connect to AskCody through Microsoft Graph, which uses application permissions instead of a service account. Read more in How AskCody integrates with Microsoft Exchange or go directly to How to upgrade your Exchange Online integration to Microsoft Graph.

We require Application Impersonation to make sure that changes made to the meetings from the screen are reflected in the calendars of the meeting's attendees and resources. On Exchange Online though, AskCody connects through Microsoft Graph, and the Displays booking features are covered by the Calendars.ReadWrite application permission. No impersonation role is needed. See Permissions used and required connecting AskCody with MS Graph and Entra ID.

In Exchange Server, the meeting organizer must be the one making the change. Changes are made as follows:

Book meeting from the screen

The meeting is added directly to the meeting room's calendar. If the meeting starts immediately, it is automatically confirmed.

Cancel meeting

Either manually before the meeting has begun or automatically if the meeting is not confirmed in time: The meeting room is removed from the meeting's resources/attendees unless the meeting room itself is the organizer, in which case the meeting is canceled.

Confirm meeting

No changes are made in Exchange.

End meeting

The end time of the organizer's meeting is set to the current time plus 1 or 2 minutes. This is done to prevent Exchange from rejecting the meeting update, which would cause the meeting to be removed from the meeting room calendar.

Extend meeting

The end time of the organizer's meeting is increased by the duration specified.

In all cases, meeting updates are sent to all attendees and resources to ensure that their respective calendars reflect the changes made.