Azure Security Securitycontacts

Connector for the azure-security-securitycontacts 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

• securitycontacts_list — GET /subscriptions/{subscriptionId}/providers/Microsoft.Security/securityContacts — Security contact configurations for the subscription
• securitycontacts_get — GET /subscriptions/{subscriptionId}/providers/Microsoft.Security/securityContacts/{securityContactName} — Security contact configurations for the subscription
• securitycontacts_create — PUT /subscriptions/{subscriptionId}/providers/Microsoft.Security/securityContacts/{securityContactName} — Security contact configurations for the subscription
• securitycontacts_delete — DELETE /subscriptions/{subscriptionId}/providers/Microsoft.Security/securityContacts/{securityContactName} — Security contact configurations for the subscription
• securitycontacts_update — PATCH /subscriptions/{subscriptionId}/providers/Microsoft.Security/securityContacts/{securityContactName} — Security contact configurations for 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: securitycontacts_list
# (attach an 'oauth' credential to the task — no inline secrets)