We begin season three of the Practical 365 podcast discussing the biggest news for Exchange Hybrid organizations in a long, long time – including the renaming of Azure Purview to Microsoft Purview and what that means. It’s all time for change in the world of Microsoft 365 compliance.

Removing the Last Exchange Server

Before we get into Azure purview now renamed as Microsoft purview, and the associated language that goes along with that – we take a deeper dive into removing the last Exchange Server. You will certainly have heard about this by now if you’ve followed Practical 365, or the Exchange Team Blog: You can now remove the last Exchange Server, after moving to Exchange Online.

We discuss how, what to be concerned about – and how we will actually be able to do this. We note that it’s the Management-Tools Only Installation using the Exchange Server 2019 CU12 install. Fundamentally – Do. Not. Uninstall. Your. Exchange. Server.

The result will be bad – you can remove it permanently though, and you can use the installer to add the Exchange Management tools into a new forest for “greenfield” installs. No mail relay capability is included, and it’s PowerShell only:

Read more in my blog: Don’t Remove the Last Hybrid Exchange 2019 Server Just Yet

But wait, there’s more! Those announcements from Microsoft brough a new servicing model for Exchange with some added bonuses. Here’s a synopsis:

  • A six-monthly model – H1/H2 CUs for Exchange 2019
  • Exchange 2016 will get security updates
  • A “Free” Hybrid license for Exchange 2019
  • On-Premises Server bug Bounty – $500 – $30K if you find bugs

Read more from Tony Redmond’s blog: Microsoft Revamps Exchange On-Premises Servicing Model

Microsoft Purview

Azure Purview was renamed Microsoft Purview, but also – Everything under compliance & data governance is Microsoft Purview. Well, unless it’s Azure AD related governance that is, or Teams-related governance.

Every Microsoft MVP has been tweeting the diagram you’ll find in the link below, so to make things clear as mud, here’s our handy table “How to Purview it” table for working out what things are called now:

It wasMake it Purview
It was “Microsoft 365/Office 365/Azure/Microsoft” + Product NameIt’s now “Microsoft Purview” + Product Name
You know it as MIPNow you call it MPIP*
(Or maybe you’ll carry on calling it MIP, because people know that)
Product + “in/for Microsoft 365”Microsoft Purview + Product
Where it says “Advanced”Remove that and add “(Premium)”
What was “Information Governance”Is now “Data Lifecycle Management
It’s not “Microsoft 365 compliance center”It’s now “Microsoft Purview Compliance Portal”
It’s not “Azure Purview Portal”It’s now “Microsoft Purview Governance Portal”
Table 1: The Practical 365 “intentionally hard to understand, but probably just as easy to remember” guide to Purview renaming.

If you look at the documentation, and assume when it says Microsoft Purview, it means all of it – it means just the old Azure Purview bits. Much the same goes for the pricing, we think – you don’t get the lot in the “pay as you use model.”

Join us next week for episode two, where we’ll be getting back into the swing of reviewing the roadmap, and much more.

About the Author

Steve Goodman

Technology Writer and Chief Editor for AV Content at Practical 365, focused on Microsoft 365. A 12-time Microsoft MVP, author of several technology books and regular Microsoft conference speaker. Steve works at Advania in the UK as Field Chief Technology Officer, advising business and IT on the best way to get the most from Microsoft Cloud technology.

Leave a Reply