After moving some Mailboxes from Office 365 to Exchange 2013 on-premises and disabling licenses in the Office 365 portal I got the following warning on my computer (laptop and workstation):
Account Notice
We’ve run into a problem with your Office 365 subscription, and we need your help to fix it.
Continue reading We’ve run into a problem with your Office 365 subscription
I am working with a customer that’s running Exchange 2010 on-premises and want to move to Office 365 in a hybrid scenario. The hybrid servers are running Exchange 2010. After implementing a hybrid scenario everything was working fine, but after some time I received calls that free/busy wasn’t working correctly anymore.
When a user with a Mailbox in Exchange online and he wants to schedule a meeting with a Mailbox in Exchange 2010 on-premsises all goes well and the user can see all free/busy information from all users.
When a user with an on-premises Mailbox (on Exchange 2010) wants to schedule a meeting with a Mailbox in Office 365 free/busy information from a Mailbox that’s not Domain joined he cannot check the availability information from Mailbox in Exchange Online as shown in the following screenshot:
Continue reading Free/Busy cross-premises not working correctly
Customer wanted to enable the Exchange Online Archive on his Exchange Online Mailbox. Open the Exchange Admin Center, select the user and in the actions pane select “enable” under In-Place Archive. Continue reading Unable to perform the save operation when enabling Exchange Online Archive
After moving several users successful from Exchange 2013 on-premises to Office 365 at one point the migrated stopped (for some users) with the following error message: “You can’t use the domain because it’s not an accepted domain for your organization”:
Continue reading You can’t use the domain because it’s not an accepted domain
Recently I was doing a project with Exchange 2013 on-premises and Exchange Online in a hybrid configuration (with ADFS etc.). Exchange 2013 was connected to the Internet using a (Juniper) firewall, so no TMG involved. Exchange 2013 was functioning properly.
Continue reading The call to mrsproxy.svc failed. The HTTP request was forbidden
Jaap Wesselius 
You must be logged in to post a comment.