Azure Quantum Session Lifecycle
A 5-step recipe with Microsoft Azure Quantum. We can help you get access.
Recipe · 5 steps
Azure Quantum Session Lifecycle
Open a session, submit a job into it, enumerate its jobs, and close it.
- Open a new session with the supplied id and job failure policy.
- Request a container SAS URI to stage input data for the session's job.
- Create a job that references the open session id so it runs as part of the session.
- List the jobs that belong to the session to confirm the job was attached.
- Close the session now that its job has been submitted and enumerated.
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).
- sessionId: A client-generated unique identifier for the session.
- jobFailurePolicy: Policy controlling session behavior when a job fails (e.g. Abort or Continue).
- jobId: A client-generated unique identifier for the job created in the session.
- containerName: The storage container name used to host job data.
- quantumItemCount: The number of quantum computing items in the job.
For your developer
Arazzo workflow microsoft-quantum:session-lifecycle, 5 operations: Sessions_Open → Storage_GetSasUri → Jobs_Create → SessionsJobs_List → Sessions_Close. Specs on APIs.io.