Microsoft Outlook Busy Sync Settings

https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app

Prerequisite: These settings can be configured only for institutions which use Outlook 365 with mailboxes on Microsoft Exchange Online.

Institutions can configure these Outlook Busy Sync settings with the Staff Calendar feature to check for conflicts in a staff member's official Outlook calendar. This verification prevents a scenario where multiple appointments will be booked at the same time. For more information, see:

  • Steps 1 - 11 must be performed to create an application registration in the Azure Active Directory and must be performed by an institution's Outlook / mailbox administrator.
  • Step 12 must be performed by an Anthology Reach DevOps professional or a Professional Services team member after receiving a request from the institution to implement the staff calendar feature along with a mechanism to check for conflicting appointments.
  1. Using admin credentials, login to https://aad.portal.azure.com/.

  2. Navigate to Azure Active Directory.
  3. Navigate to App Registrations > New Registrations.
  4. Enter the name, for example EngageApp, and then click Register.

    The EngageApp will be registered. Make a note of the Application (client)ID.

  5. To configure Certificates & secrets, select Certificates & secrets > New client secret.
  6. Provide a description for the secret, and set the expiry. When done, click Add.

  7. After saving the client secret, its value will be displayed. Copy the value because you won't be able to retrieve the key later. You will need to provide the key value with the application ID to sign in to the application. Store the key value where your application can retrieve it.
  8. To configure permissions, select API Permissions > Add a permission.
  9. Select Microsoft Graph under Microsoft APIs.
  10. Select Application permissions > Calendars.Read and then click Add permissions.
  11. You will be required to grant admin consent. If you have admin permissions, click Grant admin consent > Yes.

    Permissions will then be granted.

  12. This step must be performed by a DevOps professional. Configure the CMC_GraphAppClientId and CMC_GraphAppClientSecret keys value in the Azure App Service with the Application (client) ID from step 4 and client secret from step 7.

Note: For more information see Microsoft documentation.