Unable to see free / busy information across two different organizations

Hi Daryl,

Thanks for the quick reply. I ran the command and get the following error. I cannot confirm if users in the external domain were able to see free / busy calendar prior to us moving the Exchange servers to a new building, but they say they are pretty sure they were able to. Also, I cannot say for sure if the test-organizationrelationship was working either.

Thanks,
OrganizationRelationShip.PNG

the user identity has to be your primary or the users primary smtp address (i believe) not your domain login, from memory when i done it i used -verbose at the end of the command too

did you check you can hit their https://autodiscover.yourdomain/autodiscover/autodiscover.svc/WSSecurity ? can you get to it without cert errors etc?   if you cant get the https connection to that site it wont work at all , probably the first thing you want to nail before checking the rest




ps also check the organisation relationship settings on both ends , easiest to do this is in the GUi Managerment console

click on organizational configuration. Check the Federation trust ( needs to be valid with Microsoft, just check its there for now  as its a prereq for a org relationship ) then check the organization relationship tabs

that is where the free busy stuff is set between you and the other side.

pps once the above is confirmed working or valid check the sharing policys which is under organizational configuration > then mailbox > sharing policys

the reason you will need to check sharing policys is by default anonymous users may not have any permissions and they will need some to see free busy info, you can apply the policy to just the calendars you want to share

let me know how you go.

just thought of something else, you mention you changed locations, did your public IP change? if so does you auto discover record point to the new location IP?

Hi Vijaya,

Thanks for the reply. I verified both commands and get no errors. the Get-FederationInformation shows the domain name and target autodiscover url correctly.  The Test-OrganizationRelationship does not display anything, but no errors either.

Hi Daryl,

yes, our Public IP did change, however we have updated it in the places we could think of. The remote organization is still able to see users in our organization and invite them to meetings, however cannot see their free / busy schedule. Thanks for the follow up.

check the organization relationships tab

in the gui  Organizatin Config > organization Relationships > click on the name of the one you have setup and verify that the Free busy settings are correct on the general tab

You may have to wait 24 hours for the MS Federation gateway to pickup the change.

Thanks Guys, turned out the autodiscover record was still pointing to the old public IP. After making the switch, users in the remote organization are now able to see the free / busy schedule. Thanks so much for your help and tips.