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?
About Tony Redmond
Microsoft 365 and Office 365: Microsoft’s Confusing Branding
The recent 10th anniversary of the launch of Office 365 brought some questions about the demarcation between Office 365 and Microsoft 365. For instance, do I have an Office 365 tenant or is it a Microsoft 365 tenant? Is a feature part of Microsoft 365 or does it belong to Office 365? And why does Microsoft insist on calling its desktop Office apps Microsoft 365 Apps for enterprise? Welcome to the bizarre world of branding, and that’s before throwing Windows 365 into the mix.
Teams Chat Becomes Fluid (or Lively)
Teams is the first major Microsoft 365 application to ship support for Fluid components. Teams chats can include components like a task list, checklist, table, or paragraph. When a live component is sent to other chat participants, everyone involved in the chat can edit and update the component. It’s a new way of collaborative working which challenges traditional approaches. Fluid components will also find their way into applications like OneNote, Outlook, and Whiteboard. Looks like a good thing, but how do these components work in practice?
Using the Service Communications API to Report Service Update Messages
The Office 365 Service Communications API allows tenant access to service update message data, just like you see in the Microsoft 365 admin center. This article explores how to use the API to fetch service messages and report them in different formats, including HTML and even as a Word document.
Microsoft Is Moving the Office 365 Service Communications API to the Graph
Microsoft is moving the Office 365 Service Communications API to the Microsoft Graph. The new API is in public preview. Converting PowerShell scripts from the old API to the new isn’t particularly difficult if you have ever worked with the Graph before. As always, the devil is in the detail, but persistence and some mild swearing should be enough to get scripts over the line. This article explores how to use the new API to fetch and report details of service incidents.