Microsoft plans to remove the management of Exchange transport-rule based policies from the classic EAC in mid-2022. Given that Microsoft 365 DLP policies offer the same if not better functionality for Exchange Online and can process other workloads as well, it’s a good time to consider transitioning away from the older technology. Microsoft is obviously not putting any engineering effort into Exchange-based DLP, so there’s no good reason not to move over and use the technology they are investing in, The transition will take time and effort, but it will be worth it.
Find articles about implementing and managing compliance features for Office 365.
Along with the general availability of a new Graph Export API for Teams, Microsoft is introducing new licensing and charging models. Understanding the charging incurred for different uses will take some time to sort out and could pose real challenges for ISVs working in the migration space. Developers need to understand terms like model A and model B, seeded capacity, and consumption units and how these apply to their apps. The question now is if this is a test bed for Microsoft to apply similar charges to other APIs.
On November 1, Microsoft will limit auto-expanding archives to 1.5 TB and bring the era of “bottomless archiving” to an end. The new limit might not affect many Exchange Online tenants, but it’s a wake-up call for administrators to check how archiving is used in their tenants. To help the process, we’ve written a PowerShell script to report the current set of user and shared mailboxes with archives.
Microsoft would like Office 365 tenants to use Microsoft 365 retention policies instead of Exchange Online mailbox retention policies. Their stance is reasonable because Microsoft’s engineering effort is focused on workload-agnostic retention across the Microsoft 365 ecosystem. However, mailbox retention policies continue to offer some advantages that aren’t available in the Microsoft 365 equivalent. And they’re cheaper too because they don’t need Office 365 E3 or E5 licenses.
Microsoft insists that encrypted SharePoint and OneDrive for Business files found by eDiscovery searches can only be decrypted by Advanced eDiscovery, which requires Office 365 E5 licenses. This seems unfair, especially as Office 365 E3 tenants can create and use sensitivity labels to protect Office documents stored in SharePoint Online and OneDrive for Business. An example of not very joined up thinking when it comes to software licensing?