How to move service principal from Azure AD API to Azure Graph?

Question

I got an email from Microsoft stating I need to move a service principal from Azure AD Graph to Microsoft Graph. The link in the email takes me to page that shows Azure Active Directory Powershell is the affected resource, but I can't find it to move it. Where would it be located and how do I move it?

Answer 1

Hello @Carlton Whitmore,

You had received a recommendation for the application ID 1b730954-1685-4b74-9bfd-dac224a7b894 corresponds to a Microsoft first-party application known as "Azure Active Directory Powershell".

There is no direct way to move or migrate for the first party apps. Instead, you need to migrate your scripts to use the latest Microsoft Graph commands.

https://techcommunity.microsoft.com/blog/microsoft-entra-blog/action-required-azure-ad-graph-api-retirement/4090533

If you are using service principal login for applications like Azure Active Directory PowerShell, Microsoft Azure PowerShell or Microsoft Azure CLI, and the application is using Azure AD Graph APIs, it will show on the Migrate Applications recommendation. In this case, the application’s identity is registered in your tenant, and you must take action.

The below is the action required for Azure Active Directory PowerShell application which would eliminate the usage of Azure AD graph.

Appid	App Name	Action required
1b730954-1685-4b74-9bfd-dac224a7b894	Azure AD PowerShell	Azure AD PowerShell is deprecated and will be retired soon. You should migrate to Microsoft Graph PowerShell SDK. For more information, reference: Migrate from Azure AD PowerShell to Microsoft Graph PowerShell.

Scripts written in Azure AD PowerShell won't automatically work with Microsoft Graph PowerShell. The new cmdlet names have been designed to be easy to learn. Instead of using AzureAD or AzureADMS in cmdlet names, use Mg. For example, the cmdlet Get-AzureADUser is equivalent to Get-MgUser

Using the Cmdlet map, get the Microsoft Graph PowerShell equivalents for your cmdlets.

If you are not using any scripts involving Azure AD PowerShell, you can safely ignore this recommendation. If you are using the scripts involving Azure AD PowerShell, use the Cmdlet map, to use the latest commands.