Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Can't see free/busy information after a mailbox is moved to Microsoft 365: the 'Could not be updated' error

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

After a mailbox moves to Microsoft 365, a colleague still on the on-premises side opens Scheduling Assistant and sees no free/busy for that person. Opening the calendar gives a "Could not be updated" error. Microsoft's documented cause is that the Calendar folder's Default permission is None or Contributor. The fix is to set the Default permission to Free/Busy time, or to Free/Busy time, subject, location.

If that is already correct, Microsoft's page gives no further step for this symptom. A different fault with a different error text, an Exchange Online user who cannot see an on-premises user's availability, has its own section under Fix.

What the error means

Microsoft's page, "Users can't see free/busy information after a mailbox is moved to Microsoft 365", gives the scope: it applies to Exchange Online, with an on-premises user looking up a mailbox that has moved. The explanation: "When you query free/busy information by using Scheduling Assistant in a cross-forest scenario, the Availability service uses the organization relationship instead of delegated user permissions."

The organization relationship "links to the default account that is seen in the calendar permissions". Therefore it "can't process an explicitly granted permission such as "Free/Busy time" or "Free/Busy time, subject, location."" That is why the Default entry decides what the lookup shows.

Microsoft states the consequence: "If the default permissions are set to None or Contributor, no free/busy information is displayed for remote users, and users cannot view the mailbox calendar. This is because neither kind of permission offers any level of free/busy visibility."

Why did the move change anything? Microsoft explains that "In a hybrid deployment, free/busy and calendar-sharing functionality work differently than when both users are in the same environment. The default permissions determine the kind of free/busy information that users in a remote forest can see." After the move, the lookup between a person on your servers and a mailbox in Microsoft 365 is a cross-forest request, and the Default entry decides what it shows.

Three calendar roles matter, as Microsoft defines them on the cmdlet page:

  • AvailabilityOnly: "View only availability data".
  • LimitedDetails: "View availability data with subject and location".
  • Reviewer: the permissions FolderVisible and ReadItems, which allow reading the calendar items themselves.

Microsoft also says that when the Default permissions are None or Contributor, "details can be obtained only when user delegation is used by attaching calendars directly to the calendar view of Outlook." That is a workaround for one person, not a fix for the whole group.

Likely causes

Cause What you see How to confirm
Default calendar permission is None or Contributor Blank Scheduling Assistant and "Could not be updated" for the moved mailbox Get-MailboxFolderPermission on the calendar shows the Default entry as None or Contributor
The opposite direction, a different fault: an Exchange Online user cannot see an on-premises user's availability (Microsoft's InvalidUser page, for Exchange Server SE with the dedicated Exchange hybrid application) Diagnostic response The response from the Autodiscover service failed due to an error in user setting 'ExternalEwsUrl'. Error message: InvalidUser. Follow the separate section under Fix
Details wanted, not just availability Free/busy works but subject and location are blank Microsoft: Limited Details is "insufficient in a hybrid environment"; at least Reviewer is needed

Prove the cause before changing anything

  1. List the calendar permissions of the moved mailbox. Microsoft's cmdlet page shows this form for the Calendar folder:
Get-MailboxFolderPermission -Identity ayla@contoso.com.au:\Calendar

Save the output. Look at the entry for the default (everyone) user and note its access rights.

  1. Confirm which way the failure runs. This fault is an on-premises user who cannot see a moved mailbox. If instead an Exchange Online user cannot see an on-premises user's availability and the diagnostic shows InvalidUser, use the separate section under Fix.

Fix

Default permission. Microsoft's workaround: the mailbox owner "can work around this issue by changing the default permissions to Free/Busy time or Free/Busy time, subject, location." This "changes the free/busy information that is shared for all remote users."

Save first: the Get-MailboxFolderPermission output from step 1, which holds the previous value.

Disruptive step: the change below lets every remote user see when this person is busy.

Change the Default entry on the calendar, either in Outlook's calendar permissions, which is where Microsoft's page shows the setting, or with the cmdlet, using the name shown for the default entry in your saved output:

Set-MailboxFolderPermission -Identity ayla@contoso.com.au:\Calendar -User "name-from-your-saved-output" -AccessRights AvailabilityOnly

The -User value must be the name exactly as listed in your saved listing. Microsoft's role AvailabilityOnly is described as "View only availability data"; LimitedDetails as "View availability data with subject and location". Matching these cmdlet roles to the Outlook levels "Free/Busy time" and "Free/Busy time, subject, location" is the reading used here, not a mapping Microsoft's pages state, so confirm the level in Outlook afterwards.

To undo it, set the entry back to the recorded value. Note that Microsoft says granting Contributor changes the permission level to Custom, so a restored entry may display as Custom.

Details for one person. For a remote user to see item details, Microsoft says "The user has to be granted at least Reviewer permission to view calendar item details", and that "A remote user can be granted Calendar folder permissions to obtain additional access to the contents of the Calendar folder". Microsoft says a change to the Default entry applies to all remote users, so grant Reviewer to the named person rather than raising Default.

Save first: keep the Get-MailboxFolderPermission output from step 1, which shows who already has access.

Risk: the named person can then read the item subjects, locations and contents of that calendar. Use the form on Microsoft's Add-MailboxFolderPermission page:

