This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The following is an excerpt from Organization relationships in Exchange Online
"When you set up the organization relationship, you're responsible for setting up your side of the relationship. You specify the level of information that users in the external organization can view in your organization. The external organization is responsible for setting up their side of the relationship and specifying their level of information that's visible to users in your organization (which might be different than yours)."
However, we encountered a strange outcome when setting up an organization relationship between two tenants today.
There are two Exchange Online tenants abc.com and xyz.com
Users cannot see free busy of one another
First, we set up an organizational relationship in Exchange Online tenant of abc.com and shared free busy with domain xyz.com.
We immediately checked from xyz.com Exchange Online mailboxes if free busy of abc.com Exchange Online mailboxes were visible. Well, they were not. That is the expected behavior. Or is it? Does organizational relationship always require setting up at both tenants? This is my first question.
From abc.com too free busy of xyz.com was not visible, as per expected behavior.
After creating the organizational relationship in abc.com Exchange Online when we checked the details, we found the application Uri and Autodiscover endpoints pointing to on-premises. So, we changed the values to outlook.com and https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc/WSSecurity respectively.
When we checked xyz.com we were still not able to see the free/busy of abc.com.
But wait, when we checked from abc.com we were now able to see free busy of xyz.com.
That is not an expected behavior as per Microsoft documentation, right? Please advise.
PS: abc.com and xyz.com are a single on-prem multi-tenant hybrid.
@Anonymous
I am writing here to confirm with you any update about this thread now.
If the suggestion below helps, please feel free to accept it as an answer to close this thread. It also could be beneficial to other community members reading this thread.
We immediately checked from xyz.com Exchange Online mailboxes if free busy of abc.com Exchange Online mailboxes were visible. Well, they were not. That is the expected behavior. Or is it? Does organizational relationship always require setting up at both tenants? This is my first question.
This phenomenon caused by wrong configuration in "TargetApplicationUri" and "TargetAutodiscoverEpr". After creating relationship between tenant, you need double check value for those two attributes. Then your tenant free/busy will be shared to target tenant.
PS: abc.com and xyz.com are a single on-prem multi-tenant hybrid.
If so, I would suggest you try to create a organization relationship with Exchange online default domain name.
Then check with mailbox which use the default domain name, whether free/busy shared as expected. I guess this phenomenon caused by shared domain name in hybrid.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.
Hello @KyleXu-MSFT
Yes, in abc.com's own hybrid organizational relationship "TargetApplicationUri" and "TargetAutodiscoverEpr" values are missing from both directions.
The values we changed were for tenant-to-tenant organizational relationship from abc.com to xyz.com. We have not yet created an organizational relationship between xyz.com to abc.com.
Does organizational relationship work only when set up from both sides? I want to get this fundamental concept right before we discuss further.
I tested with three tenants (A and B has two-way relationship, B and C have one-way relationship) and find out that for free/busy sharing between tenant, two-way organization relationship is needed.
After modifying, we need wait a while (about one hour) for it to take effect.
When you set up "your end" of the process, you're basically giving the other tenant permissions to see availability info for your users. Thus both sides need to do their part for the process to cover all users.
With that in mind, when one of the organizations is in Hybrid, you need to set up additional (two-way) relationships, as you effectively have three (or more) organizations now. This is known as the Hybrid mesh and is detailed here: https://techcommunity.microsoft.com/t5/exchange-team-blog/the-hybrid-mesh/ba-p/605910
Hello Vasil, thank you for your response. Yes, we have gone through the article on Hybrid mesh. However, I still do not understand why after changing the Autodiscover and application Uri details in the organizational relationship at my end I am able to view the free busy of the domain I am sharing my free busy with.
Without knowing the full setup, it's hard to answer. Likely all mailboxes from said domain were moved to the cloud and have switching the URI makes it possible for the availability info to be queried. Org relationships are not domain-based, they cover the entire organization (Exchange Online and Exchange server sharing the same domains still counts as two separate orgs), although in some cases you might need to adjust the list of domains.
Querying the other domain might be failing because the targetaddress of the matching user is configured incorrectly, but that's just a guess. If you have examined the article above, you have probably seen the two detailed "troubleshooting" articles too - follow them to get a proper understanding of what's happening: https://techcommunity.microsoft.com/t5/exchange-team-blog/demystifying-hybrid-free-busy-finding-errors-and-troubleshooting/ba-p/607727