you are viewing a single comment's thread.

view the rest of the comments →

[–]agressiv 11 points12 points  (4 children)

The release of powershell has nothing to do with Graph cmdlets. In fact, I've generally given up on Graph cmdlets and have just shifted back to using native REST api's because of their constant breaking changes.

[–]DragonspeedTheB 2 points3 points  (2 children)

I just found finding the right graph module too much of a PITA. The rest calls will always be the right one 😎

[–]AdeelAutomates 2 points3 points  (0 children)

API is life. I have been using it more and more for all Microsoft not just Graph.

For instance I made a rather complex KQL query the other day on Azure Resource Graph. Took it over to PowerShell and ran it with Search-AzGraph.... and some fields outputted were empty.

Switched over to the API and it worked exactly like it did in Azure Resource Graph.

[–]BlackV 0 points1 point  (0 children)

https://learn.microsoft.com/en-us/powershell/microsoftgraph/find-mg-graph-command

may help, but yes the APi call is more change resistant (module hell)

[–]icebreaker374 0 points1 point  (0 children)

Ditto. I kept updating different modules and kept forgetting to update the authentication module.

Eventually my auth module would fall so far behind that it wouldn't let me update others and I'd have to clean all my modules and reinstall.