Skip to content

Commit d045e45

Browse files
authored
Merge pull request MicrosoftDocs#7700 from MicrosoftDocs/CalSync-chrisda
CalSync-chrisda to Master
2 parents f62231e + fce435a commit d045e45

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

exchange/exchange-ps/exchange/Set-MailboxCalendarFolder.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -283,7 +283,19 @@ Accept wildcard characters: False
283283
### -SharedCalendarSyncStartDate
284284
This parameter is available only in the cloud-based service.
285285

286-
{{ Fill SharedCalendarSyncStartDate Description }}
286+
**Note**: This parameter is supported only for shared calendars that have been upgraded as described in [Calendar sharing in Microsoft 365](https://support.microsoft.com/office/365-b576ecc3-0945-4d75-85f1-5efafb8a37b4), and is not applicable to any other type of calendar or mailbox folder.
287+
288+
The SharedCalendarSyncStartDate parameter specifies the limit for past events that are visible to users who have access to the specified shared calendar. A copy of the shared calendar with events that go back as far as the value specified by this parameter is stored in the user's mailbox.
289+
290+
To specify a date/time value for this parameter, use either of the following options:
291+
292+
- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z".
293+
- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://docs.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
294+
295+
**Notes**:
296+
297+
- Users need to have FullDetails, Editor, or Delegate access to the specified shared calendar.
298+
- Setting this parameter might cause events in the shared calendar to briefly disappear from view while the calendar is resynchronized.
287299

288300
```yaml
289301
Type: DateTime

0 commit comments

Comments
 (0)