Tony Redmond

Microsoft has put a huge amount of emphasis on Office 365 Groups as the basis for team-based collaboration for its cloud service. Collaboration often requires input from external people and that hasn’t been possible until now. The announcement of external user support for Office 365 Groups is welcome, even if it is restricted in part.

Migration of legacy archives like Enterprise Vault are often left as the last part of the journey from on-premises servers to Office 365. A wide range of third-party migration tools are available, but many complex twists and turns await the unwary as they cope with journal reports, archive mailboxes, splitting and explosions, and the sheer amount of data to be migrated. It’s an interesting problem to solve.

Office 365 Connectors allow data drawn from multiple internet sources like Twitter to be imported into Office 365. This article explains why imported tweets result in multiple SendAs events logged in the Office 365 Audit log.

The Office 365 Import Service does a good job of “bringing data home” by ingesting PST files and other data into Exchange Online mailboxes and SharePoint Online libraries. But sometimes you just want to do your own thing – and you can with the New-MailboxImportRequest cmdlet.

By the time Microsoft Ignite happens in September 2016, the Outlook app for iOS and Android will have an all-Microsoft infrastructure. The Amazon-based cache is being replaced by a new architecture that is shared by Exchange Online, Exchange on-premises and non-Microsoft email servers like Gmail. It’s a big change and it’s happening now.