Azure Resourcehealth Resourcehealth

Connector for the azure-resourcehealth-resourcehealth API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://management.azure.com
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• emergingissues_list — GET /providers/Microsoft.ResourceHealth/emergingIssues — Lists Azure services' emerging issues.
• emergingissues_get — GET /providers/Microsoft.ResourceHealth/emergingIssues/{issueName} — Gets Azure services' emerging issues.
• metadata_list — GET /providers/Microsoft.ResourceHealth/metadata — Gets the list of metadata entities.
• metadata_get — GET /providers/Microsoft.ResourceHealth/metadata/{name} — Gets the metadata entity.
• operations_list — GET /providers/Microsoft.ResourceHealth/operations — Lists available operations for the resourcehealth resource provider
• availabilitystatuses_listbysubscriptionid — GET /subscriptions/{subscriptionId}/providers/Microsoft.ResourceHealth/availabilityStatuses — Lists the current availability status for all the resources in the subscription.

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: emergingissues_list
# (attach an 'oauth' credential to the task — no inline secrets)