Table of Contents
Part of the Office 365 for IT Pros February 2026 Release
The Office 365 for IT Pros team is delighted to announce that update #20 for the Automating Microsoft 365 with PowerShell eBook is available for subscribers to download. The updated files are available to subscribers of both Automating Microsoft 365 with PowerShell and Office 365 for IT Pros (2026 edition). We will issue the February 2026 update for the main book on February 1, 2026.
Please use the link in the receipt emailed after purchase or your Gumroad.com account to fetch the updated PDF and EPUB files.
We have also updated the Kindle and Paperback editions that are available from Amazon.com. Subscribers who purchase through Gumroad and want to read the book on Kindle devices do so by transferring the EPUB file to their device.
Updates and Revisions in Automating Microsoft 365 with PowerShell #20
Like all our monthly releases, update #20 contains a mixture of new material, updates, and revisions (including a few fixes). The book now includes coverage of the create Site Graph API mentioned last month. Since the API first appeared, Microsoft decided to drop the ability to create new sites linked to Microsoft 365 Groups. In addition, the API sadly lacks some essential functionality, such as adding members to newly created sites.
A new section addresses the question of how to create channel meetings for Teams. The feature is an example of an internal API in action because it’s not possible to create the same kind of channel meeting with the Graph APIs. The workaround is to create a personal meeting (a regular calendar event) and then post a notice about the meeting in the channel. This works, but the meeting doesn’t appear in the channel calendar.
New Version of the Microsoft Graph PowerShell SDK
Soon after we announced the availability of update #19 for Automating Microsoft 365 with PowerShell in December, Microsoft shipped V2.34 of the Microsoft Graph PowerShell SDK. The updated module appeared just 12 days after V2.33, so it came as a complete surprise. Soon afterwards, we reported that security was the prime driver for the accelerated release. However, the PowerShell gallery reports nearly 30 downloads of V2.33, which indicates that quite a number of people haven’t got the message that they should upgrade to V2.34.
I’ve been using V2.34 since its release and haven’t detected any problems over and above known issues, like the removal of the BodyParameter parameter for several directory-related cmdlets.
Exchange Online PowerShell and the Graph SDK
Microsoft updated the Exchange Online PowerShell module to V3.9.2 on January 5, 2026, The only real change is the introduction of the EXOModuleBasePath parameter to point to the folder where the module downloads its temporary module files on startup. I assume that the change is intended to give more control over where these files go. For example, if you run:
Connect-ExchangeOnline -EXOModuleBasePath c:\temp
You’ll end up with a temporary folder like C:\Temp\tmpEXO_gbdobe5j.d3j where Exchange Online stores downloaded definitions for many of its PowerShell cmdlets (functions).
OperationStopped: Could not load file or assembly 'C:\Program Files\PowerShell\Modules\ExchangeOnlineManagement\3.9.2\netCore\Microsoft.Identity.Client.dll'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
Or maybe the complaint about an error acquiring a token shown in Figure 1.
Running Connect-MgGraph after connecting to Exchange Online does not have the same problem. Assembly clashes remain a problem for Microsoft 365 PowerShell and are evidence of how teams in the world’s largest software company can utterly fail to cooperate around the use of common components. It’s a blessed mystery
If you’re looking for PowerShell code examples for Microsoft 365, why not visit the Office 365 for IT Pros GitHub repository. The repository holds over 300 scripts covering a wide range of situations.