Table of Contents
Microsoft Graph PowerShell SDK Updates Force Early Release of Automating Microsoft 365 with PowerShell
Recently, Microsoft released V2.41 of the Microsoft Graph PowerShell SDK, followed a few days later by V2.41.1 and V2.24.2 on October 14. Suffice to say that although V2.41 initially fixed a major longstanding issue, it also introduced some problems of its own that Microsoft subsequently addressed in V2.41.1 and V2.41.2 (released on October 16). So far, V2.41.2 looks solid. No assembly clashes and everything works as expected in Azure Automation with versions of PowerShell earlier than V7.6.
In any case, we’ve updated the Automating Microsoft 365 with PowerShell eBook to reflect the current situation and to include some new information. The new update is V29.2 and updated PDF and EPUB files are available to subscribers to download from Gumroad.com.
This update is also part of the November 2026 update for the Microsoft 365 for IT Pros (2027 edition) four-book bundle. Depending on what happens with Microsoft 365 PowerShell or Graph APIs before the end of the month, we might update the book again before the formal release of the November update on November 1, 2026.
Updating PowerShell
One question we are asked many times is whether it’s necessary to update to the latest version of PowerShell 7. Microsoft releases new builds of PowerShell 7 regularly (the latest build is 7.6.7 released on October 13, 2026). Downloading 112 MB and running the installation procedure to update PowerShell doesn’t take very long.
Even less effort is required if you choose the option to have Windows Update install PowerShell updates (Figure 1). If you use PowerShell regularly, enabling Microsoft Update support when installing PowerShell is a sensible choice because it removes the need to track new releases manually.
Given that it’s easy to keep PowerShell updated, I don’t see any harm in seeking to run the latest version on workstations. But it’s a personal choice and there’s no great harm done in running a slightly out-of-date version.
Error Handling
Another question we get is why the scripts available from the Microsoft 365 for IT Pros GitHub repository don’t include comprehensive logging and error handling. The answer is simple. We include basic error handling (think Try and Catch blocks) because the intention of the scripts is to illustrate principles, not to deliver production-ready code.
Take the example of the script to report file-level archiving for SharePoint Online sites. Anyone planning on using this code in their tenant is likely to extract the bits that do the heavy lifting, like interpreting the archive status for items held in document libraries and surround the code with whatever error handling and coding standards apply within their organization. We have zero knowledge of what those standards might be, so it’s not worth our while to write anything other than basic code. We leave the technical flourishes to you.
There’s no doubt that sometimes our code isn’t all that great. If you find problems in the code, please open an issue in our GitHub repository. Even if you don’t submit a fix, reporting problems helps us improve future versions. Feel free to use GitHub to fork the repository and suggest some pull requests to fix bugs and suggest code improvements in other ways. We’re not proud!
The Value of ePublishing and Automating Microsoft 365 with PowerShell
The flexibility of electronic self-publishing is great for authors who write about technical topics where the subject matter changes frequently, just like Microsoft 365. Readers benefit by always having books that contain up-to-date information. We leverage the benefits of ePublishing to the hilt and hope that you enjoy the latest update for the Automating Microsoft 365 with PowerShell eBook.
Remember, the link in your receipt will always fetch the latest version of our book files. We might not remind people when a new version (or point version) is available, so check when you have a moment.
As to the folks who bought the paperback version of Automating Microsoft 365 for PowerShell, we’re sorry that we cannot update words on printed pages. Perhaps that technology will come in the future, but for now all we can do is apologize.