Microsoft has updated the Teams PowerShell module to allow it to run in a Cloud Shell session. This is good news if you need to run one or two Teams cmdlets without access to your normal workstation, but it’s not so good if you expect to run code which runs well in normal PowerShell sessions. The limitations which exist get in the way of getting work done, which is a pity.
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.
Why Microsoft 365 Audit Logs Lack Proper Fit and Finish
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.