Misleading documentation for Azure Automation Runbook API usage - Parameter as JSON data
The documentation for the Azure Automation API usage regarding using the runbook parameter as JSON data is misleading, not consistent.
The documentation https://docs.microsoft.com/en-us/azure/automation/runbook-input-parameters#passing-a-json-object-to-a-runbook is stating:
"It can be useful to store data that you want to pass to a runbook in a JSON file. For example, you might create a JSON file that contains all parameters that you want to pass to a runbook. To do this, you must convert the JSON code to a string and then convert the string to a PowerShell object before passing it to the runbook."
But the documentation https://docs.microsoft.com/en-us/azure/automation/runbook-input-parameters#start-a-runbook-by-using-the-rest-api-and-assign-parameters is stating that "any valid JSON data" can be passed as parameter value which is unfortunately not correct / working:
Runbook parameters: Optional. A dictionary of the parameter list in (name, value) format, where name is of type String and value can be any valid JSON value.
Please update the documentation according the findings in the microsoft case 120022622002204, so that only string is a valid parameter value.
I place this as a feedback here based on the suggestion in the microsoft case 120022622002204