Every time Microsoft 365 Copilot interacts with a user, the Microsoft 365 substrate captures the Copilot interaction as a compliance record in the user's mailbox. By fetching and analyzing the compliance records, we can understand how the user interacts with Copilot. This article discusses how to retrieve and analyze the records with the Microsoft Graph PowerShell SDK.
Sometimes Microsoft 365 tenants need to store specific data for objects like users and groups. The Graph provides several extensibility options. This article describes how to define and use schema extensions to store information about the container management labels assigned to Microsoft 365 Groups.
Compliance search purge actions are Microsoft's search and purge tool. Today, a purge action is limited to removing 10 items per mailbox. Microsoft is increasing the limit to 100 as part of its eDiscovery modernization project. This article reviews the state of the art for using PowerShell to purge mailbox items and contemplates how purges might work after modernization finishes.
It's time to check recipient filters for dynamic distribution groups to ensure that you don't have any wildcard prefixes used with the -eq operator to find recipients based on their email addresses. A November 30 update will stop this kind of recipient filter from working and might have a knock-on effect on other processes.
The deployment of intelligent versioning to SharePoint Online worldwide is proceeding. Intelligent versioning is all about reducing the amount of storage quota consumed by file edits. It's a great idea, but it has one downside for many Microsoft 365 tenants: retention policies and labels stop SharePoint removing unwanted versions. Read more here, including a script to interpret Microsoft file version data.
Microsoft is giving Purview eDiscovery a make-over to introduce a modernized UI and to simplify the solution into standard and premium variants. Content searches are going away, but the same functionality is available as a standard case. It's time to prepare the folks who work on compliance and run eDiscovery investigations for the changes coming at the end of 2024/2025.
Oversharing of information is a major concern in the AI era. This article describes how to write a script to report file sharing for OneDrive for Business accounts. The report details the files shared, the type of sharing link and access, and who can access the files. It's an example of using the Microsoft Graph PowerShell SDK to understand what's happening in a tenant.
The room mailbox statistics script has proven to be a popular script downloaded and used by many to analyze the usage patterns of room mailboxes. Recently, a reader pointed out that the Graph API request to fetch workspaces didn't work. Microsoft has changed the Places resource and the request now needed to run against the beta endpoint. All of which brought me to rewrite the script using the Graph SDK.
Users receive all manner of notification messages from different sources. These messages are of no great value after a few days, so here's a script to find and remove messages to clean up mailboxes. All written using cmdlets from the Microsoft Graph PowerShell SDK.
Microsoft's big launch of Copilot Wave 2 featured many new capabilities, like a super-duper focused Inbox for Outlook (one that works this time), Python in Excel, and a profusion of agents for SharePoint Online. The idea behind agents is pretty good and should be valuable, even if IT might have some dark thoughts about how agents might allow people to access information that they shouldn't (this won't happen).
Three years ago, we described how to create organizational contacts in user mailboxes with Graph API requests. In this iteration, we read the contacts from a Microsoft list and use Microsoft Graph PowerShell SDK cmdlets to update user mailboxes. The techniques explained in the article can be used in many scenarios.
Microsoft plans a transition of the current Exchange Server licensing and support model to Exchange Server subscription edition (SE) starting in 2025. Organizations must prepare for the transition by upgrading servers to the latest cumulative updates of Exchange 2016 and Exchange 2019. The transition is unlikely to be seamless, but glitches can be avoided by good planning and careful monitoring of community discussions.
