New Azure AD app name for Microsoft Graph PowerShell SDK and CLI
We would like to announce the new Azure AD application name for our Microsoft Graph PowerShell SDK and CLI. The name currently shown as Microsoft Graph PowerShell in the consent window will change to Microsoft Graph Command Line Tools effective May 2023.
The decision to change the Azure AD application name was made to better reflect the app registration that supports both the PowerShell SDK & CLI and to align with our continued support for command line experiences. We are confident that this change will better resonate with our customers and help us continue to provide you with the best possible product.
Please note that this change only affects the Azure AD application name of the SDK. This does not impact the features or functionality of the product itself, and there is no need to reconsent any permissions to existing apps that are already using PowerShell SDK and CLI. Please read the FAQs below for additional information. You can expect the same great performance and reliability that you have come to expect from our products.
We appreciate your continued support and look forward to serving you with our newly named SDKs. If you have any questions or concerns, please do not hesitate to reach out to PowerShell or CLI.
1. Where will this change be reflected?
This change will be visible if you take dependency on the Azure AD application (see FAQ #2 on how this applies) or in the consent window for both PowerShell and CLI SDKs where the name displayed will now be ‘Microsoft Graph Command Line Tools’.
2. Does this change affect me?
This change only affects any script that is currently referencing to the application name or service principal name explicitly.
For example, a script that does a comparison to the current Azure AD application name.
Application.DisplayName == “Microsoft Graph PowerShell”
ServicePrincipal.AppDisplayName == “Microsoft Graph PowerShell”
Should change “Microsoft Graph PowerShell” to “Microsoft Graph Command Line Tools”.
3. What if I have my own Azure AD application registration ?
This change does not impact customers with their own Azure AD application registration.
Visit us at Microsoft 365 Dev Center. Follow us on (@Microsoft365Dev) / Twitter for the latest news.
Wouldn’t a better fix to update code to match on ID, rather than a potentially attacker controlled display name? It would also prevent future updates to the display name from causing issues again.