'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Can External Users Edit Calendars Across Microsoft 365 Tenants?
Question details
The user is trying to determine if external users from another Microsoft 365 tenant can edit a shared calendar, as assigned editing permissions are failing to work.
- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- An administrator is using Add-MailboxFolderPermission to grant calendar Editor rights to an external user in a different Microsoft 365 tenant.
- Observed behavior
- The PowerShell command succeeds without errors, but the external user remains unable to edit the calendar and may only see an empty calendar or have view-only access.
Ensure you have Microsoft 365 Global Administrator or Exchange Administrator privileges to review organization-wide external sharing policies.
Verify Cross-Tenant Calendar Sharing Limitations
Understand that Exchange Online sharing policies generally restrict cross-tenant calendar access to viewing only, preventing external users from acting as Editors.
In Microsoft 365, cross-tenant calendar sharing policies strictly limit external access for security reasons. Most organizational relationships only support 'Free/Busy' or 'View Only' synchronization.
Even if folder-level permissions are successfully assigned via PowerShell commands like Add-MailboxFolderPermission, the overarching organizational sharing policy will override these settings, effectively blocking editing capabilities for external users.
Log in to the Microsoft 365 Admin Center, navigate to Settings > Org settings, and select Calendar to review your external sharing limits.
Ask the external user to verify if they can at least view the calendar events. If they can view but not edit, the system is functioning within its cross-tenant policy limits.
Recreate Permissions and Clear Outlook Cache
If the shared calendar appears completely empty rather than view-only, reset the sharing permissions and clear the local application cache.
Submit a Microsoft 365 Support Request
Engage Microsoft Support to review your specific tenant configuration and confirm if any backend policy restrictions are causing unexpected sharing failures.
Manage Your Schedules and Documents with WPS Office
While cross-tenant calendar editing in Microsoft 365 is restricted by strict server policies, collaborating on daily office documents shouldn't be complicated. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office, allowing seamless document sharing and editing.
- 1. Download the Installer: Visit the official WPS Office website and download the free version for your operating system.
- 2. Install the Suite: Run the downloaded installer and follow the simple on-screen prompts to set up WPS Office.
- 3. Open Your Files: Launch WPS Office to instantly open, edit, and share your existing Microsoft Office documents without any conversion.
Frequently Asked Questions
Why does the Add-MailboxFolderPermission command succeed if editing isn't allowed?
The PowerShell command successfully modifies the folder-level permissions on the specific mailbox. However, Exchange Online evaluates organizational sharing policies at runtime. The broader cross-tenant policy limits external users to view-only access, effectively overriding the folder permission.
Can I bypass the cross-tenant calendar editing restriction using B2B collaboration?
Currently, even with Microsoft Entra B2B collaboration configured, native calendar editing (Editor role) across different Microsoft 365 tenants is generally unsupported. External users are typically restricted to Free/Busy or full details viewing.
Why does the shared cross-tenant calendar show up as completely empty?
An empty calendar usually indicates a synchronization failure or a policy block. This can happen if an unsupported permission level (like Editor) causes the sharing connection to fail. Removing the permissions, waiting 24 hours, and sharing with 'View' access usually resolves this.
