Azure Quantum Submit Job and Retrieve Results
A 4-step recipe with Microsoft Azure Quantum. We can help you get access.
Recipe · 4 steps
Azure Quantum Submit Job and Retrieve Results
Stage storage, submit a quantum job, poll to completion, and return its output URI.
- Request a container SAS URI so input data can be staged into the workspace storage that the job will reference.
- Create the quantum job referencing the SAS container URI, the input/output formats, and the quantum computing item count.
- Read the job status. Repeat this step while the job is still running and branch to completion handling once it reaches a terminal status of Succeeded, Failed, or Cancelled.
- Confirm the job succeeded and capture the output data URI and format where the quantum results were written.
What you'll need to have ready
- subscriptionId: The Azure subscription identifier that owns the workspace.
- resourceGroupName: The resource group containing the Quantum workspace.
- workspaceName: The name of the Azure Quantum workspace.
- apiVersion: The data-plane api-version, e.g. 2026-01-15-preview.
- authToken: The Azure AD bearer token (without the "Bearer " prefix).
- jobId: A client-generated unique identifier (GUID) for the new job.
- containerName: The storage container name used to host job data.
- blobName: Optional blob name within the container to stage input data.
- inputDataFormat: The format of the input data, e.g. microsoft.qio.v2.
- outputDataFormat: The expected format of the output data.
- quantumItemCount: The number of quantum computing items in the job.
- inputParams: Target-specific input parameters for the job.
For your developer
Arazzo workflow microsoft-quantum:submit-job-poll-results, 4 operations: Storage_GetSasUri → Jobs_Create → Jobs_Get → Jobs_Get. Specs on APIs.io.