I came across the call to ‘https://mail.domain.com/EWS/mrsproxy.svc failed error while trying to move a mailbox from Exchange on-premise to Office 365. … Office 365 Mailbox Move Fails – The Remote Server Returned An Error (401) Unauthorized.Read More »
I was at a customer site who was having issues with Azure AD Connect not synchronizing shared and resource mailboxes to Office 365. In short, any accounts that is in a disabled state. … Azure AD Connect Not Synchronizing Shared and Resource MailboxesRead More »
Scripting Agent Initialization Failed: “File is not found” error came up during an Exchange 2016 Setup into an existing Exchange 2010 environment. … Scripting Agent Initialization Failed: “File is not found” Error During Exchange 2016 SetupRead More »
How to go past the ‘Adding Federated Domain’ status in the hybrid configuration wizard, while running from an Exchange 2016 CU7 server? … [Solved] Hybrid Configuration Wizard Stuck on ‘Adding Federated Domain’ StageRead More »
One of the first questions that you get from the security folks who will be involved in an Office 365 migration project is the actual location of the organization data. While you can broadly answer the locations as US, EU etc, I am sure they will want a more precise answer. … Figure Out Office …
Figure Out Office 365 Datacentre Locations In A Region Read More »
UK based organizations may have a requirement to have their data at rest in a UK based Office 365 datacentre. It may be to satisfy compliance requirements or due to the upcoming Brexit. Microsoft has an answer for organizations that fall in this category – move your data back! … Move Core Data Back To …
Move Core Data Back To UK Datacentres For Compliance Read More »
Failed move requests is a common occurance in any Exchange migration, whether it is to a new version of on-prem Exchange or to Office 365. One of the main reasons for a failed move is that there are more bad items in the mailbox than what is set on the move request. … Change Bad …
Change Bad Items Limit Of Failed Move Request On The Fly Read More »
A common problem that I have seen at client sites is the free/busy failure while looking up an on-premise mailbox from a migrated user. In this article, we will look at the common steps to troubleshoot the issue. … Free Busy Not Working From Office 365 To On-PremiseRead More »
Getting the mailboxes to which you have full access automatically mapped in the Outlook profile dates back to Exchange 2010. While it is a time saver in an on-premise deployment of Exchange 2010, how will things be when these mailboxes are migrated to Office 365 in a hybrid deployment? … Auto-Mapping Mailboxes After Office 365 …
Auto-Mapping Mailboxes After Office 365 Migration Read More »
When a federated user tried logging into Office 365 portal, the generic “We have received a bad request” error came up in the browser. The detailed information towards the bottom of the browser had a proper error. … AADSTS50008 SAML Token Is Invalid ADFS ErrorRead More »
