With the pace of Office 365 adoption globally, many administrators will inevitably find themselves in a position where they need to manage more than one tenant simultaneously. When managing at scale, PowerShell allows authentication to multiple tenants using different PowerShell instances. Profiles and containers are a great way to operate across multiple tenants and accounts without going through cumbersome sign-out processes and closing browsers.
This article examines the different components of Defender for Office 365, and how you can customize the configuration beyond the baselines to enhance the relevance and impact the policies have on your tenant. The most important aspects to review when modifying the configuration from baselines and the reasons to consider each configuration option are highlighted, but they don’t take you all the way. The items listed here are a subset of what’s available, but when combined with the baselines will help you to bring your Defender implementation to the next level.
Azure B2B guest accounts are often created during a Merger & Acquisition, so teams from both organizations can easily collaborate during the business and technology integration. However, these external users with B2B Guest accounts in their directory will eventually need to be migrated, which is problematic since B2B Guest accounts aren’t recognized as being licensed. The guest account can be removed and a new one created, but previous permissions would be lost. So how do we preserve permissions, keep collaborating without managing two sets of credentials while preparing the user account for data migrations? This article walks you through a solution that can be used in certain situations to help you easily manage the account to meet your needs.
So, you’ve completed your migration to Exchange Online. Email flows smoothly into and out of the cloud, and all your mailboxes are now online. What’s next for your Exchange Servers, now that you’ve made the transition?
After completion you will have several tasks to perform to remove Exchange Servers from your environment, but there is one important caveat you need to know about; if you run Azure AD Connect then you can’t remove every Exchange Server from your environment. You will need to keep at least one around for management purposes. In this article, I’ll walk through what you can do to minimise what you keep and need to maintain, and what you can consider planning for in the future. You can also join me at TEC this week, on September 2nd.
After a decade of no price increases for Office 365 licenses, Microsoft plans to introduce new pricing effective March 1, 2022. The uplifts range from $3 to $4 extra per user per month. This doesn’t sound much, but an extra $36 per user per year for Office 365 E3 quickly mounts up. And when you look at the overall installed base, some eyewatering numbers are involved. While we might complain about increases, I still think Office 365 and Microsoft 365 are reasonable value.