How to Set Default Calendar Sharing Permissions for an Organization
Question details
The organization needs a way to configure internal calendar sharing permissions for all employees so they can automatically view availability, subjects, times, and locations of their colleagues' events.

- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- Automating internal calendar visibility across all mailboxes so users do not have to manually share their calendars with the rest of the company.
- Observed behavior
- Without central configuration, each user's calendar permissions remain restricted by default, requiring them to manually configure their mailbox folder settings for others to see meeting details.
Ensure you have the Exchange Online PowerShell module installed and that your account holds the necessary Exchange Administrator permissions to modify mailbox folder settings.
Set Calendar Permissions Using Exchange Online PowerShell
Use PowerShell commands to automate the assignment of default calendar permissions for all user mailboxes across the organization.
This method updates the 'Default' user permissions on the calendar folder of internal mailboxes. This ensures that any authenticated internal user can view calendar details according to the access rights you specify, without affecting external sharing policies.
Open your PowerShell terminal as an administrator and run the command `Connect-ExchangeOnline` to log in with your administrative credentials.
To test the permission on one user, execute `Set-MailboxFolderPermission -Identity "user@yourdomain.com:\Calendar" -User Default -AccessRights LimitedDetails`. This grants internal users access to view availability, subjects, and locations.
To apply this organization-wide, first fetch all standard mailboxes by running `$Mailboxes = Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited`.
Run a `foreach` loop to process the retrieved mailboxes: `foreach ($Mailbox in $Mailboxes) { $Calendar = $Mailbox.PrimarySmtpAddress + ":\Calendar"; Set-MailboxFolderPermission -Identity $Calendar -User Default -AccessRights LimitedDetails }`.

Create a Calendar Group for Selected Users
If you only need a specific group of users to share detailed free/busy information rather than the entire organization, configuring a calendar group is more efficient.
Manage Your Documents and Schedules with WPS Office
While Microsoft Exchange manages complex organizational email and calendar routing on the backend, WPS Office provides a free, lightweight, and user-friendly alternative to Microsoft Office for your daily productivity needs. Enjoy seamless format compatibility and built-in scheduling templates.
- 1. Download the Installer: Navigate to the official WPS Office website and download the free installation package tailored to your Windows, Mac, or Linux operating system.
- 2. Install the Software: Run the downloaded executable file and follow the simple on-screen prompts to complete the installation in minutes.
- 3. Access Free Templates: Launch WPS Office, open the Template library from the home screen, and search for 'calendar' or 'schedule' to instantly start organizing your team's workflow.

Frequently Asked Questions
Does setting the 'Default' calendar permission expose details to external users?
No. The 'Default' user parameter in the Set-MailboxFolderPermission cmdlet applies strictly to internal, authenticated users within your Exchange organization. External sharing is governed separately by your organization's sharing policies and federated trust settings.
What does the 'LimitedDetails' access right specifically reveal?
The LimitedDetails access right allows internal users to see the availability (Free/Busy status), the subject of the meeting, and the location. It keeps the actual body text and attachments of the calendar events private.
Can I apply these settings based on a user's department?
Yes. When retrieving mailboxes using Get-Mailbox, you can pipe the results to a Where-Object filter based on the department attribute. This allows you to run the Set-MailboxFolderPermission loop exclusively on users within a specific department.
Why did my PowerShell command fail with an 'item already exists' error?
If you receive an error stating the permission entry already exists, it means the Default user already has explicitly defined access rights. In this case, you should use the Set-MailboxFolderPermission cmdlet instead of Add-MailboxFolderPermission to overwrite the existing setting.




