Tom Piechota

Also needs checking all commands should throw a readable exception if there are permission/authorization errors.

I've forced an error in 5.1 (400 bad request), checking the full exception object from both invoke-webrequest and invoke-restmethod still doesnt show any further detail than this. Not sure what...

@liamjpeters Hey, thanks for this comment, interesting, I'll take a closer look this next week, haven't unfortunately had much chance of late! Hope things are going well!

This might also be a better method for parsing the script block pushed into Invoke-SNOWBatch, rather than using the current regex method. It's something to explore anyway.

I've tested Import-DefaultParamSet with the following additional code: ``` $Parsed = [System.Management.Automation.Language.Parser]::ParseInput($BaseCommand.Definition,[ref]$null,[ref]$null) $ParsedParams = $parsed.FindAll({$args[0] -is [System.Management.Automation.Language.ParameterAst]},$true) ``` Within the section that loops through the get-command $BaseCommand.Parameters, I'm also doing...

@peombwa - New-MgGroup has both HideFromAddressLists & HideFromOutlookClients as switches but these cannot be used when creating a group, an error is thrown to indicate a subsequent 'patch' request is...

@dimitertodorov Hey man! Awesome work, I really appreciate you putting time and effort into improving the module, I've not had a great deal of time myself this past year to...

Collapse, Fade and Grow work ok. But I can replicate the same issue with Zoom also

@timayabi2020 - The reason that I was using the search parameter is because this would typically automatically wildcard my search. So for example, if I had multiple access review definitions...

I'll be honest, I'm failing to understand how it's a service issue and not a build issue with the module or underlying dependencies (in which case I would have thought...