Azure AD PowerShell to Microsoft Graph PowerShell migration FAQ

This article provides answers to frequently asked questions about migrating from Azure AD PowerShell to Microsoft Graph PowerShell.

What happens to Azure AD PowerShell come June 2023?

In June 2020, we announced the retirement of Azure AD Graph API in favor of the Microsoft Graph API, which provides all the functionality of Azure AD Graph along with new functionality. As a result, all applications calling the Azure AD Graph API would receive an error message from the endpoint after the original proposed retirement date of June 30, 2022. Azure AD PowerShell is one of the applications that utilizes the Azure AD Graph API.

Azure AD PowerShell will continue to function after June 2023 to allow users more time to migrate to Microsoft Graph PowerShell. Customers can migrate to Microsoft Graph PowerShell with a phased shutdown of the Azure AD Graph endpoint. We encourage you to migrate to Microsoft Graph PowerShell.

What is Microsoft doing about the gaps in functionality between Azure AD and Microsoft Graph PowerShell modules?

As part of the parity work, we're looking at the MSOnline (MSOL) and Azure AD PowerShell cmdlets and mapping the functionality to Microsoft Graph PowerShell. This ensures that all existing scenarios are available in Microsoft Graph PowerShell. To help with migration, see the cmdlet map of MSOnline and Azure AD PowerShell cmdlets to Microsoft Graph PowerShell.

Users have also reached out with specific scenarios and cmdlets that we'll add to Microsoft Graph PowerShell. We've added tools such as the Find-MgGraphCommand and Find-MgGraphPermission to help you find and use the appropriate Microsoft Graph PowerShell cmdlets.

What is Microsoft doing to improve the Microsoft Graph PowerShell user experience?

Microsoft Graph PowerShell cmdlets are autogenerated from the Microsoft Graph API schema. The process has its advantages, for example, providing a rich set of cmdlets that cover the whole API landscape. The disadvantage is that the resultant cmdlets may not be user-friendly compared to human authored cmdlets. Consequently, we're actively working on usability improvements.

The Microsoft Graph PowerShell SDK is also open source and users can contribute to the usability work or add new scenarios to manage Azure AD.

How is Microsoft going to support users who are migrating to Microsoft Graph PowerShell?

We're working on additional tools that will help migrate existing scripts that target Azure AD PowerShell so that these scripts can use Microsoft Graph PowerShell cmdlets instead.

Send us your feedback or suggestions on how we can improve Azure AD management within Microsoft Graph PowerShell SDK by logging an issue.