Service issues › EX1542065
Some users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online
- Started
- 04 Nov 2026 16:00 UTC
- Last update
- 12 Nov 2026 22:21 UTC
- Status
- serviceDegradation
- Origin
- microsoft
Timeline
12 Nov 2026 22:21 UTC · regular
Title: Some users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online
User impact: Users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online.
More info: To remediate impact while our investigation is ongoing, admins can configure free/busy sharing between impacted organizations using Organization Relationship. The Organization Relationship will take precedence over the cross-tenant access policy and sharing will begin working again after caches clear, usually within 2 hours. If EWS has been disabled in your tenant, it will need to be re-enabled to support Organization Relationship. The Organization Relationship should be removed when this incident is resolved.
Current status: We're monitoring the deployment of our fix which has reached 62 percent saturation to the affected environment. We anticipate the fix will complete deployment by Saturday, November 14, 2026.
Scope of impact: This issue impacts some users whose organization utilizes cross-tenant access policy, who may be unable to view free/busy info shared between organizations in Exchange Online. This section may be updated as the investigation progresses.
Estimated time to resolve: We anticipate that the fix will complete deployment and remediate the impact by Friday, November 14, 2026.
Root cause: A recent change introduced a regression that causes cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.
Next update by: Friday, November 13, 2026, at 11:00 PM UTC
11 Nov 2026 23:22 UTC · regular
Title: Some users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online
User impact: Users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online.
More info: To remediate impact while our investigation is ongoing, admins can configure free/busy sharing between impacted organizations using Organization Relationship. The Organization Relationship will take precedence over the cross-tenant access policy and sharing will begin working again after caches clear, usually within 2 hours. If EWS has been disabled in your tenant, it will need to be re-enabled to support Organization Relationship. The Organization Relationship should be removed when this incident is resolved.
More information on this process can be viewed here: https://learn.microsoft.com/en-us/exchange/sharing/organization-relationships/create-an-organization-relationship
Current status: After further analysis, we've isolated that additional organizations utilizing cross-tenant access policies are affected by this free/busy issue, and we've expanded communications to all potentially affected users. We've updated the "Title", "User impact", and "Scope of impact" fields of our communications to reflect this. We've initiated deployment of a fix to address a regression introduced by a recent service change that caused cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address. We're evaluating ways to expedite our deployment and we aim to provide a timeline to remediation as soon as possible
Scope of impact: This issue impacts some users whose organization utilizes cross-tenant access policy, who may be unable to view free/busy info shared between organizations in Exchange Online. This section may be updated as the investigation progresses.
Start time: Wednesday, November 4, 2026, at 4:00 PM UTC
Root cause: A recent change introduced a regression that causes cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.
Next update by: Friday, November 13, 2026, at 12:00 AM UTC
11 Nov 2026 19:44 UTC · regular
Title: Some users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online
User impact: Users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online.
Current status: We've completed validation of our code fix to revert the service change responsible for this issue and have initiated deployment to the affected environment. As deployment progresses, some users may begin experiencing impact alleviation. We'll provide an estimated resolution timeline once available.
Scope of impact: This issue impacts some users whose organization utilizes cross-tenant access policy, who may be unable to view free/busy info shared between organizations in Exchange Online. This section may be updated as the investigation progresses.
Root cause: A recent change introduced a regression that causes cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.
Next update by: Friday, November 13, 2026, at 8:30 PM UTC
10 Nov 2026 19:35 UTC · regular
Title: Some users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online
User impact: Users may not see free/busy info shared between organizations using cross-tenant access policy in Exchange Online.
Current status: We're validating our code fix that'll revert the offending service change, address the offending regression, and remediate the impact. We'll provide an updated timeline for the deployment of our code fix after our internal validations have verified that its deployment won't produce any unexpected problems for the service.
Scope of impact: This issue impacts some users whose organization utilizes cross-tenant access policy, who may be unable to view free/busy info shared between organizations in Exchange Online. This section may be updated as the investigation progresses.
Root cause: A recent change introduced a regression that causes cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.
Next update by: Wednesday, November 11, 2026, at 8:30 PM UTC
10 Nov 2026 09:28 UTC · regular
Title: Users can’t see free/busy information in cross-tenant Outlook calendars using Outlook desktop and Outlook on the web
User impact: Users can’t see free/busy information in cross-tenant Outlook calendars using Outlook desktop and Outlook on the web.
Current status: We've identified that a recent change introduced a regression that caused cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address, resulting in impact. We're reverting the change to restore the correct configuration and expect to confirm the deployment timeline by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in cross-tenant Outlook calendars is impacted. This section may be updated as our investigation continues.
Root cause: A recent change introduced a regression that caused cross-tenant mailbox requests to be rejected when a tenant ID was used instead of the mailbox's SMTP address.
Next update by: Tuesday, November 10, 2026, at 8:30 PM UTC
10 Nov 2026 04:53 UTC · regular
Title: Users can’t see free/busy information in cross-tenant Outlook calendars using Outlook desktop and Outlook on the web
User impact: Users can’t see free/busy information in cross-tenant Outlook calendars using Outlook desktop and Outlook on the web.
Current status: After further investigation, it was determined that additional information from affected systems and users regarding recent mailbox migrations would be required to facilitate remediation efforts. We're reaching out to your representatives to gather additional diagnostic logs to help with understanding the underlying root cause.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in cross-tenant Outlook calendars is impacted. This section may be updated as our investigation continues.
Next update by: Tuesday, November 10, 2026, at 9:30 AM UTC
10 Nov 2026 03:15 UTC · regular
Title: Users can’t see free/busy information in cross-tenant calendar
User impact: Users can’t see free/busy information in cross-tenant calendar.
Current status: Our investigation into data migration configurations is progressing, however due to the complexity of the issue this is taking longer than initially anticipated. We're reviewing telemetry relevant to affected systems and will provide an updated timeline on remediation as one becomes available.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in cross-tenant Outlook calendars is impacted. This section may be updated as our investigation continues.
Next update by: Tuesday, November 10, 2026, at 5:30 AM UTC
10 Nov 2026 01:25 UTC · regular
Title: Users can’t see free/busy information in cross-tenant calendar
User impact: Users can’t see free/busy information in cross-tenant calendar.
Current status: Our review of the database mismatch mentioned in previous communications is ongoing. In parallel, we've expanded the investigation and are examining configuration settings and system telemetry to identify and isolate potential errors which may have occurred during recent data migrations to determine whether these could be contributing to impact.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted. This section may be updated as our investigation continues.
Next update by: Tuesday, November 10, 2026, at 3:30 AM UTC
09 Nov 2026 22:57 UTC · regular
Title: Users can’t see free/busy information in cross-tenant calendar
User impact: Users can’t see free/busy information in cross-tenant calendar.
Current status: We're analyzing a database mismatch from free/busy information requests shared by your representatives to isolate if this is the underlying source of impact and to evaluate our next steps towards remediation.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted. This section may be updated as our investigation continues.
Next update by: Tuesday, November 10, 2026, at 1:30 AM UTC
08 Nov 2026 01:13 UTC · regular
Title: Users can’t see free/busy information in cross-tenant calendar
User impact: Users can’t see free/busy information in cross-tenant calendar.
Current status: Our review of the recently provided data from your organization has been inconclusive. Subsequently, we’ve begun to reach out to your representatives to gather several reproductions of impact as we anticipate that these items will expedite our investigative efforts and help determine our next troubleshooting actions.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted. This section may be updated as our investigation continues.
Next update by: Monday, November 9, 2026, at 11:30 PM UTC
07 Nov 2026 05:23 UTC · regular
Title: Users can’t see free/busy information in cross-tenant calendar
User impact: Users can’t see free/busy information in cross-tenant calendar.
Current status: We’ve collected the read-only outputs containing information about your organization's relationship and connector settings and are working on correlating its GetSchedule requests to the failures observed in the HAR so that we can identify the underlying root cause and develop a remediation plan.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted. This section may be updated as our investigation continues.
Next update by: Sunday, November 8, 2026, at 3:00 AM UTC
07 Nov 2026 00:47 UTC · regular
Title: Users can’t see free/busy information in cross-tenant calendar
User impact: Users can’t see free/busy information in cross-tenant calendar.
Current status: We're continuing our investigation of HAR logs and have determined that additional information about your organization's relationship and connector settings is needed to better understand the issue and identify remediation steps. We're coordinating with your representatives to collect these details.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted.
Next update by: Saturday, November 7, 2026, at 6:00 AM UTC
06 Nov 2026 22:47 UTC · regular
Title: Users can’t see free/busy information in cross-tenant calendar
User impact: Users can’t see free/busy information in cross-tenant calendar.
Current status: We’ve received the requested fresh HAR logs and are analyzing them to identify and isolate any errors potentially contributing to impact for further investigation.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted.
Next update by: Saturday, November 7, 2026, at 1:00 AM UTC
06 Nov 2026 21:50 UTC · regular
Title: Users can’t see free/busy information in cross-tenant calendar
User impact: Users can’t see free/busy information in cross-tenant calendar.
Current status: We’re reaching out to your representatives to request fresh HTTP Archive format (HAR) logs to assist our investigation into the source of the issue.
Scope of impact: Your organization is affected by this event, and any user attempting to view free/busy information in the cross-tenant calendar is impacted.
Next update by: Friday, November 6, 2026, at 11:00 PM UTC
06 Nov 2026 21:33 UTC · regular
Title: Users can’t see free/busy information in cross-tenant calendar
User impact: Users can’t see free/busy information in cross-tenant calendar.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
© Microsoft — archived from Microsoft 365 service health. Content notice