“Ding ding ding, and that is the end of round three here at the Melbourne arena. And we can see TinyBreak is getting his ass kicked here tonight, right Jeff?”
“Thats right Bill, this vs match of TinyBreak v Powershell promised to deliver, but it has not gone well today for the self proclaimed engineer”
“Correct Bill. From sketchy ChatGPT scripts, to issues importing the graph module and the outright failure of some Microsoft scripts using the AzureAD module its a bloody mess out there. Frankly, if you were TinyBreak’s coach you’d be recommending he pull the plug on this fight before taking any more abuse”
“Ding ding ding, and that is the end of round three here at the Melbourne arena. And we can see TinyBreak is getting his ass kicked here tonight, right Jeff?”
“Thats right Bill, this vs match of TinyBreak v Powershell promised to deliver, but it has not gone well today for the self proclaimed engineer”
“Correct Bill. From sketchy ChatGPT scripts, to issues importing the graph module and the outright failure of some Microsoft scripts using the AzureAD module its a bloody mess out there. Frankly, if you were TinyBreak’s coach you’d be recommending he pull the plug on this fight before taking any more abuse”
🤣🤣🤣
Something about the module having >4096 cmdlets and and being too big to load? I hit this last week, it was most infuriating.
yeah forgot to define the scope of graph to users. Was annoyed at that too!
Agreed. If you can’t load it without setting scope, then scope should be a mandatory parameter.