One of my clients had an issue trying to install an v2 extension-based hybrid worker in their #Azure tenant. Everything was working and then stopped, but no changes were made to the env. So we investigated deprecations, baseline changes, policies, etc. Nothing on the client side.

I ended up opening a case w/Microsoft Support. Got on a Teams call and gathered some data. Then ran into a permissions roadblock. Found out the client eng wasn't aware they had a CSP.

So the case was put on hold while they opened a new case through the CSP. Found out later that the 2nd MS rep is unable to link, or even access, the first case. Go figure. Then found out the case is actually being handled by an MS contractor. So, me > client > CSP > contractor > escalated to MS. Every email reply goes through a chain like this...

Interesting #powershell thing that seems to impact cloud service calls when the incoming request is parsed via JSON. If you pass an implicit boolean in a return object, it's actually parsed as "IsPresent":true/false. So an Azure runbook that expects a [boolean] will trigger an exception.

Try this (below) then try again after putting [boolean] in front of $SwitchParam in the result object.