Integrating GOGET with your calendar system ensures seamless synchronization with room resource calendars.
This article covers:
- Select your calendar provider
- Microsoft 365 Integration Guide
- Exchange Server 2013/2016/2019 Integration Guide
- Google Workspace Integration Guide
Select your calendar provider
Click the calendar platform used by your organization to begin:
Microsoft 365 Integration Guide
Step 1. Configure Microsoft 365
- Follow this setup guide: Guide: configure Microsoft 365
Step 2. Add integration in the admin dashboard
- Go to "Manage -> Calendars" in the main menu.
- Press "Add integration" to launch the wizard.
- Choose "Microsoft 365 + Teams".
- Press "Sign in with Microsoft".
- Log in with your service account user. Don’t have one? See this guide.
-
(If applicable) If prompted for admin approval (based on Entra ID settings), contact your Microsoft 365 admin or submit a support request.
- Review and accept the permissions requested by GOGET. Note that the integration uses Delegated permissions which means that only resources specifically granted permission to are accessible.
- Once connected, click on the integration in the list view to verify configuration. If you experience issues, see this article: Troubleshooting: Microsoft 365 integration
- When Microsoft 365 is correctly configured all room resource calendars are listed in the view.
What's next:
Exchange Server 2013/2016/2019 Integration Guide
Step 1. Configure Exchange
- Follow this guide to prepare your Exchange environment: Guide: configure Exchange 2013/2016/2019
Step 2. Add integration in the Admin Dashboard
- Go to "Manage -> Calendars" in the main menu.
- Press "Add integration" to launch the wizard.
- Choose "Exchange EWS".
- Fill in the required information:
- Name: Display name in GOGET (doesn’t have to match Exchange).
-
Exchange EWS URL: For on-premise Exchange servers the communication is by EWS (Exchange Web Services) protocol which is supported by all Exchange servers from version 2007 and newer. Microsoft 365 will not work with EWS.
Enter the EWS URL for your Exchange server in order for Room Display to connect. It must be the full URL, for example: https://mail.company.com/EWS/Exchange.asmx
Don't know your EWS URL?
-Check this article: Determining the Exchange Web Services (EWS) URLCommon error is using the Outlook Web Access URL:s that contains: /OWA/ (instead of /EWS/). This will not work.
-
Service account username: Service account is an account in Exchange with its own mailbox and FullAccess permission to the Room Resources. It is used by Goget to access booking information in your Room Resources.
-If your organization uses NETBIOS style (e.g. DOMAIN\Username), then enter in format “domain\username”.
-If your server requires NTLM authentication, the NETBIOS style format must be used. -
Service account password: Enter the Service account password.
-
Use Exchange impersonation (advanced): Enable this option to activate the impersonation access method.
- If you get an error code when clicking "Create", see this article: Troubleshooting: Exchange 2013/2016/2019 integration
- Once connected, click on the integration in the list to verify setup.
- The integration is now finished! For adjustments of the configuration see "Settings" tab.
What's next:
Google Workspace Integration Guide
Step 1. Configure Google Workspace
- Follow this guide to prepare your Google environment: Guide: configure Google Workspace
Step 2. Add integration in Admin Dashboard
- Go to "Manage -> Calendars" in the main menu.
- Press "Add integration" to launch the wizard.
- Choose "Google Workspace".
- Log in using your service account.
- Review and accept the requested permissions. Note that the integration can only access resources which the service account has been specifically granted permission to.
- Once the integration is added, click on the name in the list view. If you experience issues, see this article: Troubleshooting: Google Workspace integration
- When Google Workspace is correctly configured all room resource calendars are listed in the view.
What's next: