Microsoft 365 Cross-Tenant Calendar Sharing: What SMB Admins Need to Know

Why cross-tenant calendar sharing is changing

Microsoft 365 admins who share calendars, free/busy information, or MailTips with people in other organizations — a common setup for SMBs that work closely with partner companies, franchises, or affiliated businesses — are facing two related changes worth understanding separately.

First, Microsoft has been rolling out an improved shared calendar sync model that changes how quickly calendar updates appear across devices and applications. Second, and more urgently for anyone sharing calendars across tenant boundaries, Microsoft is retiring Exchange Web Services (EWS) as the underlying mechanism for some cross-organization sharing configurations, which means those configurations need to be migrated to a newer policy model.

Neither change requires SMB admins to panic, but both deserve a deliberate check of current configurations, because the second change has a real deadline tied to EWS deprecation.

What’s changing with shared calendar syncing

Microsoft has updated how shared calendars sync across Outlook clients and devices. According to Microsoft’s documentation, the improvements include more consistent sharing permission options across Outlook versions, easier acceptance of shared calendar invitations, and calendars that sync to all devices with near-immediate updates — at least in supported scenarios.

Under the new model, when a user accepts a shared calendar, a copy of that calendar is created in their own mailbox rather than simply linking to the owner’s mailbox. Changes are then synced to that local copy, which is what enables faster updates and support for mobile apps.

Instant syncing has limits — especially across tenants

Not every shared calendar configuration benefits from instant syncing. Microsoft’s documentation is specific about this: instant syncing is only enabled when both users are in the same Microsoft 365 tenant, or when the calendar is shared by an Outlook.com user. For calendars shared between users in different Microsoft 365 tenants, the sync happens periodically — approximately every three hours — rather than instantly.

If external sharing isn’t allowed for the calendar owner’s tenant, cross-tenant sharing is treated the same as sharing with a third-party service. In that case, Microsoft generates an Internet Calendar Subscription (ICS) URL instead of a live shared calendar, and the recipient’s own calendar service determines how often it refreshes. Outlook.com recipients using an ICS URL typically see updates roughly every three hours, while third-party services such as Gmail may update less frequently — Microsoft’s documentation notes this can be every 24–48 hours.

In short: cross-tenant calendar sharing today is not instant, and administrators should not expect real-time updates when calendars are shared between separate Microsoft 365 organizations.

Automatic upgrade of existing shared calendars

Microsoft has also been automatically upgrading eligible existing shared calendars — those shared internally within an organization with Editor, Delegate, or Full Mailbox Access permissions — to the newer sync model. According to Microsoft, this upgrade:

• Happens silently in the background with no action required from users or admins
• Preserves existing sharing permissions and relationships
• Retains events from roughly one year prior to the upgrade plus all future events
• Does not require re-sharing or re-accepting calendar invitations

Microsoft notes this rollout happens in phases, and calendars with a very large number of sharing relationships will not be upgraded. Organizations that received Message Center notification MC1287370 about this automatic upgrade can treat it as informational — Microsoft describes it as a background process that doesn’t require IT admin action.

It’s worth noting this automatic upgrade applies to calendars shared within an organization, not to the cross-tenant sharing scenario described above, which continues to rely on periodic syncing or ICS subscriptions rather than the instant-sync model.

The bigger change: migrating away from EWS-based cross-tenant sharing

The more consequential change for SMB admins involves how free/busy information, shared calendars, and MailTips are exchanged between Microsoft 365 organizations. Historically, this cross-organization sharing has relied on three Exchange Online configuration types:

• Organization Relationship — used to share free/busy and MailTips information with a specific external domain
• Availability Address Space — used specifically for sharing free/busy information
• Sharing Policy — used to control how users share calendars with people in other organizations

According to Microsoft’s migration guidance, Organization Relationship and Sharing Policy configurations depend on Exchange Web Services (EWS), which is being deprecated in Exchange Online, and on high-privilege access patterns that Microsoft is retiring in favor of modern authentication. Microsoft states that all its own products, including Outlook, Teams, and Dynamics 365, are removing their EWS dependencies as part of this effort.

Availability Address Space is also part of Microsoft’s migration guidance. For free/busy sharing between two Exchange Online tenants, Microsoft states that only the OrgWideFBToken access method is functional. If an Availability Address Space uses another access method, it can’t be migrated to Microsoft 365 Cross-Tenant Access Policy using this path.

The replacement is the Microsoft 365 Cross-Tenant Access Policy, which Microsoft describes as the new standard for free/busy, calendar, and MailTips sharing between Microsoft 365 tenants. This policy builds on the existing Microsoft Entra Cross-Tenant Access Policy framework, rather than being a completely separate system.

Microsoft’s guidance notes that this migration path is still rolling out and may not yet have reached every tenant. Admins should check their Message Center for tenant-specific rollout information before planning migration work.

Who is affected

This change is relevant to any SMB Microsoft 365 tenant that currently shares free/busy availability, calendars, or MailTips with people in a different Microsoft 365 organization — for example, a partner company, a franchise network, or a related business entity using its own separate tenant. Microsoft’s migration guidance covers Organization Relationship, Availability Address Space, and Sharing Policy configurations used for these scenarios.

Organizations that only share calendars internally, within a single tenant, are affected primarily by the shared calendar sync improvements described earlier, not by the EWS-related migration.

Organizations that don’t share calendars or free/busy information across tenant boundaries at all are unlikely to be affected by the Cross-Tenant Access Policy migration, though it’s still worth confirming this is genuinely the case rather than assuming it.

