10 docs tagged with "Exchange"

When a resource is added to the Dime.Scheduler Exchange connector - by the administrator or automatically by the scheduled resource synchronization job - the system creates a user account for that resource. There are two user account types in the connector resources will be assigned to a resource user account.

The Exchange connector is able to handle both message flows between Dime.Scheduler and Microsoft Exchange. The technology that enables this two-way communication is the Microsoft Graph API, which is the gateway to data and intelligence in Microsoft 365. The Dime.Scheduler Exchange connector uses this technology and applies its own rules and logic to ensure events in the planning board in Dime.Scheduler are kept in sync with events in the Outlook calendars of the resources, and vice versa.

Link Dime.Scheduler category to Outlook category

Dime.Scheduler Exchange setup

This article is concerned with the message flow from Dime.Scheduler to Exchange.

The Dime.Scheduler Exchange connector - unsurprisingly - provides a link between Dime.Scheduler and Exchange. Using the Azure development platform that connects the various systems and data stores across Microsoft 365, appointments of connected Exchange calendars can be kept in sync with the planning in DIme.Scheduler.

This article is concerned with the message flow from Exchange to Dime.Scheduler.

The process to get the integration between Dime.Scheduler and Exchange running isn't overly complicated. Basically, it boils down to the creation of an Microsoft Entra ID App Registration, and copying certain values in the Exchange setup pages in Dime.Scheduler.

To connect Dime.Scheduler to Microsoft 365 and other Azure resources, the administrator needs to grant Dime.Scheduler access to the organization's data on Microsoft 365. In Microsoft Entra ID, this is done with so-called "application registrations". With such registrations, administrators can define what an application is allowed to do. It makes perfect sense to only allow the least permissive permission set and nothing more to prevent potential security leaks.

A powerful rules engine allows fine-grained rules which appointments should be synchronized with Exchange.