Add-MailboxFolderPermission -Identity ayla@contoso.com.au:\Calendar -User julia@contoso.com.au -AccessRights Reviewer

Back-out: remove that one person's entry, in the form on Microsoft's Remove-MailboxFolderPermission page:

Remove-MailboxFolderPermission -Identity ayla@contoso.com.au:\Calendar -User julia@contoso.com.au

Microsoft's workaround for the mailbox owner is Outlook's calendar permissions; an administrator can use the cmdlet form above instead.

The opposite direction, a different fault: an Exchange Online user cannot see an on-premises user's availability. This is not the symptom above. Microsoft's InvalidUser page covers it for "a supported Exchange Server SE deployment with the dedicated Exchange hybrid application", and says it "doesn't cover every InvalidUser error in a different tenant or a Microsoft Graph request." Its cause: "The cloud mailbox's proxy addresses or the endpoint used for the hybrid availability request can be misconfigured." Read first, and change nothing:

Get-Mailbox -Identity ayla@contoso.com.au | Format-List PrimarySmtpAddress,EmailAddresses
Get-OrganizationRelationship | Format-List
Get-IntraOrganizationConnector | Format-List

Microsoft says to verify that the expected secondary address in your hybrid routing domain, such as contoso.mail.onmicrosoft.com, is present, and to compare the discovery or EWS endpoint with the actual on-premises deployment. Test the other direction independently. Microsoft's Test-OrganizationRelationship page says it "only verifies that the configuration allows these features to work correctly" and does not perform functional tests of free/busy:

Test-OrganizationRelationship -UserIdentity ayla@contoso.com.au -Identity contoso.com

Run it with your own relationship name in -Identity, and in -UserIdentity a mailbox in your own organisation, because Microsoft's page describes -UserIdentity as "the mailbox for which a delegation token is requested to access the external organization's configuration information."

Proxy address missing. Save first: add | Out-File -FilePath C:\Temp\proxy-before.txt to the Get-Mailbox command above and keep the file (the folder must exist).

Disruptive step: the correction below adds or changes a proxy address in the on-premises directory, which alters mail routing for that user. Impact: mail to the user can route differently once the change synchronises.

Microsoft says: "correct the address in the authoritative on-premises directory and synchronize the change. Don't edit a synchronized property only in Exchange Online." Microsoft's page names no attribute and no command for this edit; the address is one of the mailbox's proxy addresses, the EmailAddresses value in your listing. To undo it, put the on-premises address list back to the list saved in proxy-before.txt in the same tool, and synchronise again.

Endpoint wrong. Microsoft says to correct a confirmed endpoint error "using the configuration object that the request actually uses." If an organization relationship is in use, Set-OrganizationRelationship can set the correct TargetSharingEpr, which Microsoft's Set-OrganizationRelationship page describes as "the URL of the target Exchange Web Services for the external organization."

Save first: save the output of Get-OrganizationRelationship | Format-List to a file, for example by adding | Out-File -FilePath C:\Temp\orgrel-before.txt.

Risk: a wrong endpoint stops availability lookups for everyone using that relationship. Use the form below with the confirmed URL in place of the placeholder:

Set-OrganizationRelationship -Identity "Contoso" -TargetSharingEpr "the-confirmed-EWS-URL"

Back-out: run the same command with the TargetSharingEpr value from the saved file. If the saved value is empty, Microsoft's page gives no way to clear it: record that, and get the previous value from whoever configured the relationship before you change it.

Confirm the fix

Wait for any directory synchronisation to finish, then repeat the exact lookup that failed, with the same requester and target. For the opposite-direction fault, Microsoft's check is: "Confirm that ExternalEwsUrl no longer returns InvalidUser and that availability loads. Test the other direction independently." For the permission case, ask the on-premises user to open Scheduling Assistant for the moved person.

Example (illustrative): 140 mailboxes at contoso.com.au move in 7 batches of 20 (140 divided by 7). After batch 1, the help desk finds that in 9 of the 20 moved calendars the Default entry is None or Contributor. That is 45% (9 divided by 20). They set the 9 to Free/Busy time before batch 2 moves, and add a Default-permission check to the cut-over list.

What to watch afterwards

  • Check the Default calendar permission for each batch before and after it moves, since Microsoft says it decides what remote users see.
  • Add a scheduling test between one moved and one unmoved user to each go/no-go list.
  • Keep the saved permission output with the batch record, so the change can be undone.
  • Ask the first few moved users whether colleagues still on the old servers can see their availability. Microsoft says to test each direction independently for the InvalidUser fault.
  • Re-check Default permissions on any calendar that is later reset or restored from a backup copy.
  • If Microsoft support is involved, the Hybrid Free/Busy Diagnostic package collects the relevant PowerShell output for them; it must be run on the hybrid server with Global admin credentials.

Risks and limits

These commands have not been run or lab-tested. Microsoft's free/busy page is about hybrid and cross-forest lookups. It does not cover cross-tenant sharing, and Microsoft's InvalidUser page says it "doesn't cover every InvalidUser error in a different tenant or a Microsoft Graph request." The Set-MailboxFolderPermission page documents the AvailabilityOnly role but does not name Default as a user value; treat the name in your own saved output as the authority.

Do not give every remote user Reviewer on every calendar to make the symptom disappear. That exposes meeting subjects and locations organisation-wide.

Sources