Creating Cloud Authorization for Azure
To allow Resource Manager to schedule jobs using your Azure account, you must first authorize MissingLink to access the account using standard Azure authorization.
From the outset, be aware that any and all MissingLink activity in your Azure account is tracked and available as part of Azure's activity log link. In addition, the access you grant MissingLink can be revoked from your Azure account at any time.
The procedure itself involves a few short commands.
Before you enable authorization, ensure that you have:
- Installed MissingLink's CLI as detailed here.
Properly configured Azure on the host. Run the following commands:
pip install --user azure-cli aws configure
For more information, see Install the Azure CLI.
Granted your user administrator's privileges to access your Azure subscription.
- (Optional) Created a separate SSH key to be used by MissingLink for Git cloning and other encryption related operations. By default, your default SSH key will be used. For more information, see Using confidential data.
The basic authorization command is:
ml resources azure init
In addition, you can use the following additional flags:
ml resources azure init --location TEXT --queue TEXT --acr ACR_NAME
--locationspecifies which location to use to host all the entities like worker instances and the default storage account.
--queuespecifies the queue to use at cloud initialization.
--acrauthorizes access to Docker images in a private ACR. See details about the
--imageflag when running jobs that require access to private ACRs.
For more information about the command, see the CLI reference.
The authorization process takes a few minutes. The outcome is a basic, default resource group for this authorization. The resource group is configured with a capacity of one Standard_NC6s_v3 instance. You can use MissingLink's dashboard or the
ml resources group command to modify the configuration.