We are announcing the release of Microsoft Graph PowerShell SDK v2.19, which introduces backward compatibility support to address the issues some of our users encountered with versions 2.17 and 2.18. This release is designed to maintain productivity and efficiency in your scripting tasks, ensuring seamless support for the latest Graph API changes.

Understanding the recent changes

There are up to two minor Microsoft Graph PowerShell SDK releases that incorporate fixes and updates to reflect changes in the Graph API. However, versions 2.17 and 2.18, introduced an unexpected breaking change in existing cmdlet names due to a bug fix on our upstream OpenAPI services. We acknowledge that these changes might have potentially disrupted some of your scripts and workflows, causing inconvenience.

Impact: change in 26 v1.0 DELETE operations (‘remove-Mg*’ cmdlets) within the following modules: Microsoft.Graph.Applications, Microsoft.Graph.Groups, Microsoft.Graph.Education, Microsoft.Graph.Identity.DirectoryManagement and Microsoft.Graph.Identity.SignIns. See list of affected v1.0 cmdlets here and beta cmdlets here.

Who is impacted

If you have been using versions 2.17 or 2.18 and utilizing the impacted cmdlets, we strongly recommend upgrading to version 2.19. This new version supports users upgrading from previous versions and those who adapted to the compatibility changes introduced in versions 2.17 and 2.18.

Our response

We deeply value our community and your feedback, which is why we have launched a backward compatibility release to minimize the impact of these changes and maintain the recent enhancements:

Key Features of the Backward Compatibility Release

• Restoration of Deprecated Cmdlets: We’ve restored the cmdlets that were deprecated in version 2.17 to ensure your existing scripts continue to function without modification.
• Support for New Cmdlets: The new cmdlets introduced in version 2.17 remain available, allowing you to gradually transition to the updated commands.

Apology and commitment

We sincerely apologize for any inconvenience caused by the recent changes. Our goal is to continuously improve the Microsoft Graph PowerShell SDK to better serve your needs, and we regret any disruption that this may have caused. We are committed to learning from this experience and making the necessary adjustments to ensure smoother transitions in the future.

Thank you to our contributors

We extend a heartfelt thank you to all the contributors of the Microsoft Graph PowerShell SDK for your dedication and support. Your efforts in reporting issues, suggesting features, and enhancing our documentation have been crucial to our progress. Special thanks go to the contributors of Issue #2670 in our repository for capturing and contributing to the resolution of this critical issue.

Additional support

For any issues during the upgrade process or further inquiries, please visit our Microsoft Graph PowerShell GitHub repository.

Thank you for your understanding and cooperation as we continue to improve the Microsoft Graph PowerShell experience.