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?
Find articles about implementing and managing compliance features for Office 365.
Microsoft announced a bunch of changes for Microsoft 365 records management on May 19. The most interesting changes are allowing all licenses Office 365 accounts to use Teams retention policies and the advent of adaptive scopes for retention policies, both of which should be useful for many tenants. The announcement also covers multi-stage disposition reviews. If you know what that means, you’ll be excited. If not, you won’t.
When it comes to eDiscovery and which solution is right for your organization, “you get what you pay for.” Microsoft 365 services are no different – you’re either willing to pay for them or you aren’t. Some organizations will not need or want to pay for Advanced eDiscovery, while others will find it an essential purchase. Regardless of which camp your organization resides in, Microsoft provides customers with the flexibility to choose between two eDiscovery tools best suited for your needs.
SharePoint site and information architecture has been around long enough to be an established practice and area of expertise in the SharePoint world. What’s new about it, however, is its elevated role in Microsoft 365 compliance. Architectural decisions made in a tenant can have lasting, follow-on effects which information architects need to be aware of. This post highlights some key points about how these decisions can affect managing compliance at scale by providing structure and governance to SharePoint.
The audit events generated for license assignments to user accounts available in the Azure AD audit log and Office 365 audit log are inconsistent and incomplete. This is certainly true for licenses assigned to accounts through auto-claim policies and group-based licensing, but known gaps exist in the audit records generated in other areas of Office 365 and Microsoft 365 functionality. We think Microsoft needs to pay attention to ensure that auditing works consistently and predictably across all workloads. Once they improve the fit and finish of audit record generation, they can move into other areas, like charging for access to high-value audit events.