Documentation Index

Fetch the complete documentation index at: https://documentation.sysaid.com/llms.txt

Use this file to discover all available pages before exploring further.

Syncing the SysAid Calendar with Microsoft or Google

Prev Next

Calendar Sync connects your organization's SysAid calendar to Outlook (Microsoft 365) or Google Calendar, so service record due dates, activities, and SysAid events show up in the calendar your team already uses. Synchronization is one-directional: SysAid exports data out, and nothing is imported back from Outlook or Google.

Available for:

Customers using SysAid Spaces. If you're using SysAid Classic, see Calendar Sync.

Setting this up has two parts:

  1. Connect SysAid to your provider (below). This is a one-time, organization-wide setup, done once by whoever manages your integration settings.

  2. Each admin turns on sync for their own account. This is covered in Configuring Calendar Settings, and requires step 1 to already be in place.

General setup fields

  1. Navigate to Settings > Setup > Calendar Sync, then fill out the following fields.

Field

Description

Protocol

Select OAuth 2, EWS, or MAPI as the protocol for integration with your external calendar.

Exchange Server Name

The name or IP address of the computer that hosts your calendar. Not used for OAuth 2.0.

Network domain name (NetBIOS)

Your network domain name. Not used for OAuth 2.0.

Username

The Exchange, O365, or Google account used for synchronization. For Exchange, this account needs permission to create events on employees' Outlook calendars.

Password

The password for that account.

Sync user email address

The account's email address.

Please note:

If your company uses multiple email domain formats (e.g., @sysaid.com, @internal.sysaid.com), use the email address with the most common format. Any user whose email uses a different domain won't be able to sync their calendar.

  1. Once configured, check the Enable Synchronization checkbox on this page to make sync available to all admins. Each admin still needs to turn on sync for their own account separately, in Configuring Calendar Settings.

  2. Click Test Exchange Settings to confirm SysAid can connect using the credentials you've supplied.

  3. Click Save.

Setting up OAuth 2.0 with Microsoft 365

  1. From the Protocol drop-down, select OAuth 2.0, then select Microsoft 365.

  2. Register your application in Entra ID:

    1. In your Microsoft 365 account, navigate to Entra ID > App registrations.

    2. Click New registration, name your application, select the single tenant option, optionally select a platform configuration, then click Register.

  3. Create a client secret: in App registrations > Certificates & secrets, click New Client secret, enter a description, set Expires to Never, click Add, then copy the generated secret into the Client secret field back in SysAid.

  4. Set up API permissions:

    1. In API permissions, click Add a permission > Microsoft Graph > Delegated Permissions, then check User.Read.

      Checking the User.Read permission

    2. Click Add Permissions, then click Application Permissions and check Calendars.ReadWrite, Mail.ReadWrite, Mail.Send, and User.Read.All.

    3. Click Application Permissions > Grant admin consent for <domain name> > Yes.

  5. Copy the Tenant ID and Client ID: in App registrations, select the app you just created, then copy the Application (client) ID and Directory (tenant) ID into the matching fields in the SysAid calendar sync form.

    Copying the tenant and client IDs

  6. Fill out the rest of the calendar sync form as described in General setup fields above.

Setting up OAuth 2.0 with Google

  1. From the Protocol drop-down, select OAuth 2.0, then select Google.

  2. Create a project in the Google Cloud Platform Console: click Select a project > New Project.

  3. Enable APIs: in APIs & Services > Library, search for and enable Gmail API and Google Calendar API.

  4. Create a service account: in Credentials, click Create Credentials > Service Account, name it, and click Create. On the permissions page, set the Project role to Owner.

    Setting the Owner role on the service account

  5. Configure the OAuth consent screen: click OAuth consent screen > Internal > Create, name the application, then click Add Scope and add both https://mail.google.com/ and https://www.googleapis.com/auth/calendar.

  6. Generate a JSON credentials file: open your service account, check Enable G Suite Domain-wide Delegation, click Add Key > Create new key > JSON > Create, and save the file.

    Enabling domain wide delegation

  7. Configure the Google Admin console (admin.google.com):

    1. Under Security > Advanced settings > Manage Google Services, confirm Gmail and Calendar are unrestricted.

      Confirming Gmail and Calendar are unrestricted

    2. Under Manage Third Party App Access > Configure new app, find your app by its client_id value, select both Client ID checkboxes, and set access to Trusted: Can Access All Google Services.

      Configuring third party app access

    3. Under Manage Domain-wide Delegation > Add New, enter the client_id and both OAuth scopes from your JSON file, then click Authorize.

  8. In SysAid, paste the client_id value into Service Account and the private_key value into Private Key.

  9. Fill out the rest of the calendar sync form as described in General setup fields above.

Next steps

Enabling sync here makes it available, but each admin still needs to turn it on for their own account before their calendar actually syncs. See Configuring Calendar Settings.