The AI Foundry Command Job job type submits an Azure Machine Learning Command job (run a script / binary on a compute target) in an Azure AI Foundry workspace. The template Command Job is identified by its job name — Polysync stores that in the External Id.
This job type is supported on the Azure AI Foundry platform.
name.AI Foundry Command Job (set automatically on
import).Optional job attributes (override template values per execution):
AI Foundry Compute Name — overrides properties.computeId.AI Foundry Environment Name — overrides properties.environmentId.AI Foundry Command — overrides properties.command.GET /jobs?api-version=2024-10-01&$filter=jobType eq 'Command'&$top=100
Identical to AI Foundry Pipeline Job
— Input / Input&Output values land in inputs with { value, type: "literal" },
and on completion properties.outputs populates Output / Input&Output
parameters.
Request body:
{
"properties": {
"jobType": "Command",
"displayName": "<polysync-name>",
"command": "<from-attr-or-template>",
"computeId": "<from-attr-or-template>",
"environmentId": "<from-attr-or-template>",
"inputs": {
"<name>": { "value": <typed-value>, "type": "literal" }
}
}
}
Identical to AI Foundry Pipeline Job:
PUT /jobs/{newJobName} with the body above.GET /jobs/{runId} with the same Azure ML status
mapping table.POST /jobs/{runId}/cancel.https://ml.azure.com/runs/{runId}
?wsid=/subscriptions/{subId}/resourceGroups/{rg}
/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}
command string using
${{inputs.name}} — Azure ML interpolates Polysync values at run
time.ComputeNotFound — the override compute name does not exist in
the workspace. Check the AI Foundry compute page.EnvironmentNotFound — the override Environment is missing or
not at the registered version. Use a fully-qualified
azureml:env-name:version style.