Set up calendar sync

Choose source, destination and direction

A sync connection relates selected calendars. A one-way connection copies the permitted representation from source to destination. A two-way connection requires a supported, writable calendar on each side. An ICS feed can be a source, never a writable destination.

Start with a dedicated pair of test calendars. Identify the original calendar for each event before deciding how you want information to flow. Avoid overlapping connections that copy the same source into the same destination without a clear reason.

Choose what travels

Select the permitted content level for the connection. Busy-only is appropriate when the destination only needs to know that a time is occupied. More detail requires both your choice and the workspace policy to allow it. Synchronizing a work calendar into a personal destination can be limited by organizational policy.

Verify one event lifecycle

1. Create one recognizable test event in the source, with no guests.
2. Wait for processing and confirm the expected representation in the destination.
3. Change its time at the source and check the copy.
4. Delete the test source event and verify the resulting behavior for that connection.

The processing path depends on provider notifications, polling, queues and provider availability. Do not assume an immediate update or a universal latency guarantee.

Operate an existing connection

Use pause/disable and the connection’s current status before changing a live setup. Stopping a connection and deleting copies are different operations; read the specific confirmation before proceeding. Do not manually edit a managed copy to test whether it is independent. See sync troubleshooting.