Want to share free/busy information with another 365 tenant - Federation Information could not be received from my org

Joe Grover 431 Reputation points
2021-07-13T14:15:15.163+00:00

We currently have a hybrid setup with 365 and Exchange 2016 on-premises. We'd like to share free/busy data for some of our online 365 users with another company who also has a 365 tenant (online-only I believe).

However it appears that our federation information cannot be retrieved. If I run Get-FederationInformation against their domain, I receive info. If I run it against our domain however, I get the dreaded Federation information could not be received from the external organization.

Based on my investigations, I have confirmed the following:

  • WSSecurityAuthentication is set to True
  • MRSProxy is enabled
  • The /autodiscover.svc/WSSecurity URL at our autodiscover URL (which is currently pointing to an on-premise KEMP load balancer) displays a logon prompt
  • Both ports 80 and 443 are accessible (the KEMP does HTTP redirect to HTTPS)

We're still in the process of migrating the last batches of users, so our autodiscover URL is still pointed on-prem. I don't know if this is the issue, or if/when I can change the autodiscover URL to Microsoft (since we will be staying in Hybrid mode for some time), but I'd like to get this working sooner rather than later.

On my end, I'd gone into the Exchange Admin Center (online) and set up an Organization Sharing object for the other tenant. They are unable to do this back to us due to the errors above. Thoughts?

Microsoft Exchange Online Management
Microsoft Exchange Online Management
Microsoft Exchange Online: A Microsoft email and calendaring hosted service.Management: The act or process of organizing, handling, directing or controlling something.
4,143 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,318 questions
0 comments No comments
{count} vote

Accepted answer
  1. Joe Grover 431 Reputation points
    2021-08-16T18:07:40.093+00:00

    I can confirm that autodiscover wound up being the root of the issue. It wasn't working in my previous comment apparently due to the powershell command we'd used to try to manually specify the AutodiscoverEPR. I had them remove that command, then set up the org relationship normally (now that my autodiscover points to 365) and it started working almost immediately.

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
  1. Vasil Michev 94,131 Reputation points MVP
    2021-07-13T15:19:19.363+00:00

    Since at least one of the organizations is in Hybrid, you will need to create additional org relationships as detailed here: https://techcommunity.microsoft.com/t5/exchange-team-blog/the-hybrid-mesh/ba-p/605910


  2. Xzsssss 8,861 Reputation points Microsoft Vendor
    2021-07-14T07:56:32.407+00:00

    Hi @Joe Grover ,

    If you only want to share the free busy of your O365 users ( O365 users to O365 users), I think you could simply create the organization relationship on Exchange online Admin Center or using the cmdlets on Exchange online Powershell:

    New-OrganizationRelationship -Name "Contoso" -DomainNames "contoso.com","northamerica.contoso.com","europe.contoso.com" -FreeBusyAccessEnabled $true -FreeBusyAccessLevel LimitedDetails  
    

    On Exchange online Admin Center:
    114531-image.png

    For more details: Create an organization relationship in Exchange Online

    Best regards,
    Lou


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  3. Xzsssss 8,861 Reputation points Microsoft Vendor
    2021-07-22T06:59:27.04+00:00

    Hi @Joe Grover ,

    Oh sorry I didn't make it more clear, as you could sharing free busy with their tenant, your partner should try this command to share free busy to you.

    As for the Get-OrganizationRelationship, could you see the relationships here:
    117002-image.png

    For me I get the error below when trying to share free busy on Exchange online admin center, but I could use the command to do that.
    116976-image.png

    Best regards,
    Lou


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.