Cannot View Calendars Between On-Premises Exchange 2007 and Office 365 Environments

Users that are migrated to Office 365 cannot see the calendars of our users whose mailboxes are still housed on our Exchange 2007 server and vice versa. Thank you for any help you can provide!
Todd WilloughbyLead System EngineerAsked:
Who is Participating?
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:
What kind of migration? Free/busy info will only be visible if you are in Hybrid. Otherwise you will have to share the calendars between the two organizations: http://technet.microsoft.com/en-us/library/jj916670(v=exchg.150).aspx
0
Murali ReddyExchange ExpertCommented:
Cross premise permissions will not replicate to cloud when you moved the mailboxes to office365. So, if there are any mailboxes/calendars can't be accessible for the permissions set.

However, the calendar view is possible based on your organization relationship, how it is configured. Please run the below command.

Get-OrganizationRelationship |fl FreeBusyAccessEnabled,FreeBusyAccessLevel

FreeBusyAccessEnabled : True/False (should be true)
FreeBusyAccessLevel   :  (None | AvailabilityOnly | LimitedDetails) (Should not be none)

Use, Set-OrganizationRelationship  to make the changes accordingly.
0
Todd WilloughbyLead System EngineerAuthor Commented:
This is what I get whenever I attempt to the Get-OrganizationRelationship commandlet on both the hybrid server and the Exchange 2007 server:

The term 'Get-OrganizationRelationship' is not recognized as the name of a cmdlet, function, script
 file, or operable program. Check the spelling of the name, or if a path was included, verify that
the path is correct and try again.
At line:1 char:29
+ Get-OrganizationRelationship <<<<  |fl FreeBusyAccessEnabled,FreeBusyAccessLevel
    + CategoryInfo          : ObjectNotFound: (Get-OrganizationRelationship:String) [], CommandNot
   FoundException
    + FullyQualifiedErrorId : CommandNotFoundException
The term 'Get-OrganizationRelationship' is not recognized as the name of a cmdlet, function, script
 file, or operable program. Check the spelling of the name, or if a path was included, verify that
the path is correct and try again.
At line:1 char:29
+ Get-OrganizationRelationship <<<<  |fl FreeBusyAccessEnabled,FreeBusyAccessLevel
    + CategoryInfo          : ObjectNotFound: (Get-OrganizationRelationship:String) [], CommandNot
   FoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Open in new window

0
Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Murali ReddyExchange ExpertCommented:
How did you do the migration? Don't you have exchange 2010 servers in your setup?

Could you paste the results of this>?

Get-AvailabilityAddressSpace |fl
0
Murali ReddyExchange ExpertCommented:
Are you able to see the freebusy information of cloud mailboxes from onpremises?
0
Todd WilloughbyLead System EngineerAuthor Commented:
I ran the Get-OrganizationRelationship |fl FreeBusyAccessEnabled,FreeBusyAccessLevel commandlet in a regular powershell instance not a EMS instance. Below is the output I received when I ran the commandlet in EMS on my Exchange 2013 hybrid:

FreeBusyAccessEnabled: True
FreeBusyAccessLevel:      LimitDetails
0
Murali ReddyExchange ExpertCommented:
Sorry, is this your onpremise details or cloud instance?
0
Todd WilloughbyLead System EngineerAuthor Commented:
On-premises.
0
Murali ReddyExchange ExpertCommented:
Then your organization relationship is set to share the freebusy information with your cloud users. What are you using for synchronization, ADFS?

Just check when is the last sync happened.

Is it happening for all existing onpremise users or any new users?
0
Todd WilloughbyLead System EngineerAuthor Commented:
Honestly, I don't know what we are using to share the free/busy info; how would I check? A consultant is handling a lot of the configuration.

The issue of not being able to see calendars only affects on-prem to cloud and vice versa. All on-prem users can see each others' calendars but not on-prem to cloud.
0
Guy LidbetterCommented:
Are you running an Exchange 2010 Hybrid Deployment server?

It sounds like you may not have the correct domain names in the Organizational Relationship.

Does this look like your issue? http://support.microsoft.com/kb/2667844

Regards

Guy
0

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
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.