PowerShell Graph SDK API

[Bugzi]

Hello,

 

Has anyone got any experience with the new PowerShell Graph SDK api please?

 

I'm looking at converting our current scripts over to this but it seems the commands for Teams don't seem to support basic error handling.

 

For example if I put "New-MgTeam -BodyParameter $params" into a Try / Catch and the command throws an error, Catch just doesn't seem to get triggered.

 

Wondering if there is a workaround or such for this please?

 

Thanks

[psydii]

I can't help. However I can say that the team behind this have nothing but contempt for those whom they allege to serve.

 

Let me introduce you to a command I stumbled across today:

 

Get-MgDeviceManagementDeviceCompliancePolicySettingStateSummaryDeviceComplianceSettingState

 

Yes that is a 91 character command, and the first parameter name of this command is 23 characters long, and that takes a GUID.

 

 

Nobody on the team behind this godforsaken monstrosity of a system have ever run a human scale system, nor do they understand why things like Bash and PowerShell exist, nor do they have any understanding of the importance of the philosophical differences between *nix and NT.

 

The team at Microsoft get tools written by past and future colleagues, why do they feel that giving us a thinly wrapped API is sufficient for us to happy and productive? The PM behind this should be given an internet disconnected machine, a kernel, a file system and and a compiler, and told to get on with their job.

[chaplic]

I've been doing a lot with Graph API in powershell before these new modules and dont really see the benefit of the autogenerated cmdlets. If I use the 'real' graph API call then I can repro what I'm doing using the Graph API explorer.

[psydii]

I shouldn't have to, as a systems administrator/operator, be anywhere near an API on a daily basis. Powershell is supposed to expose useful capabilities in commandlets, not require me to read developer documentation to get *anything* done.

 

Of course calling the API directly is extremely powerful, and great that we *can*, but we should not *have* to.

 

Does the Powershell Graph API team have to code their own Email Client and Server, or do they use Outlook/365?

 

That Powershell Graph API adds no value to and admin who has managed to get the hang of calling the API directly from Powershell, really speaks volumes as to what Microsoft think of us.

 

The problem is that it is designed by engineers building a global scale service, however their customers need to get work down at people scale.

[psydii]

Here's a quiet little announcement by the Powershell Graph SDK PM , it suggests Microsoft are (finally) building powershell cmdlets useful getting actual things done in Entra/(and 365?) again:

 

We should see something in the next couple of months.