For example, the default permissions can be set to Free/Busy time: This changes the free/busy information that is shared for all remote users. If a remote user must be able to see free/busy information for the mailbox, the mailbox owner can work around this issue by changing the default permissions to Free/Busy time or Free/Busy time, subject, location. This is because neither kind of permission offers any level of free/busy visibility.
If the default permissions are set to None or Contributor, no free/busy information is displayed for remote users, and users cannot view the mailbox calendar. The default permissions determine the kind of free/busy information that users in a remote forest can see. In a hybrid deployment, free/busy and calendar-sharing functionality work differently than when both users are in the same environment. When the default permissions of the Calendar folder are set to None or Contributor, details can be obtained only when user delegation is used by attaching calendars directly to the calendar view of Outlook. Therefore, it can't process an explicitly granted permission such as "Free/Busy time" or "Free/Busy time, subject, location." Workaround The organization relationship links to the default account that is seen in the calendar permissions. Scheduling Assistant makes cross-forest requests on behalf of the organization relationship instead of on behalf of the user who is requesting it. When you query free/busy information by using Scheduling Assistant in a cross-forest scenario, the Availability service uses the organization relationship instead of delegated user permissions.
The default permissions of the Calendar folder are set to None or Contributor. After a mailbox is moved to Microsoft 365, an on-premises user can't see the free/busy information for the mailbox in Scheduling Assistant.Īlso, the user can no longer view the Calendar folder, and the user receives a "Could not be updated" error.
0 kommentar(er)
