Calendar Data Source FAQ

How to Choose the Right Calendar Data Source?

SyncSign supports multiple calendar data sources. You can choose the appropriate one based on your environment and requirements:

Calendar Data Sources

Data Source Type	Use Case	Deployment Method	Notes
Google Calendar	Personal or small teams	Cloud (SaaS) / On-Premise (SOPS)	Easy to configure
G Suite	Enterprise Google Workspace	Cloud (SaaS) / On-Premise (SOPS)	Supports organization management & resources
Office 365	Microsoft 365 users	Cloud (SaaS) / On-Premise (SOPS)	Supports organization management & resources (Delegated & App auth)
Exchange Server	On-premise Exchange deployment	On-Premise (SOPS)	Requires SOPS server
NextCloud	Self-hosted CalDAV server	On-Premise (SOPS)	Requires SOPS server
CSV URL	Custom data source	On-Premise (SOPS)	Requires SOPS server

Note

• Cloud deployment (SaaS): Suitable for most users, simple configuration, no local server required

• On-premise deployment (SOPS): Suitable for enterprises with special data security requirements, all data stays within the corporate network

Office 365 Related Issues

Microsoft 365 Compatibility

Which Microsoft 365 licenses are supported?

SyncSign is designed to integrate seamlessly with standard Microsoft Business solutions. We support most commercial plans, including but not limited to:

• Microsoft 365 Business Basic

• Microsoft 365 Business Standard

• Microsoft 365 Business Premium

As long as your organization uses a standard commercial environment, SyncSign can integrate with your Exchange Online calendars.

Does SyncSign support Microsoft GCC High?

No. Currently, SyncSign does not support Microsoft GCC High (Government Community Cloud High) environments.

Note: GCC High uses a separate architecture designed for strict government compliance, which is incompatible with our standard integration.

Can I use a personal Microsoft account?

Yes! SyncSign offers free support for individual users. If you are using a personal Outlook.com or Microsoft account (non-business), you can still integrate it with SyncSign devices at no cost.

Room/Calendar Not Appearing in SyncSign Client

1. Verify Calendar Access and Delegate Settings

Please confirm that the Microsoft 365 account you use to sign in to the SyncSign client has management access to the calendar that is not appearing.

• For a regular user calendar:

  Run the following PowerShell command to check permissions:

  Get-MailboxFolderPermission -Identity "[email protected]:\Calendar"
  

  Check if the SyncSign integration account appears in the permission list with at least Editor access.

• For a room resource calendar:

  Run the following PowerShell command to check permissions:

  Get-MailboxFolderPermission -Identity "[email protected]:\Calendar"
  

  Ensure the SyncSign account has Editor or Delegate permissions.

  Note

  If you are using Application permissions (Global Admin mode in SyncSign), the service account must have tenant-wide admin consent to access room/resource mailboxes.

2. Check Outlook Calendar Grouping (My Calendars vs Other Calendars)

SyncSign retrieves calendars through the Microsoft Graph API. When using Delegated User mode, if your integration only enumerates the default calendar group (“My Calendars”), shared or room calendars located under Other Calendars may not appear. This is an API visibility limitation, not a permission issue.

Options to fix:

• Option A (recommended for admins): Use Application permissions

  Access the room’s calendar directly using its mailbox address. This method does not depend on Outlook grouping.

  GET https://graph.microsoft.com/v1.0/users/{roomMailbox}/calendar/events
  

• Option B (for Delegated User mode): Make sure the calendar is under “My Calendars”

  • In Outlook Web or Desktop → go to Add calendar → From directory

  • Search for the target calendar (user or room resource)

  • In the Add to dropdown, select My Calendars (not “Other Calendars”)

  • If the calendar was previously added under “Other Calendars”, remove it and re-add it under My Calendars

  • Go back to the SyncSign client and re-login to Microsoft 365 to trigger synchronization

  Warning

  Moving a shared or room calendar to “My Calendars” helps only for Delegated User mode. In Global Admin mode (Application permissions), this step is not required. If you are unsure which authorization mode is currently active, try switching modes in SyncSign and re-login to test visibility.

Recommended Investigation Order:

1. Check calendar/room resource permissions – ensure the SyncSign account has at least Editor or Delegate permission.

2. If using Delegated User mode, ensure the calendar is under “My Calendars”, or update the Graph API integration to enumerate all calendar groups (/calendarGroups).

3. If using Global Admin mode, verify that tenant admin consent has been granted for Application permissions.

4. Re-authorize and sign in to your Microsoft account in the SyncSign client, then trigger synchronization to verify whether the calendar appears.

Summary:

• Calendars under “My Calendars” are the most reliably discoverable in Delegated User mode.

• Room/resource calendars can always be accessed directly via Application permissions (Global Admin mode), regardless of Outlook grouping.

• Moving a calendar to “My Calendars” is a helpful workaround, not a strict requirement.

Display Synchronization Refresh Failure

1. Check Microsoft 365 Account Permissions

The Microsoft 365 account used to authorize login in the SyncSign client may have lost management permissions for the calendar (room resource) bound to the Display.

Troubleshooting steps:

1. Go to the SyncSign client and navigate to the Display configuration page

2. Unbind the Display from the calendar

3. Re-bind the Display to the calendar

Expected results:

• If binding succeeds: Observe whether the Display can synchronize and refresh the calendar information

• If binding fails: Please contact us and provide error screenshots for further troubleshooting and analysis

2. Integration Failure Due to Client Secret Expiration (SOPS Deployment)

The most common reason is that the Client Secret for the Azure App has expired. Once this date is reached, Microsoft rejects connection requests from SyncSign, causing the synchronization to fail.

Fix (typically takes only 5 minutes):

1. Log in to the Azure Portal and locate the specific App

2. Generate a new Client Secret

3. Immediately copy the new Secret Value and update it in your SOPS system configuration settings

4. Once saved, the integration will be restored immediately

Event Title Shows Organizer Name Instead of Event Subject

By default, Office 365 room resources are configured to display the organizer’s name instead of the actual event title. This means SyncSign displays may show the organizer’s name rather than the meeting subject.

Solution:

Please refer to: Modify the Settings of the New Room Resource

This document provides step-by-step instructions on how to modify the room resource settings using PowerShell or Azure Cloud Shell to ensure event titles are preserved and displayed correctly on SyncSign displays.

Other Issues

If the above solutions do not resolve your issue, or if you need additional assistance, please feel free to contact us:

• Website: https://help.sync-sign.com

• Email: help@sync-sign.com