This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
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?
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.
Hi Joe,
Very glad to know it's working now. I tried to reproduce what you have experienced but just failed again and again.
Thank you for sharing your resolution here. For sure it will help others who have the same questions.
I converted your comment to a answer and you could mark your own answer as Accepted.
Again, thank you and have a nice day!
Best regards,
Lou
Thanks for your assistance in helping me work through it. It's appreciated.
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
This is one of the articles I'd seen, but it confused me. The article shows two on-premise orgs sharing info, then an on-premise sharing with a hybrid. I need to have a hybrid share with a 365 org.
Using this information, do they need to create a connection to our on-prem? Do I need to create a connection to them from on-prem? As far as I know I have the information set up between us and them--the wizard in the Exchange Admin Center was pretty straightforward from that point.
What I don't know is what they need to do now. They've advised that they can't complete the setup because they get the same error I do when running the Get-FederationInformation command. I'm not sure what it is I need to do on my end so that command returns information.
It's analogous. When you're in Hybrid, you have two organizations "coupled" together, but you still need an org relationship to see free/busy info (one in each direction). Now you're adding another organization in the mix, meaning additional (two way) trusts need to be added between each org.
So, Get-FederationInformation will only successfully return results if the domain specified has a trust with you? The articles I read indicate that you should be able to run that command for your own domain and get information back. I'm not getting that, I just get the error.
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:
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.
Is this possible for on-premise as well? From what I'm being told the 365-only tenant will need to also create an org sharing to my on-premise system. I want to limit this information to:
I've already done what you described to set up the org share with them, it's them doing it back to me that's giving an error.
Hi @Joe Grover ,
No, the above only shares O365 users free busy whatever they are hybrid or not.
But if you want to share your On-prem users free busy in a hybrid deployment to another O365 tenant, you'll need a federation relation: Organization relationships in Exchange Online
If you want to share calendars with an on-premises Exchange organization, the on-premises Exchange administrator has to set up an authentication relationship with the cloud (also known as "federation") and must meet minimum software requirements.
Please refer to:https://learn.microsoft.com/en-us/exchange/federation-exchange-2013-help
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.
I only want to share free/busy data for users I've migrated to O65 with another exclusively-O365 tenant.
However I'm getting hung up on this Get-FederationInformation command, which returns nothing when I run it against my domain. From what I've read, this needs to be able to return information.
When the O365 tenant tries to set up the same trust information to us, they get errors because of this command failing. I need to determine what needs to be done on my end so it doesn't fail so they can complete their side of the connection.
Also to be clear--I've already set up the relationship to the other O365 tenant. The issue is that they can't set it up back to me, and I'm curious if it's because it's using Autodiscover to "find" us (and our Autodiscover is still pointed to our on-prem environment as we're still migrating users).
If that's the case, I need to know what I need to do so the Get-FederationInformation command can return information about our environment, as I'm being told that's why they can't set up the trust back to us.
Hi @Joe Grover ,
I did some tests about this cmdlet. I also failed run this command to my on-prem server.
Sometimes I could create the Organization Sharing with another tenant, and I could use Get-Federationinformation to this tenant.
But it's not working conversely.
Before I could find something on Autodiscover settings, please try to create the free busy sharing with the cmdlet:
New-OrganizationRelationship -name "Name" -DomainNames "domain.com" -FreeBusyAccessEnabled $true -FreeBusyAccessLevel LimitedDetails -TargetApplicationUri outlook.com -TargetAutodiscoverEpr https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc/WSSecurity
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.
The command fails.
New-OrganizationRelationship -name "TheirDomain" -DomainNames "theirdomain.com" -FreeBusyAccessEnabled $true -FreeBusyAccessLevel AvailabilityOnly -FreeBusyAccessScope "Local distribution group containing the users whose free/busy data will be shared" -TargetApplicationUri outlook.com -TargetAutodiscoverEpr https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc/WSSecurity
Processing data for a remote command failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests.
Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.
Subsequent attempts indicate:
Active Directory operation failed on DCName.domain.local. The object 'CN=TheirDomain,CN=Federation,CN=OurDomain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=local' already exists.
However I can't Get-OrganizationRelationship or Remove-OrganizationRelationship for this identity. The only relationship I see in Get-OrganizationRelationship is our hybrid connector to 365.
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:
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.
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.
Yeah, the error you showed is what they get when they try to add the sharing relationship back to me. I've successfully added the sharing relationship to them in Exchange Online admin center.
So you're suggesting they use the powershell command, and specify the 365 autodiscover URL rather than it trying to talk back to our on-prem?
Hi @Joe Grover ,
Yes, after the error above, I run the powershell command and this could work for me. The Organization sharing was added successfully to the M365 Admin Center and we could see it there.
I will go on with some tests, and try to make this issue more clear.
Best regards,
Lou
IOur partner did successfully execute the powershell command and the org relationship shows up in their EAC, however their end users still cannot see our 365 free/busy data for our users.
From what I can tell the client will still use autodiscover to determine where to go when querying free/busy data, so it looks like until I can point my autodiscover (which is imminent; I'll be posting a question about that in a few minutes heh) it isn't going to work.
Hi @Joe Grover ,
So sorry for late of this reply.
As you have posted, you could move the autodiscover and other services to O365 for a better experience.
Hope your issue could be resolved soon.
Best regards,
Lou
Ok, I changed the autodiscover URL yesterday and running Get-FederationInformation against my domain returns the expected info. It still isn't working, however (in either direction).
If I add someone from the other org to a meeting, I don't see their free/busy. Mousing over the hashmarks I see this:
They get the same thing when adding me.
I did notice if I run Get-OrganizationRelationship I still see our previous autodiscover URL under the TargetOwaURL, and there's no value for TargetAutoDiscoverEpr. I don't know if that's a reason (or a symptom). Under their entry TargetOwaURL is empty and they have one of the outlook.com servers listed for TargetAutodiscoverEpr.