Many organizations regard their people as their greatest asset. There is no disputing that the ability to hire great talent is a critical component to success, but in today’s pandemic-work-from-home world these great assets could also pose the greatest risk to your business. No amount of technology can account for human nature. You may already have invested in the best security solutions, but all it takes is a single click of a phishing email. I like to refer to this as a people problem – something that technology cannot solve entirely.
M365 - Exchange Online Center
ENow Software's Microsoft Exchange Online blog built by Microsoft MVPs for IT/Sys Admins.
While many of us are still holding onto summer, it is mid-September and Fall is just around the corner. And that means a fairly important Microsoft deadline will soon be upon us. As of November 1, 2021 only Outlook 2013 Service Pack 1 (with latest fixes) and later versions will be able to connect to Microsoft 365 services.
Two organizations each have Microsoft 365 tenants and they want to work together on several projects – some of which run for a limited time and some of which are ongoing. How can these organizations enable their people and teams to collaborate more effectively and productively across their different tenants? Add on top of this, how can this be done in a secure and compliant manner? This article describes several key collaboration options that administrators at each organization can consider as shared goals.
The third and final part of the Tenant to Tenant Migration series is about post-migration processing. In case you missed the first two parts, here is an overview of the content:
Almost every enterprise today is going through some type of transformation from historic compute solutions (i.e., “running IT in our data center”) to hybrid environments where workloads are distributed to specific locations, platforms, or providers based on business requirements. Even organizations seeking to be “cloud only” or “completely hyperconverged” will still have many environment types within their landscape. “IT everywhere” includes all the places we’d like to shift away from, like traditional corporate data centers, but won’t be able to due to technical debt and legacy systems.
In Part 1 of this blog series, we went through the topics of how to discover identities, workloads, data, and security for your tenant to tenant migration project. Part 2 of this series covers the migration itself, like which workloads can be moved, what needs to be done to prepare for the migration, what data can be migrated, if there are any gotchas to expect, and public available PowerShell scripts that make your life a little bit easier.
What (Common) Workloads Can Be Moved
The most commonly used workloads might be Exchange Online, Teams, SharePoint Online, and OneDrive for Business. As in the Microsoft cosmos, the Exchange Mailbox should always be the first workload for migration because several other features rely on the mailbox itself. Also, email was the first workload that could have been migrated to Microsoft 365 and it is still the biggest one. Teams’ one-to-one chats are stored in the mailbox itself; documents and files will be stored in SharePoint Online. OneDrive for Business is a storage within the personal SharePoint Online site, so all of them work closely together.
Microsoft 365 is not new. It’s been around for well over a decade, both in its current form as well as in its previous/current incarnation as Office 365, and before that we knew it as BPOS / Microsoft Online Services.
Welcome to part two of Addressing the Office 365 Monitoring Gaps. In part 1, Michael Van Horenbeeck discussed the differences in monitoring cloud-based systems vs traditional on-premises deployments.