Enterprise Connect for Office 365 (Graph API)

Microsoft’s Graph API is an alternative mechanism to Exchange Web Services available to organizations using Office 365. It allows integrated conferencing via Microsoft Teams, as well as a simpler setup process for administrators with no need to create a Service Account or configure ApplicationImpersonation.

Follow the steps below to connect your organization calendars to the software provider. This connection process is hosted by Cronofy and it allows us to gain access to your calendar service and broker that access out to your software provider.

Authorizing access #

Your software provider will provide you with a button or link to follow to connect your calendars with their service.

Newly invited users will need to log into Cronofy by clicking on ‘Connect with Office 365’ and use their Office 365 login credentials to join the Scheduler.

If your authorization screen does not look like the above, and only has a single button with no link below, your software provider has not enabled Graph API yet, and you should instead see the documentation for connecting via Exchange Web Services (EWS).

After selecting Link Office 365 Account you will see a screen similar to this.

You should log in as a user with Azure Active Directory Global Administrator access to your Office 365 tenant. This is the minimum level of access you will require to enable Enterprise Connect.

You will see this screen twice; once to confirm your Office 365 tenancy, and then to request the necessary scopes for Enterprise Connect.

Once complete you will be redirected back to your software vendor’s application and they will be able to synchronize your user/resource calendars.

If, after completing the Microsoft authorization flow, you observe a delay before being returned to your vendor’s application in an unsuccessful state, then you may need to retry.

The granted permissions take some time to apply across the entire Microsoft tenant after being approved for the first time, and until they are applied we’re unable to confirm the connection has been successful. We’ll retry for ~15 seconds, but in exceptional cases we’ve observed this taking longer.

If this happens, try the flow again after a few minutes, starting from your vendor’s application. To allow the permissions to propagate, don’t remove the Cronofy Enterprise for Office 365 application from Azure Active Directory between attempts.

Furthermore, the transport rules need to allow for emails with our domain.

Free-busy Access #

Free-busy only access is not available through the Microsoft Graph API, as the Graph API permissions model requires full read access even for free-busy mode. If you wish to restrict access to free-busy only, please use an Exchange Web Services connection.

Enterprise Connect for Office 365 (Graph API)

Authorizing access #

Free-busy Access #

In This Section