Office 365 - Exchange 2013/2010 Hybrid - Free/busy not working

Hello Experts,

I have a little bit of trouble setting up my Office 365 hybrid environment.

Our current environment is as followed:
2* Exchange 2010 RU10 CAS/HT
2* Exchange 2010 RU10 MBX (all users reside on exchange 2010)
2* Exchange 2013 CU9 CAS/MBX  servers for hybrid connection to our Office 365 tenant.

We have the tenant configured and connected to our mail organization, mail flow works like charm.
We use ADFS 2.0 and AADSync for our users.

I have moved my own mailbox to the cloud to start the initial testing and iron out the biggest flaws in the setup before I transfer a select few users (other administrators) for the technical test-phase.

Almost everything works.
Only the free-busy with on-premises does not work.

When I try to open the calendar of another user I receive a “Free/Busy information is not available.” Error (this is a Office365 >> On-Prem situation).
I have enabled the sharing policies for free/busy but they seem to have no effect.

When I change the default permissions on a users calendar to “Reviewer” I am able to see everything in de users calendar.
When I switch the permissions back to anything less than reviewer I lose the ability to view the users calendar.

From on-prem to office 365 users are able to see my free/busy information.

Can anybody shine some light on this problem?
If you need more information, just let me know.
StruktonRailAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vasil Michev (MVP)Commented:
Well what are your Default permissions on user's Calendars? What does Test-OrganizationRelationship show?

Just in case, here are the general resources for troubleshooting hybrid free/busy issues, wouldnt hurt going over them again:
https://support.microsoft.com/en-us/kb/2555008
https://support2.microsoft.com/common/survey.aspx?scid=sw%3ben%3b3526&showpage=1
StruktonRailAuthor Commented:
The default sharing policy used in our on-premesis organization is "Calendar free/busy information with time, subject, and location"

The sharing policy on our online environment is the same.

Output of "Get-Organizationrelationship" from our online shell:
PS C:\> Get-OrganizationRelationship | fl

DomainNames           : {Domain.com, *domains*...}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel   : LimitedDetails
FreeBusyAccessScope   :
MailboxMoveEnabled    : False
DeliveryReportEnabled : True
MailTipsAccessEnabled : True
MailTipsAccessLevel   : All
MailTipsAccessScope   :
PhotosEnabled         : True
TargetApplicationUri  : FYDIBOHF25SPDLT.Domain.com
TargetSharingEpr      :
TargetOwaURL          :
TargetAutodiscoverEpr : https://autodiscover.Domain.com/autodiscover/autodiscover.svc
OrganizationContact   :
Enabled               : True
ArchiveAccessEnabled  : False
AdminDisplayName      :
ExchangeVersion       : 0.10 (14.0.100.0)
Name                  : O365 to On-premises
DistinguishedName     : CN=O365 to On-premises,CN=Federation,CN=Configuration,CN=Domain.onmicrosoft.com,CN=ConfigurationUnits,DC=EURPR05A003,DC=prod,DC=outlook,DC=com
Identity              : O365 to On-premises
Guid                  : d23f04c8-b952-4cf8-b45c-686ec6dd657b
ObjectCategory        : EURPR05A003.prod.outlook.com/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass           : {top, msExchFedSharingRelationship}
WhenChanged           : 5-10-2015 14:31:16
WhenCreated           : 18-9-2015 16:53:28
WhenChangedUTC        : 5-10-2015 12:31:16
WhenCreatedUTC        : 18-9-2015 14:53:28
OrganizationId        : EURPR05A003.prod.outlook.com/Microsoft Exchange Hosted Organizations/Domain.onmicrosoft.com - EURPR05A003.prod.outlook.com/ConfigurationUnits/Domain.onmicrosoft.com/Configuration
Id                    : O365 to On-premises
OriginatingServer     : DB4PR05A003DC02.EURPR05A003.prod.outlook.com
IsValid               : True
ObjectState           : Unchanged


Output of "Get-Organizationrelationship" from our local shell:
[PS] C:\>Get-OrganizationRelationship | fl


DomainNames           : {Domain.com, Domain.mail.onmicrosoft.com}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel   : LimitedDetails
FreeBusyAccessScope   :
MailboxMoveEnabled    : True
DeliveryReportEnabled : True
MailTipsAccessEnabled : True
MailTipsAccessLevel   : All
MailTipsAccessScope   :
PhotosEnabled         : True
TargetApplicationUri  : outlook.com
TargetSharingEpr      :
TargetOwaURL          : https://outlook.com/owa/Domain.com
TargetAutodiscoverEpr : https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact   :
Enabled               : True
ArchiveAccessEnabled  : True
AdminDisplayName      :
ExchangeVersion       : 0.10 (14.0.100.0)
Name                  : On-premises to O365
DistinguishedName     : CN=On-premises to O365,CN=Federation,CN=Domain Holding,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=local
Identity              : On-premises to O365
Guid                  : 4fb1f91a-1db1-41c7-96dd-f668cae4acd3
ObjectCategory        : domain.local/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass           : {top, msExchFedSharingRelationship}
WhenChanged           : 2-10-2015 14:50:25
WhenCreated           : 18-9-2015 16:53:25
WhenChangedUTC        : 2-10-2015 12:50:25
WhenCreatedUTC        : 18-9-2015 14:53:25
OrganizationId        :
Id                    : On-premises to O365
OriginatingServer     : NL_DC01.domain.local
IsValid               : True
ObjectState           : Unchanged

the Test-OrganizationRelationship cmdlet shows all systems go, no warnings or errors at all.
StruktonRailAuthor Commented:
After opening up a case with microsoft the solution was found by running the following powershell command on the on-premise exchange 2010 server:

“Get-FederationTrust | Set-FederationTrust –RefreshMetadata”

After waiting for 15 minutes everything started working.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
StruktonRailAuthor Commented:
A support case with Microsoft resolved the problem, they gave us this solution.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Office 365

From novice to tech pro — start learning today.