In the past few months, even the more conservative on-premises Exchange admins have at least considered migration to Office 365 (Microsoft 365). And, to be honest, they have (or would have) joined the majority. As the businesses operate in the cloud, companies more frequently look for the steps for a tenant-to-tenant migration. While those migrations have various grounds (mergers and acquisitions being the most common), they all have one thing in common – they require quite a lot of effort from IT teams.
In 2020, Microsoft introduced a native way to perform this type of move. However, it’s difficult to call this approach a convenient one – it requires a lot of manual configuration and running scripts in Exchange Online PowerShell. Moreover, the functionality is still in preview stage and is lacking some important features, e.g. the migration of public folders is currently not being supported. Microsoft still suggests using a third-party tool to accomplish this administration task. Having this in mind, I will show you how to easily migrate mailboxes between Office 365 tenants using CodeTwo Office 365 Migration.
Microsoft has been promoting Viva for nearly 2 years now as ‘an employee experience platform that brings together communications, knowledge, learning, resources, and insights in the flow of work.’ Maybe it’s just me, but this description doesn’t really explain what Microsoft Viva is, and what to expect from it. That’s why I dived into this subject to give you a straightforward description of Viva, admin to admin.
Whether your company has been using mobile devices for years or is just implementing them in the workplace, it’s good to know how to manage them. Certain Microsoft 365 plans give you access to Intune (Microsoft Endpoint Manager) which lets you configure all devices. In this guide, I’ll show you how to deploy and configure Outlook for Android app. But before that, you’ll see how to pre-configure Intune to seamlessly deploy any Google Play Store app in your organization.
In this article, I am going to show you how to use the Search-Mailbox PowerShell cmdlet together with the-DeleteContent switch to delete email (and other item types) from multiple mailboxes on Microsoft Exchange Online, as well as on-premises Exchange.
Merging Office 365 (Microsoft 365)* tenants is about migrating mailboxes from one or more tenants to another. In other words, it’s a tenant-to-tenant migration, but the context is that the target tenant is already inhabited. This article explains how to merge Office 365 tenants in the easiest way.
*While the article is about how to merge Office 365 tenants, a quick foreword is in order. It’s been almost two years since Office 365 was renamed to Microsoft 365. After all this time, both names are used but, in most cases, people seem to prefer the shorter version – Office 365. That’s why throughout the article, I’ll use Office 365 (referring to Microsoft 365 at the same time) to make things more concise.
Mailbox migration is a complex process which requires technical skills and knowledge of both the source and the target environment. One of the questions that comes up while planning the migration is roles and permissions required to successfully execute the migration. You could drop the subject by simply stating “get global admin if it’s Microsoft 365 (Office 365) and Organization Management role when on-premises”. However, your company might have a strict policy to follow the principle of least privilege. That’s when knowing the exact required permissions comes in handy.
To create mailboxes in Microsoft 365 (Office 365), you can use the admin center or PowerShell. Both methods support individual and bulk creation methods. See step-by-step instructions on how to create user or shared mailboxes in your Microsoft 365 tenant.
Microsoft 365 admins have many tools they can use to secure documents and emails. One of those tools is a sensitivity label. I’ll explain in detail what a sensitivity label is, how to set it up and test if it works well.
Shift to the cloud is affecting all IT fields, including device management where Microsoft Intune is getting more and more popular at the cost of solutions such as Group Policies or Microsoft Endpoint Configuration Manager (MECM).
Update: This post was updated on August 8, 2022, as the Plus Addressing feature is currently turned on by default in all organizations.
Listening to the users’ voices, Exchange Team finally deployed the Plus Addressing feature (aka subaddressing or Dynamic ‘+’ Email Aliases) in Exchange Online in October 2020. The feature was literally won over by Exchange admins, getting 6589 votes on UserVoice (back when UserVoice was still used to collect feedback) and becoming the top requested one at the same time.