Inconsistencies in Microsoft 365 Licensing for Security and Compliance

with 1 Comment by Tony Redmond

The new licensing guidance for Microsoft 365 security and compliance features is welcome, but as is probably inevitable, some inconsistencies exist that need to be probed and discussed, and hopefully resolved by Microsoft in the long run. Why do DLP policies for Teams need E5 licenses? Why does applying a default retention label to a SharePoint library need E5? There's lots to discuss about issues Microsoft should fix.

The Confusing World of Microsoft 365 Security and Compliance Licensing

by Tony Redmond

Licensing the range of Microsoft 365 compliance and security features is a task taken on by the bravest. Or so they say. Another way of putting it is that people just don't understand what licenses are needed for the different compliance, data governance, and security features. A new Microsoft 365 Compliance plan and three sub-licenses might make it easier, even if they're more expensive. After reading the PDF to explain what licenses are needed, maybe you'll know what you need to buy.

AAD Licensing for Groups and Teams Features Burdens Office 365 Tenants

by Tony Redmond

Microsoft clarified what AAD features need premium licenses at Ignite. Tenants need many of those features to control Office 365 Groups and Teams, and some of the listed features are surprising. Did you know that the group creation policy is a premium feature? Or adding a default classification. The chosen set of features seems odd, but at least Microsoft is now clear about what you must license.

Post-Ignite 2017 Reflections About Office 365

by Tony Redmond

After returning from the Ignite conference, I have pages of notes to pour over. Here are some of the more interesting things i learned about Office 365, including who should be in my "inner loop" and "outer loop", why Microsoft talks about Microsoft 365 when they really mean Office 365, and some Exchange Online cmdlets I had not heard about before.