According to the API page for Enable Account, a body is required, and that body is required to contain a value for forceProvisioning. The documentation for the Powershell SDK says the same thing for Enable-V2025Account. However, the task always returns an error.
When I use the developer tools in Chrome and enable the account via the UI, an empty body is passed. I was able to reproduce this in Postman. If I make the API call with a body:
{
“externalVerificationId”: “”,
“forceProvisioning”: false
}
The task that it generates fails. If I pass an empty body:
{}
The subsequent task is successful, and the account becomes enabled.
Since the Powershell cmdlet requires an -AccountToggleRequest parameter, and I cannot pass a $null. How do I get the cmdlet to accept an empty body, or is this a case where the API documentation is incorrect, so the SDK was assembled based on bad input?