Skip to Main Content
You are now in the main content area

Events and Windows 10 Visibility Issue in Google Calendar

If you are syncing your Google calendar using the Calendar App in Windows 10 (for both mobile devices such as Surface and desktop computers), please be aware that for any event that you create or update using the Windows 10 Calendar Application, the event’s visibility will be set to “public” regardless what visibility option it was set to before.

If your calendar isn’t shared with anyone, this is not an issue, since your calendar isn’t shared with anyone, so your events aren’t either. This will however become an issue when you change the calendar’s sharing settings.

Implications of Sharing Calendar with Others

  1. If your calendar is shared with specific people and they see only free/busy, events that are default or private will become public. People will be able to see all event details.
  2. If your calendar is shared with specific people and they see all event details, events that are private will become public. People will be able to see all event details.
  3. If your calendar is made public and people can can see only free/busy, events that are default or private will become public. Anyone can see all event details.
  4. If your calendar is made public and people can can see all event details, events that are private will become public. Anyone can see all event details.

Google Calendar Events are Public in Windows 10

By default, TMU employees' primary calendar is shared with other employees in TMU domain with free/busy information. If you use the Calendar App in Windows 10 and sync with your Google Calendar, any event created or updated with it will be “public” and other employees will be able to see all event details.

Hence, all event details for any events, that were created before with “Default” or “Private” options and are updated via the Calendar App, can be seen by other employees instead of only “busy”.

Please note this appears to be an issue with the Calendar App in Windows 10. Computing and Communications Services is reporting the issue to Microsoft.