This cmdlet is part of a Preview module. Preview versions aren't recommended for use in production environments. For more information, see https://aka.ms/azps-refstatus.
create a solution for the specific Azure resource or subscription using the inputs 'solutionId and requiredInputs' from discovery solutions.
<br/> Azure solutions comprise a comprehensive library of self-help resources that have been thoughtfully curated by Azure engineers to aid customers in resolving typical troubleshooting issues.
These solutions encompass (1.) dynamic and context-aware diagnostics, guided troubleshooting wizards, and data visualizations, (2.) rich instructional video tutorials and illustrative diagrams and images, and (3.) thoughtfully assembled textual troubleshooting instructions.
All these components are seamlessly converged into unified solutions tailored to address a specific support problem area.
Each solution type may require one or more 'requiredParameters' that are required to execute the individual solution component.
In the absence of the 'requiredParameters' it is likely that some of the solutions might fail execution, and you might see an empty response.
<br/><br/> <b>Note:</b> <br/>1.
'requiredInputs' from Discovery solutions response must be passed via 'parameters' in the request body of Solutions API.
<br/>2.
'requiredParameters' from the Solutions response is the same as ' additionalParameters' in the request for diagnostics <br/>3.
'requiredParameters' from the Solutions response is the same as 'properties.parameters' in the request for Troubleshooters
create a solution for the specific Azure resource or subscription using the inputs 'solutionId and requiredInputs' from discovery solutions.
<br/> Azure solutions comprise a comprehensive library of self-help resources that have been thoughtfully curated by Azure engineers to aid customers in resolving typical troubleshooting issues.
These solutions encompass (1.) dynamic and context-aware diagnostics, guided troubleshooting wizards, and data visualizations, (2.) rich instructional video tutorials and illustrative diagrams and images, and (3.) thoughtfully assembled textual troubleshooting instructions.
All these components are seamlessly converged into unified solutions tailored to address a specific support problem area.
Each solution type may require one or more 'requiredParameters' that are required to execute the individual solution component.
In the absence of the 'requiredParameters' it is likely that some of the solutions might fail execution, and you might see an empty response.
<br/><br/> <b>Note:</b> <br/>1.
'requiredInputs' from Discovery solutions response must be passed via 'parameters' in the request body of Solutions API.
<br/>2.
'requiredParameters' from the Solutions response is the same as ' additionalParameters' in the request for diagnostics <br/>3.
'requiredParameters' from the Solutions response is the same as 'properties.parameters' in the request for Troubleshooters
The DefaultProfile parameter is not functional.
Use the SubscriptionId parameter when available if executing the cmdlet against a different subscription.
scope = resourceUri of affected resource.<br/> For example: /subscriptions/0d0fcd2e-c4fd-4349-8497-200edb3923c6/resourcegroups/myresourceGroup/providers/Microsoft.KeyVault/vaults/test-keyvault-non-read
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
-InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable,
-ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see
about_CommonParameters.
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
