This guide provides step-by-step instructions for configuring an on-premise or hosted version of Microsoft Exchange to integrate with GOGET using the EWS (Exchange Web Services) API.
We support two access methods for room resource calendars:
Delegated Access (recommended) - The simplest setup, requiring only the Service Account user to have permission to access the room resource calendars.
Impersonation Access (advanced) - Offers the best performance for organizations managing 15+ rooms. Requires setting up access and permissions using PowerShell.
Applies to: Exchange Server 2013/2016/2019
This article covers:
Step 1: Add a service account
Service account is an account in Exchange with its own mailbox and FullAccess permission to the room resources (ie the meeting rooms). It is used by GOGET to access booking information and can either be an existing user or a new account.
- Access your Exchange Admin Center with an admin account.
- Add a regular user which will act as service account for the integration. We recommend an email which is easily identifiable like goget@domain.com.
- Make sure it's licensed for AT LEAST email access.
- Note! you can use an existing user account as the service account if preferred.
Step 2: Choose an access method
Option 2A: Delegated Access (Recommended)
- In the Exchange Admin Center go to “Recipients -> Resources” in the main menu.
- Add or edit room resource calendars to match your organization’s meeting spaces.
- Double click on one of the room resources that will be synced with GOGET and under “mailbox delegation -> Full Access” add the Service Account and then press "Save".
- GOGET uses delegated access which means that the platform can only access information for room resources which the service account has explicit permission for.
- Note that it may take several hours for permission changes to propagate.
Option 2B: Impersonation Access (Advanced)
- Follow this guide: https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-configure-impersonation to configure impersonation access for the service account.
What's next: