Blog Post

Microsoft Entra Blog
4 MIN READ

Automate and manage Azure AD tasks at scale with the Microsoft Graph PowerShell SDK

Alex_Simons's avatar
Alex_Simons
Icon for Microsoft rankMicrosoft
Jun 02, 2021
Howdy folks,   We’ve heard from customers that having a great PowerShell experience is critical in helping manage your identity needs at scale from automating tasks through scripts to managing us...
Updated Aug 19, 2021
Version 2.0
Alex_Simons's avatar
Icon for Microsoft rankMicrosoft
Joined May 01, 2017
View Profile
Microsoft Entra Blog
Stay informed on how to secure access for employees, customers, and non-human identities, from anywhere, to multicloud and on-premises resources, with comprehensive identity and network access solutions powered by AI.
JGrote's avatar
JGrote
Iron Contributor
Jun 02, 2021

Thank you for taking the time to publish and clarify the current roadmap.

 

Specifically in regards to users of the AzureAD module (clarify if I am wrong):

  1. Their stated roadmap is to migrate to the Microsoft Graph SDK, there will not be an equivalent "AzureAD" module that will be rewritten to use MS Graph SDK
  2. Some commandlets in Az are expected to be the "friendly" cmdlets, however today as far as I can tell these still use the legacy AzureAD Graph API, will these be updated to use MS Graph SDK? These will also be very limited compared to what is currently offered in the AzureAD module.
  3. There will be no other development of "friendly" cmdlets, the Graph SDK will primarily be the autogenerated cmdlets, with guidance coming in the form of documentation and examples.

My concern is that the Graph SDK has been stated to be just that, a software SDK for powershell developers to develop against the graph SDK. This leaves "normal" administrators in a difficult position. Is Microsoft expecting that the "Az" small friendly command set is all that will be invested in making the SDK available to bridge the gap for these administrators?

 

If so, then is Microsoft expecting there to be community led efforts to build modules that translate the SDK direct calls into more "friendly" commands normally associated with the AzureAD module? If so then that may be a major problem, as a standard AzureAD administrator-level user will look at the new graph SDK commands, consider them extremely difficult to use or unintuitive, and stay on the AzureAD module or bail entirely to use a different solution.