Jan 15 2020
04:13 AM
- last edited on
Apr 04 2022
07:26 AM
by
TechCommunityAP
Jan 15 2020
04:13 AM
- last edited on
Apr 04 2022
07:26 AM
by
TechCommunityAP
Calendar sharing.
How can I set the default permissions of calendar sharing within my organization so that everyone "can view all details" of everyone else?
Setting default sharing policy in Exchange 365 only affects sharing with external organizations if I'm not mistaken, so have do I control it for the internal organization? I have nonetheless tried adding our internal domain there as well, to no avail.
Surely there must be a way to control default calendar sharing permissions within ones own organization?
The other option is to use powershell on some schedule to maintain sharing permissions for all our users, but that would be a more inconvenient solution.
Jan 15 2020 04:25 AM
Jan 15 2020 09:06 AM
Just to confirm what Adam said above, PowerShell is your only option here. And you have to run it periodically if you want to include any newly created users.
Jun 10 2022 09:35 AM - edited Jun 10 2022 09:37 AM
I am so surprised to find that I can control the default sharing experience of calendars with people outside the organization but not *within* the organization.
This means that if I have two organizations working closely together then I can set the default to be 'Can view titles and locations' and each organisation can see this level of detail in each other's calenders - but the co-workers in the same organization will only see free-busy. Unless, that is, each person manually changes the 'Inside your organization' sharing permission - or we have a PowerShell script run on a periodic basis to change people's internal sharing permission (with the attendant complexity of those people who have a legitimate reason to be excluded from the script making the change).
It seems like a significant oversign in the abilities of the Exchange Admin Center and sharing permissions. Does anyone know whether this is on the roadmap? (I wasn't finding many useful hits when I searched for the answer - which is why I've ended up here.)
Feb 14 2023 11:56 AM
Apr 11 2023 12:45 AM
Jul 10 2023 03:09 PM