Integration with Microsoft Exchange

AskCody + Microsoft Exchange

AskCody is built native to Microsoft Exchange. Meeting rooms, desks, and bookings in AskCody are based on the resource calendars in your Exchange environment, and everything AskCody shows and updates flows through that integration. This article gives IT Admins the overview of how the integration works and where to go for setup, security, and troubleshooting.

Integrating the AskCody Meeting Management Platform with your Microsoft Exchange Server or Exchange Online tenant (Office 365) is an important and key step in setting up AskCody. Therefore, it’s highly recommended that you spent some time understanding Microsoft Exchange, and how AskCody integrates with Exchange. This will help you understand the requirements when the integration between Exchange and AskCody will be established.

Exchange Online: Microsoft Graph

For Microsoft Exchange Online, AskCody connects through Microsoft Graph, the API Microsoft provides for working with Microsoft 365 data. Your Microsoft 365 administrator grants consent to the AskCody enterprise application once, and no service account, password, or EWS URL is stored or shared with AskCody.

The integration uses four application permissions, documented in Permissions used and required connecting AskCody with MS Graph and Entra ID: Calendars.Read, Calendars.ReadWrite, GroupMember.Read.All, and User.Read.All. Compared to the earlier EWS model, this is a narrower grant: AskCody has access to calendars, not full mailbox content.

Microsoft is retiring Exchange Web Services (EWS) for Exchange Online. Microsoft begins blocking EWS requests on October 1, 2026, and removes EWS permanently on April 1, 2027. If your Exchange Online integration was set up before July 2026, read How to upgrade your Exchange Online integration to Microsoft Graph.

• Setup: Integrating Microsoft Exchange with AskCody
• Granting consent: How to Grant Enterprise Application Permissions to AskCody in Azure
• Restricting access to specific mailboxes: Limiting which mailboxes AskCody can access in Exchange Online

Exchange Server: Exchange Web Services (EWS)

For Exchange Server (on-premises and hybrid setups), AskCody connects through Exchange Web Services (EWS), a native part of Microsoft Exchange. EWS must be enabled and reachable for AskCody. The integration authenticates with a service account, which requires the ApplicationImpersonation role.

• Requirements: Requirements and Recommendations on Microsoft Exchange
• Service account: Create a service account using PowerShell
• Why impersonation: Why Basic Authentication requires Application Impersonation
• Hybrid setups: How to handle Hybrid Exchange Setups

What the integration does, regardless of environment

• Reads the resource calendars you connect, so bookings appear in AskCody in real time.
• Updates calendars when meetings are booked, rescheduled, extended, or ended from AskCody products like Central, the Outlook Add-ins, and Room Displays.
• Follows the meeting when it moves: service requests and visitor pre-registrations stay attached to the meeting when it is rescheduled. Read What is "follow the meeting intelligence"?.

Learn more

These articles highlight the overall concept of integrating AskCody with Microsoft Exchange.

• Understanding Microsoft Exchange and AskCody
• Integrating Microsoft Exchange with AskCody

• Requirements and Recommendations on Microsoft Exchange

The articles cover topics like:

• How AskCody integrates with Exchange
• How AskCody integrates with Exchange Meeting Room Resources
• What meeting data is accessible in Microsoft Exchange and what data AskCody process
• How to set up booking policies and scheduling permissions to comply with business policies and procedures
• How to integrate with Exchange using Basic Authentication or Modern Authentication (OAuth 2.0)

Further helpful reading on AskCody and Microsoft Exchange is:

• Basic Authentication vs. Modern Authentication and how these two types of authentication are different
• The difference between Impersonation and Delegation, and why Impersonation is required with AskCody
• Scoping Application Permissions with ApplicationImpersonation (Management Scope)

These articles go through important topics and highlight some frequently asked questions on AskCody and Microsoft Exchange in terms of security matters:

• Why ApplicationImpersonation is needed with Basic Auth and how ApplicationImpersonation is secure for application-level mailbox access.
• How audit logging and audit trails for a Service Account with Basic Auth can be managed for security purpose
• What the difference between Basic and Modern Auth is, how and when each should be used
• Who can use Modern Authentication instead of Basic Authentication
• Why using Modern Authentication requires a Global Admin account with a Mailbox authenticating the account the first time you sign up
• Why full access to mailboxes are needed with Modern Auth (OAuth 2.0)
• How to set up Application Scoping to limit Application Access (Management Scoping) for managing security levels with Microsoft Exchange