Connect Azure and run work in your subscription with its credits (Beta)
Beta. Choose Connect Azure, enter your directory and subscription IDs and run the shown script once in Azure
Cloud Shell. Nodus lists the subscription’s machines, its daily spend and its GPU vCPU quota on the All clouds page,
next to your AWS and GCP accounts. Nodus holds no secret: the script admits the Nodus app with read-only roles.
Beta, turned on per organization. On a connected subscription, choose Run work here, set a monthly credit
limit, run the second script once and choose Start running work here, or run
nodus cloud connect azure <name> --credit-limit 1000. Nodus places your single-node GPU work there first, then on
Nodus capacity as the account’s burst setting allows.
The script creates one resource group, a network that takes no inbound connection, and a role that changes only
that resource group. With the Reader role from connecting, it can also make a disk there from any image or snapshot
in the subscription; Nodus boots only its own marketplace image, and a subscription dedicated to Nodus keeps
private images out of reach. Machines get no managed identity and no usable SSH key.
When Azure refuses a machine for vCPU quota, Nodus skips that GPU family in that region, or the whole region for
the regional quota or when Azure does not say which, for an hour, and the account page links to the quota request.
To stop, disconnect the subscription in Nodus first, so Nodus deletes its machines, then delete the resource
group.