Azure Quantum
Azure Quantum is Microsoft's cloud service for running quantum programs on partner hardware (IonQ, Pasqal, Quantinuum, Rigetti), on simulators, and to estimate what future fault-tolerant machines would need. Programs are written with the free, open-source Quantum Development Kit in Q#, Qiskit, Cirq or OpenQASM.1
Also known as Microsoft Quantum Development Kit (QDK), Q#, Microsoft Quantum resource estimator, Azure Quantum workspace
- Intended for
- Quantum researchers and algorithm developers, Computational chemists and materials scientists, R&D teams assessing quantum readiness, Students and educators learning quantum programming
- Runs on
- Azure cloud (Azure Quantum workspace), Local development with the QDK (no Azure account required)
At a glance
- What is it?
- Azure Quantum is the Azure service for cloud quantum computing. With an Azure account and an Azure Quantum workspace you can submit jobs to quantum computers and simulators from partner providers, and use the Microsoft Quantum resource estimator to see what an algorithm would need on future scaled machines. Development happens in the Microsoft Quantum Development Kit (QDK), a free, open-source kit with a VS Code extension and a Python package that supports Microsoft's Q# language as well as Qiskit, Cirq and OpenQASM. The QDK itself works without an Azure account; running jobs on hardware needs a workspace.1
- What does it do?
- Azure Quantum gives access to trapped-ion systems from IonQ and Quantinuum, neutral-atom processors from Pasqal and superconducting processors from Rigetti, plus provider simulators and emulators. The QDK lets you write, debug and visualize quantum circuits, submit jobs and run hybrid programs where classical and quantum steps interact. The resource estimator computes physical qubit and runtime estimates from an algorithm, a hardware model and an error correction scheme. Microsoft also positions the QDK and Azure HPC for chemistry and materials simulation workflows.12
- Who needs it?
- Research groups and R&D teams that want hands-on experience with real quantum hardware from several vendors through one Azure account and billing relationship; algorithm developers who need to test code across qubit technologies; and organizations that want to estimate when a problem such as breaking a given encryption scheme or simulating a molecule would become feasible, using the resource estimator rather than hardware time.1
- What does it need?
- The QDK extension for VS Code or the QDK Python package (no Azure account needed)
- An Azure account and subscription (for example pay-as-you-go) to run jobs on hardware
- An Azure Quantum workspace with the chosen providers added
- Awareness of each provider's pricing plan and regional availability
- Programming familiarity with Python and basic quantum computing concepts
- What it is not
- Azure Quantum does not give access to Microsoft's own Majorana topological chips: Majorana 2 was announced in 2026 as Microsoft's latest quantum processing unit, but Microsoft presents it as research toward a commercially relevant quantum computer by 2029, not as an Azure Quantum target. Today's hardware is described by Microsoft as an emerging technology with limits on what programs can run. Azure Quantum is not a classical optimization service, and quantum hardware time is priced by each provider, not by Microsoft.2345
Availability and licensing. Azure Quantum is an active Azure service; the QDK is free and open source. Hardware pricing is set by providers. Checked 26 October 2026 on Microsoft's pricing page (which notes providers may change prices): IonQ simulator and Rigetti QVM free; Rigetti USD 0.02 per 10 ms of execution; Pasqal EUR 3,000 per QPU-hour; IonQ Aria-Forte plan USD 25,000 per month; Quantinuum Standard plan USD 125,000 per month. Quantum Circuits is listed as coming soon (private preview pre-registration). Majorana chips are research hardware, not Azure Quantum targets.25
The problem it solves
Quantum computing hardware comes from several vendors with different qubit technologies, programming interfaces and access models, and real machines are still small and noisy. Teams that want to learn, test algorithms or plan for future machines need a way to reach several types of hardware and to reason about future scale without waiting for it.
Azure Quantum puts multiple providers behind one workspace and one development kit, and adds a resource estimator so teams can study fault-tolerant requirements today.
How it works
The workflow has three parts:
- Develop: install the QDK extension in VS Code or the QDK Python package, and write programs in Q#, Qiskit, Cirq or OpenQASM. Q# is hardware-agnostic and describes how a classical control computer interacts with qubits.
- Estimate or simulate: run programs on local or provider simulators, or use the resource estimator with predefined fault-tolerant protocols or your own models to get post-layout physical resource estimates.
- Run on hardware: create an Azure Quantum workspace in the Azure portal, add providers, submit jobs and monitor results. Each provider sets its own pricing plan, and Azure infrastructure costs (storage) apply.1
Diagram as a list
Data & analytics
- Azure StorageStores job inputs and outputs (billed as Azure infrastructure)Connects to Azure Quantum workspace
Developer tools
- Quantum Development Kit (VS Code extension, Python package)Write and debug Q#, Qiskit, Cirq or OpenQASM programs
- Microsoft Quantum resource estimatorEstimates physical resources for fault-tolerant execution
Cloud & hybrid infrastructure
- Azure Quantum workspaceHolds providers, jobs and results in an Azure subscription
- IonQ (trapped ion)Quantum hardware and GPU-accelerated simulator
- Quantinuum (trapped ion)System Model H2 hardware and emulators
- Pasqal (neutral atom)Fresnel QPUs and emulators
- Rigetti (superconducting)Cepheus QPU and Quantum Virtual Machine
Capabilities
Multi-vendor quantum hardware2
IonQ and Quantinuum trapped-ion systems, Pasqal neutral-atom processors and Rigetti superconducting processors in one workspace.
Why it matters: Teams can compare qubit technologies without separate vendor contracts.
Limits: Provider availability varies by region; hardware remains small and error-prone.
Quantum Development Kit6
Free, open-source kit (MIT license) with Q#, the resource estimator and Quantum Katas, available as a VS Code extension and Python package.
Why it matters: Code can be written, debugged and visualized locally before paying for hardware time.
Limits: Running on hardware requires an Azure Quantum workspace.
Language choice1
Supports Q# as well as Qiskit, Cirq and OpenQASM.
Why it matters: Existing code from other ecosystems can be reused.
Limits: Each hardware target supports specific program profiles.
Resource estimator1
Computes physical resource estimates from an application, a hardware architecture model and an error correction code.
Why it matters: Helps plan for future fault-tolerant machines and compare qubit technologies.
Limits: Results are estimates based on the models and assumptions you choose.
Hybrid quantum computing1
Classical and quantum computation work together within programs on supported hardware.
Why it matters: Lets algorithms mix classical processing with quantum steps.
Limits: Each hardware target has its own program limitations, described in Microsoft's target profiles.
Simulators and emulators2
Provider simulators such as the IonQ simulator, Pasqal emulators, Quantinuum H2 emulators and the Rigetti QVM.
Why it matters: Lets teams test at larger scale or with noise models before using hardware.
Limits: Some emulators are billed; simulators cannot show real hardware behavior fully.
Practical use cases
An R&D group needs to know whether a quantum algorithm for a chemistry problem is realistic in the coming years.
- Approach
- Model the algorithm in the QDK and run the resource estimator across hardware assumptions.
- Role of Azure Quantum
- Azure Quantum's resource estimator quantifies qubits and runtime needed.
- Data, infrastructure and skills
- Algorithm implementation in Q# or another supported language.
- Type of benefit
- Planning insight
- Caveats
- Estimates depend on modeling assumptions.
- First step
- Run the estimator on a published sample and then on your own kernel.
Researchers want to compare how one circuit behaves on different qubit technologies.
- Approach
- Submit the same program to trapped-ion, neutral-atom and superconducting targets in one workspace.
- Role of Azure Quantum
- Azure Quantum provides multi-vendor access and job management.
- Data, infrastructure and skills
- Azure subscription, budget for provider pricing plans.
- Type of benefit
- Research flexibility
- Caveats
- Hardware time can be costly and queues apply.
- First step
- Validate the circuit on free simulators before using hardware.
A university course needs hands-on quantum programming without hardware budgets.
- Approach
- Use the free, open-source QDK and Quantum Katas locally.
- Role of Azure Quantum
- The QDK supplies the language, simulator and exercises.
- Data, infrastructure and skills
- VS Code or Python.
- Type of benefit
- Skills development
- Caveats
- Local simulation is limited in qubit count.
- First step
- Install the QDK extension and work through the Katas.
Works with
Optional integration
- Visual Studio Code and Visual Studio 2026The QDK installs as an extension in Visual Studio Code.
Complementary tools
- Azure GPU virtual machinesMicrosoft positions quantum chemistry workflows alongside Azure HPC and AI-accelerated computing.
- Microsoft FoundryMicrosoft's quantum solution page lists Microsoft Foundry among related solutions.
Relationship labels follow Microsoft's documentation. "Alternative approaches" does not mean one is better: each profile says when it fits.
Getting started
Install the QDK
Add the QDK extension to VS Code or install the QDK Python package, and run the first Q# program locally.
Check: A sample program runs on the local simulator and shows results.
Estimate resources
Run the resource estimator on a sample algorithm with a predefined fault-tolerant protocol.
Check: You get physical qubit and runtime estimates for at least two hardware models.
Create a workspace
In the Azure portal, create an Azure Quantum workspace and add the providers you want to use.
Check: The workspace lists the providers and their targets.
Run on a free simulator, then hardware
Submit to a free target such as the IonQ simulator or Rigetti QVM, check costs on the provider pricing page, then submit a small job to hardware.
Check: Jobs complete and costs appear as expected in the workspace.
Official resources
Deciding whether you need it?
Three free tools apply Microsoft's own published guidance to your situation, and say when Azure Quantum or any new technology is not needed.
Sources
Each statement above links to the source it comes from. Labels say who reported it.
- What is Azure Quantum? (opens in a new tab)
- List of quantum computing providers on Azure Quantum (opens in a new tab)
- Microsoft Quantum website (opens in a new tab)
- Microsoft Build 2026 live blog (opens in a new tab)
- Pricing plans for Azure Quantum providers (opens in a new tab)
- microsoft/qdk repository (opens in a new tab)
- Azure quantum computing solution page (opens in a new tab)
Thank you. Your correction was sent.
The editors check it against the sources. If you left an email address, they may reply about it.