What administrators should check

Before making any changes, Microsoft’s migration guidance recommends building an inventory of existing cross-tenant sharing configurations using Exchange Online PowerShell. This requires an account with the Organization Management role.

Review existing configurations

Run the following to identify what’s currently configured:

• Get-OrganizationRelationship — lists free/busy and MailTips sharing relationships with external domains, including whether each relationship is enabled and what access level is granted
• Get-AvailabilityAddressSpace — lists free/busy sharing configurations based on the external organization’s forest name and access method
• Get-SharingPolicy — lists calendar sharing policies and the domains and access levels they apply to

Microsoft’s documentation notes an important detail for Availability Address Space configurations: only the OrgWideFBToken access method is functional for free/busy sharing between two Exchange Online tenants, and a configuration using another access method cannot be migrated to Microsoft 365 Cross-Tenant Access Policy using this migration path.

It’s also worth checking which mailboxes are actually assigned a given Sharing Policy, since a policy can exist without being actively used — Microsoft’s guidance includes a PowerShell command for this purpose.

Confirm the external organization is hosted in Microsoft 365

Migration to Cross-Tenant Access Policy only applies where the external organization is also hosted in Microsoft 365. Microsoft’s documentation describes how to infer this from values such as TargetSharingEpr, TargetAutodiscoverEpr, or TargetApplicationUri in existing configurations — domains containing values like outlook.com, office365.com, or office365.us generally indicate a Microsoft 365-hosted organization, while other values may indicate on-premises Exchange.

What action may be required

If an SMB tenant has active cross-tenant sharing configurations with another Microsoft 365 organization, Microsoft’s guidance outlines a four-part migration process:

1. Inventory existing Organization Relationship, Availability Address Space, and Sharing Policy configurations, as described above.
2. Configure the equivalent Microsoft 365 Cross-Tenant Access Policy, which requires the external organization’s Microsoft Entra Tenant ID, Global Administrator privileges, and the Microsoft Graph PowerShell SDK Beta. This step also requires enabling the “Microsoft 365 Collaboration” trust level in Entra Cross-Tenant Access Policy for each external partner.
3. Test the new configuration. Microsoft’s documentation confirms that existing Organization Relationship, Availability Address Space, and Sharing Policy configurations take precedence over the new Cross-Tenant Access Policy, so they need to be taken out of the way before testing. Organization Relationship and Sharing Policy configurations can simply be disabled temporarily (using the -Enabled $False parameter) and re-enabled afterward if needed. Availability Address Space works differently: Microsoft’s guidance states it can’t be temporarily disabled — instead, admins must back up the configuration (using Export-CliXml) and then remove it with Remove-AvailabilityAddressSpace, restoring it from the backup later if the new policy doesn’t work as expected. Testing also requires coordination with an administrator in the partner organization, since Cross-Tenant Access Policy is described as an inbound-only setting — both organizations need complementary policies for sharing to work in both directions.
4. Clean up the old configurations once testing confirms the new policy works as expected, removing the old Organization Relationship, Availability Address Space, or Sharing Policy entries.

Because this is a coordinated, two-sided migration, SMB admins should expect to need cooperation from an administrator at each partner organization, not just changes on their own side.

Practical recommendations for SMB admins

The following are practical suggestions based on the documented behaviour above, not Microsoft-mandated steps:

• Start with the inventory step now, even if your organization hasn’t yet received a Message Center notification about the Cross-Tenant Access Policy rollout. Knowing what Organization Relationships, Availability Address Spaces, and Sharing Policies currently exist — and whether they’re actually in use — makes later migration faster.
• Plan migration around tenant availability. Microsoft says the new Microsoft 365 Cross-Tenant Access Policy is still rolling out. Check Message Center, then plan to migrate the applicable Organization Relationship, Availability Address Space, and Sharing Policy configurations after the feature reaches your tenant and before EWS deprecation.
• Identify your cross-tenant partners early. Since migration requires cooperation from an administrator in each partner organization, reaching out ahead of time avoids delays when EWS deprecation timing becomes more pressing.
• Don’t confuse the two changes. The automatic shared calendar sync upgrade is a background process that needs no action. The Cross-Tenant Access Policy migration is a manual, admin-driven process with dependencies on another organization’s cooperation.
• Set realistic expectations with users about cross-tenant calendar sharing performance. Because periodic sync (roughly every three hours) or ICS-based updates remain the norm for cross-tenant sharing, users expecting instant updates across organizational boundaries may need clarification that this isn’t yet supported.
• Watch your Message Center for tenant-specific rollout notices related to Cross-Tenant Access Policy availability, since Microsoft’s guidance indicates the rollout is ongoing and timing varies by tenant.

Conclusion

Microsoft 365 cross-tenant calendar sharing is undergoing two changes that SMB admins should track separately. The shared calendar sync model improvements make internal calendar sharing faster and more consistent across devices, with cross-tenant sharing still limited to periodic sync or ICS fallback rather than instant updates. Separately, Microsoft’s migration guidance directs admins to inventory Organization Relationship, Availability Address Space, and Sharing Policy configurations and plan a coordinated migration to Microsoft 365 Cross-Tenant Access Policy after the feature reaches their tenant and before EWS deprecation. Starting that inventory now, and identifying which partner organizations will need to cooperate on migration, is a practical way to stay ahead of the EWS deprecation timeline rather than reacting to it later.