Azure Windowsiot Windowsiotservices
Connector for the azure-windowsiot-windowsiotservices 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
oauthcredential. Mint one withitcli.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
operations_list— GET /providers/Microsoft.WindowsIoT/operations — Lists all of the available Windows IoT Services REST API operations.services_list— GET /subscriptions/{subscriptionId}/providers/Microsoft.WindowsIoT/deviceServices — Get all the IoT hubs in a subscription.services_listbyresourcegroup— GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.WindowsIoT/deviceServices — Get all the IoT hubs in a resource group.services_get— GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.WindowsIoT/deviceServices/{deviceName} — Get the non-security related metadata of a Windows IoT Device Service.services_checkdeviceservicenameavailability— POST /subscriptions/{subscriptionId}/providers/Microsoft.WindowsIoT/checkDeviceServiceNameAvailability — Check if a Windows IoT Device Service name is available.services_createorupdate— PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.WindowsIoT/deviceServices/{deviceName} — Create or update the metadata of a Windows IoT Device Service.
Inputs
- a linked
oauthcredential (no key inputs) — the server injects a freshAuthorization: Bearerfrom it operation— one of the operations above- path parameters when an operation's path contains
{...} query— optional JSON object of query paramsbody— JSON object for create/update ops
Example
operation: operations_list
# (attach an 'oauth' credential to the task — no inline secrets)