{"id":388,"date":"2026-04-13T21:33:22","date_gmt":"2026-04-13T21:33:22","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/azure-quantum-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-compute\/"},"modified":"2026-04-13T21:33:22","modified_gmt":"2026-04-13T21:33:22","slug":"azure-quantum-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-compute","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/azure-quantum-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-compute\/","title":{"rendered":"Azure Quantum Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Compute"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Compute<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<p>Azure Quantum is Microsoft Azure\u2019s managed service for running quantum and quantum-inspired workloads through a unified cloud \u201cworkspace\u201d experience. It lets you develop quantum programs, submit jobs to quantum hardware or simulators from multiple quantum providers, and manage execution results with Azure-native identity and governance.<\/p>\n\n\n\n<p>In simple terms: <strong>Azure Quantum is a control plane in Azure for quantum computing<\/strong>. You create an Azure Quantum workspace, connect one or more quantum providers\/offerings, and then submit jobs (circuits\/programs\/optimization problems) to selected targets (simulators or real quantum processing units).<\/p>\n\n\n\n<p>Technically, Azure Quantum provides:\n&#8211; An Azure Resource Manager (ARM) resource called an <strong>Azure Quantum workspace<\/strong>\n&#8211; A <strong>job management layer<\/strong> (submission, status, output retrieval)\n&#8211; Integrations with <strong>identity (Microsoft Entra ID\/Azure AD), RBAC, Azure Policy, Azure Monitor\/Activity Logs<\/strong>\n&#8211; SDKs and tooling to submit quantum or optimization workloads via <strong>Python, Q#, and provider-specific formats<\/strong><\/p>\n\n\n\n<p>The problem it solves is practical access and operations: quantum ecosystems are fragmented (multiple hardware vendors, multiple SDKs, different job formats, different account models). Azure Quantum provides a consistent Azure-native way to <strong>provision<\/strong>, <strong>secure<\/strong>, <strong>govern<\/strong>, and <strong>operate<\/strong> quantum and optimization workloads in a way that fits enterprise cloud patterns.<\/p>\n\n\n\n<blockquote>\n<p>Service status note: <strong>Azure Quantum<\/strong> is the current, official service name. Microsoft also offers <strong>Azure Quantum Elements<\/strong> (focused on chemistry\/materials workflows). This tutorial focuses on <strong>Azure Quantum (Compute)<\/strong>. If you plan to use Elements features, verify the latest product boundaries in official docs.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Azure Quantum?<\/h2>\n\n\n\n<p>Azure Quantum is a managed Azure service that provides a <strong>workspace<\/strong> to run and manage quantum computing jobs and quantum-inspired optimization jobs against supported targets from Microsoft and partner providers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose (what it\u2019s for)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Provide a <strong>cloud-hosted entry point<\/strong> for quantum computing and optimization workloads<\/li>\n<li>Offer <strong>job orchestration<\/strong> (submission, tracking, output retrieval) across multiple quantum backends<\/li>\n<li>Integrate quantum workflows with <strong>Azure security, governance, and operational tooling<\/strong><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities (what you can do)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create an <strong>Azure Quantum workspace<\/strong> in your Azure subscription<\/li>\n<li>Discover and use <strong>targets<\/strong> (simulators, QPUs, optimization solvers) depending on region and provider offerings<\/li>\n<li>Submit <strong>jobs<\/strong> and manage job lifecycle (queued\/running\/completed\/failed)<\/li>\n<li>Use development tooling (commonly via <strong>Python SDK<\/strong>, <strong>Q# \/ Azure Quantum Development Kit<\/strong>, and provider ecosystems)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Azure Quantum Workspace<\/strong>: The top-level Azure resource you deploy into a resource group.<\/li>\n<li><strong>Providers &amp; Offerings<\/strong>: Provider integrations made available in a workspace region (availability varies).<\/li>\n<li><strong>Targets<\/strong>: Specific execution backends (e.g., a simulator, a QPU, an optimization solver).<\/li>\n<li><strong>Jobs<\/strong>: The unit of execution submitted to a target with input data, producing output data.<\/li>\n<li><strong>Associated storage<\/strong>: Azure Quantum workspaces use Azure Storage for job artifacts (exact implementation details can evolve; verify in official docs).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Service type<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed Azure service<\/strong> (control plane + job management) that connects to quantum backends.<\/li>\n<li>Not a general-purpose VM\/containers compute service; rather, it\u2019s a specialized compute orchestration service for quantum and optimization workloads.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scope and tenancy<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Subscription-scoped Azure resource<\/strong>: You create a workspace inside a subscription and resource group.<\/li>\n<li><strong>Region-bound workspace<\/strong>: A workspace is deployed into an Azure region, and available providers\/targets depend on that region and your enabled offerings.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How it fits into the Azure ecosystem<\/h3>\n\n\n\n<p>Azure Quantum is typically used alongside:\n&#8211; <strong>Microsoft Entra ID (Azure AD)<\/strong> for identity and authentication\n&#8211; <strong>Azure RBAC<\/strong> for authorization\n&#8211; <strong>Azure Storage<\/strong> for job inputs\/outputs (workspace-linked)\n&#8211; <strong>Azure Monitor + Activity Log<\/strong> for operational visibility\n&#8211; <strong>Azure Key Vault<\/strong> (recommended) for secrets used by related apps and CI\/CD pipelines\n&#8211; <strong>DevOps tooling<\/strong> such as GitHub Actions or Azure DevOps pipelines for repeatable job submission workflows (where appropriate)<\/p>\n\n\n\n<p>Official documentation entry point: https:\/\/learn.microsoft.com\/azure\/quantum\/<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Azure Quantum?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Vendor flexibility<\/strong>: You can evaluate and use multiple quantum hardware providers without building separate provisioning and governance models for each one.<\/li>\n<li><strong>Faster experimentation<\/strong>: Centralizes access in Azure where teams already run data, apps, and security tooling.<\/li>\n<li><strong>Enterprise alignment<\/strong>: Integrates with Azure identity, billing, and governance practices that procurement and security teams already understand.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Unified job model<\/strong>: A consistent concept of <em>workspace \u2192 target \u2192 job \u2192 result<\/em>.<\/li>\n<li><strong>Tooling integration<\/strong>: Supports common quantum development workflows (Q#, Python, and provider ecosystems).<\/li>\n<li><strong>Hybrid readiness<\/strong>: Quantum workloads often pair with classical preprocessing\/postprocessing (data preparation, optimization, simulation). Azure provides the broader compute environment for the classical parts.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Central resource management<\/strong>: Workspaces can be deployed and managed with ARM, Bicep, Terraform (verify provider support\/version), and Azure Portal.<\/li>\n<li><strong>Auditing<\/strong>: Azure Activity Logs capture control-plane operations like workspace updates and role changes.<\/li>\n<li><strong>Repeatability<\/strong>: CI\/CD pipelines can submit jobs, collect results, and publish artifacts.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Microsoft Entra ID authentication<\/strong> and <strong>Azure RBAC<\/strong> authorization.<\/li>\n<li>Azure-native governance tools: <strong>Azure Policy<\/strong>, <strong>resource locks<\/strong>, <strong>tags<\/strong>, <strong>blueprints<\/strong> (as applicable).<\/li>\n<li>Data residency and compliance may be easier to reason about when the control plane is in your Azure tenant (but note that job execution may involve partner providers; verify provider data handling terms).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Workload scaling<\/strong> is primarily determined by the target (hardware\/simulator\/solver). Azure Quantum helps orchestrate submissions and manage job concurrency within service\/provider limits.<\/li>\n<li>Azure supports the classical compute side: you can scale preprocessing\/postprocessing with Azure Batch, AKS, Functions, or HPC patterns.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose Azure Quantum<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You want <strong>Azure-native governance<\/strong> and centralized access to quantum compute targets.<\/li>\n<li>You need to <strong>compare providers<\/strong> or keep a multi-provider strategy.<\/li>\n<li>You need <strong>job lifecycle management<\/strong> and want to integrate quantum experiments into standard cloud operations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose Azure Quantum<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You only need a <strong>local simulator<\/strong> for learning and do not need cloud orchestration (use local QDK\/Qiskit\/Cirq tooling).<\/li>\n<li>Your organization cannot accept third-party provider execution for compliance reasons (unless a provider and offering meets your requirements).<\/li>\n<li>You require low-latency interactive execution; quantum job models are generally <strong>batch-oriented<\/strong> with queuing.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Azure Quantum used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Finance (portfolio optimization research, risk, scenario generation)<\/li>\n<li>Manufacturing and logistics (routing, scheduling, supply chain)<\/li>\n<li>Pharma and materials (molecular simulation research; often overlaps with Azure Quantum Elements)<\/li>\n<li>Energy (grid optimization, exploration optimization)<\/li>\n<li>Telecommunications (network optimization)<\/li>\n<li>Research and higher education (quantum algorithms, benchmarking)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Applied research teams (quantum algorithms, optimization research)<\/li>\n<li>Data science and ML teams exploring combinatorial optimization<\/li>\n<li>Platform\/Cloud engineering teams enabling secure workspaces and governance<\/li>\n<li>DevOps teams building repeatable experiment pipelines<\/li>\n<li>Security\/compliance teams reviewing provider execution models<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Quantum circuit execution (simulators and QPUs)<\/li>\n<li>Resource estimation and feasibility analysis (where supported)<\/li>\n<li>Quantum-inspired optimization (classical solvers influenced by quantum approaches)<\/li>\n<li>Hybrid workflows (classical compute + quantum\/optimization job submissions + classical analysis)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures and deployment contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dev\/test<\/strong>: Most teams start with simulators, small circuits, and small optimization problems.<\/li>\n<li><strong>Pilot\/POC<\/strong>: Limited real-hardware submissions for benchmarking or proofs of feasibility.<\/li>\n<li><strong>Production<\/strong>: Still emerging; production often means stable pipelines for <em>decision support<\/em> or <em>research operations<\/em>, with strong governance and cost controls.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic use cases where Azure Quantum fits the operational and architectural needs. Availability depends on region and enabled providers\/targets\u2014verify in official docs and your workspace target list.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Provider benchmarking and evaluation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: You need to evaluate multiple quantum providers without building separate integrations.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Central workspace model with provider offerings and target discovery.<\/li>\n<li><strong>Example<\/strong>: A research group benchmarks the same circuit family on simulators and multiple QPUs (when available) and stores results in Azure Storage for analysis.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Quantum algorithm prototyping (simulator-first)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: You want to develop quantum programs without immediate access to hardware.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Simulator targets and development toolchain integration.<\/li>\n<li><strong>Example<\/strong>: A developer prototypes Grover-style search variants, validating circuit correctness in simulators before any QPU run.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Combinatorial optimization experimentation (quantum-inspired)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: You need to solve scheduling\/routing problems and explore quantum-inspired methods.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Supports optimization workflows (where offerings exist) and integrates with Azure for data pipelines.<\/li>\n<li><strong>Example<\/strong>: A logistics team formulates a vehicle routing problem as QUBO and tests solver strategies, tracking objective quality vs runtime.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Hybrid workflows with Azure compute<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Quantum jobs need classical preprocessing\/postprocessing at scale.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Azure provides scalable classical compute; Azure Quantum orchestrates job submissions.<\/li>\n<li><strong>Example<\/strong>: An energy company uses AKS to generate candidate instances, submits them as jobs, then aggregates results in a data lake.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Reproducible research pipelines (CI\/CD)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Quantum experiments are hard to reproduce across developers and time.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Workspace resources + job artifacts + Azure DevOps\/GitHub integration.<\/li>\n<li><strong>Example<\/strong>: A GitHub Actions workflow runs nightly experiments, stores results as build artifacts, and posts metrics to a dashboard.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Access control and governance for quantum projects<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: You need strict permissions and auditability for who can run which targets.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Entra ID + RBAC + Azure governance tooling.<\/li>\n<li><strong>Example<\/strong>: A regulated enterprise creates separate workspaces for R&amp;D vs production experiments with tighter RBAC on the production workspace.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Education labs with safe guardrails<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Students need hands-on exposure without uncontrolled spending.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Workspace-based access, target-level choices, and Azure budgets.<\/li>\n<li><strong>Example<\/strong>: A university class uses only simulator targets and enforces budgets\/quotas via Azure cost management.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Feasibility analysis via resource estimation (when supported)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: You need to understand how many logical\/physical resources a quantum algorithm might require.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: QDK tooling and estimation workflows (capability and availability can evolve\u2014verify).<\/li>\n<li><strong>Example<\/strong>: A research team estimates resources for a chemistry simulation algorithm and decides it is not yet hardware-feasible.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Operational dashboards for quantum job throughput<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: You need visibility into job volume, failure rates, and usage trends.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Azure-native logs\/metrics patterns (availability varies; at minimum Activity Logs exist).<\/li>\n<li><strong>Example<\/strong>: A platform team tracks job submissions per workspace and implements alerts for unusual spikes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Multi-environment separation (dev\/test\/prod)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: You need strong isolation between experimental work and stable pipelines.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Separate Azure Quantum workspaces per environment and controlled access.<\/li>\n<li><strong>Example<\/strong>: A fintech uses dev workspace for experiments and a prod workspace for scheduled optimization runs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Data residency-aware experimentation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: You need to run within specific Azure regions for governance reasons.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Region-specific workspaces; provider availability is region-dependent.<\/li>\n<li><strong>Example<\/strong>: An EU-based team deploys the workspace in an EU region that supports the needed offerings, aligning with internal policies.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Centralized artifact storage and traceability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Results are scattered across notebooks and laptops.<\/li>\n<li><strong>Why Azure Quantum fits<\/strong>: Workspace job artifacts and Azure storage integration.<\/li>\n<li><strong>Example<\/strong>: A research org stores input parameters, job IDs, outputs, and metadata for traceability and later analysis.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<p>Feature availability can vary by region and provider; always validate in the official documentation and your workspace\u2019s available targets.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6.1 Azure Quantum workspace (ARM resource)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Provides a managed workspace resource in your subscription to organize providers\/targets and jobs.<\/li>\n<li><strong>Why it matters<\/strong>: Creates a consistent operational boundary for access control, cost management, and governance.<\/li>\n<li><strong>Practical benefit<\/strong>: You can manage quantum resources like other Azure resources (tags, RBAC, policies).<\/li>\n<li><strong>Caveats<\/strong>: Workspace availability is region-dependent; provider offerings differ by region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.2 Provider\/target discovery and selection<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Exposes a list of targets (simulators\/QPUs\/solvers) available to your workspace.<\/li>\n<li><strong>Why it matters<\/strong>: Quantum backends are heterogeneous; selecting targets is a core operational step.<\/li>\n<li><strong>Practical benefit<\/strong>: Enables multi-provider strategies and gradual migration between backends.<\/li>\n<li><strong>Caveats<\/strong>: Some providers require separate enrollment\/terms; targets can be added\/removed over time.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.3 Job submission and lifecycle management<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Submit jobs, track status, retrieve results, and manage job metadata.<\/li>\n<li><strong>Why it matters<\/strong>: Quantum compute is typically queued and batch-executed; job tracking is essential.<\/li>\n<li><strong>Practical benefit<\/strong>: Standardizes operations (submit \u2192 poll \u2192 fetch results \u2192 archive).<\/li>\n<li><strong>Caveats<\/strong>: Job turnaround times vary widely; queuing is common.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.4 SDK support (commonly Python; plus QDK tooling)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Allows programmatic job submission and result handling.<\/li>\n<li><strong>Why it matters<\/strong>: Real workflows need automation, not just portal clicks.<\/li>\n<li><strong>Practical benefit<\/strong>: Integrates with notebooks, pipelines, experiment tracking, and MLOps patterns.<\/li>\n<li><strong>Caveats<\/strong>: SDK APIs and supported input formats evolve; pin versions in production and review release notes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.5 Identity and access integration (Entra ID + Azure RBAC)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Uses Azure\u2019s identity platform for authentication and RBAC roles for authorization.<\/li>\n<li><strong>Why it matters<\/strong>: Enterprises need centralized IAM, least privilege, and auditability.<\/li>\n<li><strong>Practical benefit<\/strong>: Access can be granted at subscription\/resource group\/workspace scope; supports managed identities for automation.<\/li>\n<li><strong>Caveats<\/strong>: Provider-side permissions\/limits may still apply depending on offering.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.6 Azure governance integration (tags, policy, locks)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Enables common Azure governance practices.<\/li>\n<li><strong>Why it matters<\/strong>: Quantum workspaces should follow the same guardrails as any other compute resource.<\/li>\n<li><strong>Practical benefit<\/strong>: Enforce naming\/tagging standards; prevent accidental deletion with locks.<\/li>\n<li><strong>Caveats<\/strong>: Specific policy definitions for Azure Quantum may be limited\u2014verify built-in policies and consider custom ones.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.7 Job artifact storage (workspace-linked)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Stores job inputs\/outputs and metadata via Azure-managed mechanisms and associated storage.<\/li>\n<li><strong>Why it matters<\/strong>: You need durable access to results for analysis and reproducibility.<\/li>\n<li><strong>Practical benefit<\/strong>: Simplifies experiment traceability.<\/li>\n<li><strong>Caveats<\/strong>: Understand data retention, encryption, and access boundaries; verify in official docs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6.8 Integration with classical Azure services (hybrid compute)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Enables pairing quantum\/optimization jobs with Azure compute and data services.<\/li>\n<li><strong>Why it matters<\/strong>: Most real solutions are hybrid.<\/li>\n<li><strong>Practical benefit<\/strong>: Use Functions\/Batch\/AKS for orchestration and scaling of classical components.<\/li>\n<li><strong>Caveats<\/strong>: You own the architecture; Azure Quantum is not a full pipeline orchestration tool by itself.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-level service architecture<\/h3>\n\n\n\n<p>At a high level, Azure Quantum sits between your client environment (developer machine, notebook, CI pipeline) and quantum compute targets (simulators, QPUs, or optimization solvers). You authenticate with Microsoft Entra ID, submit a job to the workspace specifying a target, and then Azure Quantum coordinates job handling and routes execution to the selected backend.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow (typical)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Authenticate<\/strong>: Client authenticates to Azure using Entra ID (interactive <code>az login<\/code>, service principal, or managed identity).<\/li>\n<li><strong>Discover targets<\/strong>: Client queries the workspace for available targets.<\/li>\n<li><strong>Submit job<\/strong>: Client submits job payload + metadata and selects a target.<\/li>\n<li><strong>Queue\/execute<\/strong>: Target queues and executes based on provider capacity and policies.<\/li>\n<li><strong>Retrieve results<\/strong>: Client polls job status and downloads results\/output.<\/li>\n<li><strong>Store\/analyze<\/strong>: Results are stored and analyzed in your Azure environment (Storage, Synapse, Databricks, Fabric, etc.).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related services<\/h3>\n\n\n\n<p>Common integrations include:\n&#8211; <strong>Azure Storage<\/strong>: job artifacts and research datasets\n&#8211; <strong>Azure Key Vault<\/strong>: secrets for CI\/CD (service principals, tokens for related systems)\n&#8211; <strong>Azure Monitor \/ Log Analytics<\/strong>: operational monitoring (verify which resource logs are available for Azure Quantum)\n&#8211; <strong>Azure Cost Management<\/strong>: budgets and alerts for spend control\n&#8211; <strong>GitHub \/ Azure DevOps<\/strong>: pipeline automation for job submission and regression tests<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services (typical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Microsoft Entra ID (identity)<\/li>\n<li>Azure Resource Manager (resource provisioning)<\/li>\n<li>Storage (workspace-associated storage and\/or your own storage)<\/li>\n<li>Provider backend services (partner-managed or Microsoft-managed depending on target)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Authentication<\/strong>: Entra ID tokens for Azure API access.<\/li>\n<li><strong>Authorization<\/strong>: Azure RBAC roles assigned at workspace (or RG\/subscription) scope.<\/li>\n<li><strong>Provider authorization<\/strong>: Depending on offering, additional provider-side constraints may exist; review provider terms and offering configuration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Azure Quantum is typically accessed via Azure public endpoints over HTTPS.<\/li>\n<li>For private networking (Private Link\/private endpoints), <strong>verify in official docs<\/strong> whether Azure Quantum supports it in your region and what limitations apply.<\/li>\n<li>If private endpoint is not supported, mitigate exposure using least privilege, conditional access, and strict CI\/CD identity controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Azure Activity Log<\/strong>: captures control-plane actions (create\/update\/delete workspace, role assignments).<\/li>\n<li><strong>Diagnostic settings\/resource logs<\/strong>: availability can change; <strong>verify in official docs<\/strong> if Azure Quantum emits resource logs\/metrics and what categories are supported.<\/li>\n<li><strong>Tagging<\/strong>: use tags for environment, owner, cost center, and data classification.<\/li>\n<li><strong>Budgets<\/strong>: enforce budgets at subscription or resource group scope to avoid unexpected costs, especially if QPU targets are enabled.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram (conceptual)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  Dev[Developer \/ Notebook \/ CI] --&gt;|Entra ID auth| AzureAPI[Azure APIs]\n  AzureAPI --&gt; AQW[Azure Quantum Workspace]\n  AQW --&gt;|Submit job| Target[Quantum Target\\n(QPU\/Simulator\/Solver)]\n  Target --&gt;|Results| AQW\n  AQW --&gt; Storage[Workspace-linked Storage]\n  Dev --&gt;|Fetch results| AQW\n  Dev --&gt;|Analyze| Analytics[Azure compute + analytics]\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (enterprise pattern)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph Identity\n    Entra[Microsoft Entra ID]\n    CA[Conditional Access\\n(MFA, device, location)]\n  end\n\n  subgraph DevOps\n    Git[GitHub \/ Azure DevOps]\n    Pipeline[CI\/CD Pipeline\\n(Managed Identity or SP)]\n    Artifacts[Artifacts \/ Model Registry\\n(optional)]\n  end\n\n  subgraph AzureSubscription[Azure Subscription]\n    subgraph RG[Resource Group: quantum-prod-rg]\n      AQW[Azure Quantum Workspace]\n      SA[Azure Storage Account\\n(job artifacts, datasets)]\n      KV[Azure Key Vault\\n(secrets, keys)]\n      LA[Log Analytics Workspace]\n      Budgets[Cost Management\\nBudgets &amp; Alerts]\n    end\n\n    subgraph Compute[Classical Compute]\n      AKS[AKS \/ Batch \/ Functions\\npre\/post-processing]\n      Data[Data Lake \/ Fabric \/ Databricks\\n(optional)]\n    end\n  end\n\n  subgraph Providers[Quantum Providers]\n    QPUs[QPU \/ Provider Simulators\\n(region\/offer dependent)]\n  end\n\n  DevUser[Developer Workstation] --&gt;|MFA| CA --&gt; Entra\n  Pipeline --&gt;|OIDC\/Secrets| Entra\n\n  Pipeline --&gt;|Submit jobs| AQW\n  DevUser --&gt;|Submit jobs| AQW\n\n  AQW --&gt; SA\n  AQW --&gt;|Route jobs| QPUs\n  QPUs --&gt;|Results| AQW\n\n  AQW --&gt;|Diagnostics (verify)| LA\n  Budgets --&gt;|Alerts| Ops[Ops team notifications]\n\n  AKS --&gt;|Prepare inputs| SA\n  AKS --&gt;|Read results| SA\n  AKS --&gt;|Postprocess| Data\n  Git --&gt; Pipeline\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Account\/subscription requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An active <strong>Azure subscription<\/strong> with billing enabled.<\/li>\n<li>Ability to create resources in a resource group (or an existing resource group).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<p>You typically need:\n&#8211; <strong>Contributor<\/strong> (or equivalent) on the resource group to create the workspace and related resources.\n&#8211; <strong>Owner<\/strong> or <strong>User Access Administrator<\/strong> may be required to assign RBAC roles to other identities.\n&#8211; Least privilege recommendation:\n  &#8211; Platform team provisions the workspace.\n  &#8211; Developers get a workspace-level role that permits job submission but not RBAC changes (exact built-in roles vary; verify current Azure Quantum RBAC roles in docs).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Quantum hardware jobs can be costly; ensure budgets\/alerts are in place.<\/li>\n<li>Some provider offerings may require accepting additional terms or enabling offerings.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tools needed (recommended)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Azure CLI<\/strong>: https:\/\/learn.microsoft.com\/cli\/azure\/install-azure-cli<\/li>\n<li><strong>Azure CLI quantum extension<\/strong> (if using CLI-based workflows)<\/li>\n<li><strong>.NET SDK<\/strong> (for Q# development if using QDK with .NET): https:\/\/dotnet.microsoft.com\/download<\/li>\n<li><strong>Python 3.x<\/strong> (if using Python SDK workflows): https:\/\/www.python.org\/downloads\/<\/li>\n<li><strong>VS Code<\/strong> (optional but common): https:\/\/code.visualstudio.com\/<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Azure Quantum workspace locations and offerings are <strong>region-dependent<\/strong>.<\/li>\n<li>Before starting, check the official region\/availability documentation: https:\/\/learn.microsoft.com\/azure\/quantum\/ (navigate to \u201cAzure Quantum workspaces\u201d and \u201cregions\u201d)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas\/limits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Job concurrency, maximum job size, and target-specific limits vary by provider and offering.<\/li>\n<li>Always review:<\/li>\n<li>Azure Quantum service limits (if documented)<\/li>\n<li>Provider documentation for target limits<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Often: an <strong>Azure Storage account<\/strong> associated with the workspace (creation flow may create or require one).<\/li>\n<li>Optional but recommended: <strong>Azure Key Vault<\/strong>, <strong>Log Analytics<\/strong>, <strong>budget alerts<\/strong>.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<p>Azure Quantum pricing is not a single flat rate. It is typically a combination of:\n&#8211; The <strong>target\/provider pricing model<\/strong> (QPU time, shots, job runtime, or solver usage)\n&#8211; Any <strong>Azure-side supporting costs<\/strong> (storage, monitoring, network egress, CI runners, classical compute)<\/p>\n\n\n\n<p>Official pricing page (start here):<br\/>\nhttps:\/\/azure.microsoft.com\/pricing\/details\/azure-quantum\/ (verify current URL if redirected)<\/p>\n\n\n\n<p>Pricing calculator (for broader Azure costs):<br\/>\nhttps:\/\/azure.microsoft.com\/pricing\/calculator\/<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing dimensions (common patterns)<\/h3>\n\n\n\n<p>Depending on provider\/target, you may see pricing based on:\n&#8211; <strong>Shots<\/strong>: number of repeated circuit executions\n&#8211; <strong>QPU time<\/strong>: time reserved\/executed on the hardware\n&#8211; <strong>Job runtime<\/strong> or <strong>solver time<\/strong>\n&#8211; <strong>Simulator usage<\/strong> (may be free or paid depending on provider\/offer\u2014verify)\n&#8211; <strong>Resource estimation<\/strong> or specialized tooling (availability\/pricing can change\u2014verify)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier \/ credits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Some quantum ecosystems provide free credits or limited free simulator access occasionally, but <strong>do not assume<\/strong> this is available.<\/li>\n<li>Verify current promotions\/credits in the official pricing page and in your Azure portal offering details.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Main cost drivers<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Using real QPUs<\/strong> (usually the biggest driver)<\/li>\n<li>High <strong>shot counts<\/strong> or repeated parameter sweeps<\/li>\n<li>Large numbers of jobs (automation can generate many jobs quickly)<\/li>\n<li>Data retention and storage growth (job artifacts + experiment data)<\/li>\n<li>Classical compute for preprocessing\/postprocessing (AKS\/Batch\/VMs)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden or indirect costs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Azure Storage<\/strong> transactions and capacity (especially if storing many job artifacts)<\/li>\n<li><strong>Log Analytics ingestion<\/strong> if you enable verbose diagnostics (verify availability)<\/li>\n<li><strong>Network egress<\/strong> if exporting large results datasets outside Azure<\/li>\n<li>Developer tooling compute (hosted runners, notebooks)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data transfer within Azure region is typically cheaper than cross-region or internet egress, but specifics vary.<\/li>\n<li>If provider execution or result retrieval crosses boundaries, review provider documentation and Azure bandwidth pricing:\n  https:\/\/azure.microsoft.com\/pricing\/details\/bandwidth\/<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start with simulators and small problem sizes.<\/li>\n<li>Use <strong>budgets and alerts<\/strong> in Azure Cost Management.<\/li>\n<li>Implement guardrails:<\/li>\n<li>Limit who can run expensive targets (RBAC + process).<\/li>\n<li>Separate dev\/test vs controlled environments.<\/li>\n<li>Reduce shots and job counts by using smarter experiment design:<\/li>\n<li>Parameter sweeps with early stopping<\/li>\n<li>Sampling strategies<\/li>\n<li>Batch submissions when appropriate (provider-dependent)<\/li>\n<li>Store only what you need:<\/li>\n<li>Define retention policies for job artifacts and derived datasets.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (conceptual)<\/h3>\n\n\n\n<p>A low-cost learning setup may include:\n&#8211; 1 Azure Quantum workspace\n&#8211; Minimal job artifacts stored (small storage account footprint)\n&#8211; Simulator-only experimentation\n&#8211; A few hours of local dev and occasional target listing<\/p>\n\n\n\n<p>Your direct Azure Quantum target charges could be near-zero <strong>if you do not run paid targets<\/strong>, but you should still account for:\n&#8211; Storage account monthly cost (capacity + transactions)\n&#8211; Any classical compute you spin up (not required for the basic lab)<\/p>\n\n\n\n<p>Because exact prices vary by region and usage, <strong>use the pricing calculator<\/strong> and the Azure Quantum pricing page for real numbers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations<\/h3>\n\n\n\n<p>For a production-like research operations pipeline:\n&#8211; Multiple workspaces (dev\/test\/prod)\n&#8211; CI\/CD automation that runs daily job batches\n&#8211; Data lake + analytics compute\n&#8211; Some QPU usage for benchmarking<\/p>\n\n\n\n<p>Cost planning should include:\n&#8211; Provider QPU\/solver charges (primary)\n&#8211; Storage growth and retention\n&#8211; Monitoring\/logging ingestion\n&#8211; Team-level chargeback via tags and budgets<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab is designed to be <strong>beginner-friendly, safe, and low-cost<\/strong>. It focuses on provisioning an Azure Quantum workspace, setting up tooling, validating connectivity, and running a small quantum program locally (simulator-first). Submitting to a paid cloud target is included as an <strong>optional<\/strong> step because costs and provider enrollment vary.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create an <strong>Azure Quantum workspace<\/strong> in Azure.<\/li>\n<li>Configure your machine with <strong>Azure CLI + quantum extension<\/strong>.<\/li>\n<li>Verify you can <strong>discover targets<\/strong> in your workspace.<\/li>\n<li>Create and run a <strong>Q# program locally<\/strong> (simulator-first) so you have a working development loop.<\/li>\n<li>(Optional) Prepare to submit jobs to an Azure Quantum target if you have an enabled offering.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Choose a supported region and create a resource group.\n2. Create an Azure Quantum workspace and link storage (method depends on portal\/CLI flow).\n3. Install and configure the Azure CLI quantum extension.\n4. Verify access by listing targets.\n5. Create a minimal Q# project and run it locally.\n6. Validate and clean up.<\/p>\n\n\n\n<blockquote>\n<p>Expected cost: typically low for workspace + storage, but <strong>verify<\/strong> your region and whether any selected targets incur charges. Do <strong>not<\/strong> run QPU targets unless you understand the pricing.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Create a resource group<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p>Install Azure CLI if needed:<br\/>\n   https:\/\/learn.microsoft.com\/cli\/azure\/install-azure-cli<\/p>\n<\/li>\n<li>\n<p>Sign in:<\/p>\n<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">az login\naz account show\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"3\">\n<li>Set your subscription (if you have multiple):<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">az account set --subscription \"&lt;SUBSCRIPTION_ID_OR_NAME&gt;\"\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"4\">\n<li>Choose a region supported by Azure Quantum (verify in docs). Then create a resource group:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">export LOCATION=\"&lt;YOUR_SUPPORTED_REGION&gt;\"\nexport RG=\"rg-azure-quantum-lab\"\n\naz group create -n \"$RG\" -l \"$LOCATION\"\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>: The command returns JSON showing the resource group was created.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Create an Azure Quantum workspace<\/h3>\n\n\n\n<p>You can create the workspace in <strong>Azure Portal<\/strong> (most straightforward) or via <strong>CLI<\/strong>. Portal steps are less sensitive to CLI parameter changes.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Option A (recommended): Azure Portal<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to the Azure Portal: https:\/\/portal.azure.com\/<\/li>\n<li>Search for <strong>Azure Quantum<\/strong> and choose <strong>Azure Quantum<\/strong> (or \u201cAzure Quantum workspace\u201d if that is the resource type label).<\/li>\n<li>Select <strong>Create<\/strong>.<\/li>\n<li>Configure:\n   &#8211; Subscription\n   &#8211; Resource group: <code>rg-azure-quantum-lab<\/code>\n   &#8211; Workspace name: choose a globally unique name within Azure constraints\n   &#8211; Region: choose a supported region\n   &#8211; Storage: either create new or select an existing supported storage account (the portal may guide this)<\/li>\n<li>Review + Create.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>: A deployed Azure Quantum workspace resource in your resource group.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Option B: Azure CLI (verify parameters in official docs)<\/h4>\n\n\n\n<p>Azure CLI support is provided via a quantum extension. Because CLI flags can change, treat this as a pattern and verify the latest <code>az quantum workspace create -h<\/code> output.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create a storage account (required by many workspace setups):<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">export SA=\"saquantum$(openssl rand -hex 3)\"\naz storage account create \\\n  -n \"$SA\" \\\n  -g \"$RG\" \\\n  -l \"$LOCATION\" \\\n  --sku Standard_LRS\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"2\">\n<li>Get the storage account resource ID:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">export SA_ID=$(az storage account show -n \"$SA\" -g \"$RG\" --query id -o tsv)\necho \"$SA_ID\"\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"3\">\n<li>Install the quantum extension (see Step 3), then create the workspace (syntax may vary; verify):<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">export WS=\"aqw-quantum-lab-01\"\n\n# Verify CLI help first:\naz quantum workspace create -h\n\n# Then create (example pattern; verify required flags):\naz quantum workspace create \\\n  -g \"$RG\" \\\n  -n \"$WS\" \\\n  -l \"$LOCATION\" \\\n  --storage-account \"$SA_ID\"\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>: Workspace appears in <code>az resource list -g rg-azure-quantum-lab<\/code>.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Install the Azure CLI quantum extension and set the workspace context<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Install\/upgrade the quantum extension:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">az extension add -n quantum --upgrade\naz extension show -n quantum\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"2\">\n<li>Set defaults so commands know which workspace to use:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\"># Verify the available command syntax:\naz quantum workspace set -h\n\n# Common pattern (verify flags in your CLI help output):\naz quantum workspace set \\\n  -g \"$RG\" \\\n  -n \"$WS\" \\\n  -l \"$LOCATION\"\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>: The CLI confirms the active workspace (or subsequent commands work without specifying workspace each time).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: List available targets in your Azure Quantum workspace<\/h3>\n\n\n\n<p>Run:<\/p>\n\n\n\n<pre><code class=\"language-bash\">az quantum target list -o table\n<\/code><\/pre>\n\n\n\n<p>If <code>-o table<\/code> is not supported in your version, use JSON:<\/p>\n\n\n\n<pre><code class=\"language-bash\">az quantum target list -o json\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>:\n&#8211; A list of targets appears (simulators, QPUs, solvers), depending on your region and enabled offerings.\n&#8211; If the list is empty or errors, check your region and workspace offering configuration in the portal and verify provider enrollment requirements.<\/p>\n\n\n\n<blockquote>\n<p>Important: Do not assume all targets are available by default. Some require enabling an offering or accepting provider terms.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Create and run a minimal Q# program locally (simulator-first)<\/h3>\n\n\n\n<p>This step validates your development toolchain without requiring paid targets.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p>Install the .NET SDK (if not installed):<br\/>\n   https:\/\/dotnet.microsoft.com\/download<\/p>\n<\/li>\n<li>\n<p>Create a Q# project.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p>Q# project templates and commands can evolve. The Azure Quantum Development Kit documentation is the source of truth. Start here:<br\/>\nhttps:\/\/learn.microsoft.com\/azure\/quantum\/<\/p>\n\n\n\n<p>Use the official instructions to create a Q# project. A common workflow is:<\/p>\n\n\n\n<pre><code class=\"language-bash\">mkdir qsharp-lab\ncd qsharp-lab\n\n# Verify the correct template command in official docs for your QDK version\ndotnet new -l | grep -i quantum || true\n<\/code><\/pre>\n\n\n\n<p>If templates are not installed, the docs typically instruct you how to install them.<\/p>\n\n\n\n<ol class=\"wp-block-list\" start=\"3\">\n<li>Once the project is created, run it:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">dotnet run\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>:\n&#8211; You see console output from your program.\n&#8211; If the program includes a measurement or random outcome, you may see variable outputs, which is normal.<\/p>\n\n\n\n<blockquote>\n<p>If you prefer Python-based development, Microsoft provides Python tooling for Q# and Azure Quantum workflows. Verify current packages and versions in official docs before installing.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6 (Optional): Prepare for cloud job submission<\/h3>\n\n\n\n<p>Submitting jobs to Azure Quantum targets depends on:\n&#8211; The <strong>target\u2019s expected input format<\/strong>\n&#8211; Whether the <strong>provider offering is enabled<\/strong>\n&#8211; Pricing and quotas<\/p>\n\n\n\n<p>A safe preparation step is to document your target ID(s) and confirm you can access them:<\/p>\n\n\n\n<pre><code class=\"language-bash\">az quantum target list -o jsonc\n<\/code><\/pre>\n\n\n\n<p>Pick a <strong>simulator<\/strong> target (if available) and review its documentation in the provider docs.<\/p>\n\n\n\n<p><strong>Expected outcome<\/strong>:\n&#8211; You identify at least one simulator target ID you are authorized to use.<\/p>\n\n\n\n<blockquote>\n<p>Optional execution note: The exact submission command and input format differ by target\/provider. Use the official Azure Quantum \u201csubmit a job\u201d documentation and provider-specific target docs to avoid malformed jobs and unexpected charges.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>Use the checklist below:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Workspace exists:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">az resource list -g \"$RG\" --query \"[?contains(type, 'Microsoft.Quantum')]\" -o table\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"2\">\n<li>Quantum extension installed:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">az extension show -n quantum -o table\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"3\">\n<li>Targets list successfully:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">az quantum target list -o table\n<\/code><\/pre>\n\n\n\n<ol class=\"wp-block-list\" start=\"4\">\n<li>Local Q# program runs:<\/li>\n<\/ol>\n\n\n\n<pre><code class=\"language-bash\">dotnet run\n<\/code><\/pre>\n\n\n\n<p>You\u2019re done when:\n&#8211; You can list targets from the workspace\n&#8211; Your local quantum development loop works<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Error: <code>az: 'quantum' is not in the 'az' command group<\/code><\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Install the extension:<\/li>\n<\/ul>\n\n\n\n<pre><code class=\"language-bash\">az extension add -n quantum --upgrade\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Error: Authorization \/ permission denied<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confirm you have RBAC access to the resource group and workspace.<\/li>\n<li>Ask an administrator to grant appropriate roles at the workspace scope.<\/li>\n<li>Confirm subscription selection:<\/li>\n<\/ul>\n\n\n\n<pre><code class=\"language-bash\">az account show\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Error: No targets available \/ empty list<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confirm the workspace region supports Azure Quantum offerings.<\/li>\n<li>Check in Azure Portal whether you must enable a provider offering or accept terms.<\/li>\n<li>Verify your workspace location in docs and recreate in a supported location if needed.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Error: Q# templates not found<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>QDK installation steps change over time. Follow the latest official QDK docs from the Azure Quantum documentation hub:\n  https:\/\/learn.microsoft.com\/azure\/quantum\/<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing costs, delete the resource group (this deletes the workspace and storage account):<\/p>\n\n\n\n<pre><code class=\"language-bash\">az group delete -n \"$RG\" --yes --no-wait\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>: Azure schedules deletion of all resources in the resource group.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Simulator-first development<\/strong>: Validate correctness and reduce cost before QPU runs.<\/li>\n<li><strong>Separate environments<\/strong>: Use distinct workspaces for dev\/test and controlled runs (prod-like).<\/li>\n<li><strong>Hybrid design<\/strong>: Keep preprocessing\/postprocessing in scalable Azure compute; treat quantum targets as specialized batch backends.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>least privilege<\/strong> RBAC at the workspace scope.<\/li>\n<li>Prefer <strong>managed identities<\/strong> for automation (pipelines, services) over long-lived secrets.<\/li>\n<li>Require MFA and enforce <strong>Conditional Access<\/strong> for human operators.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Set <strong>Azure budgets and alerts<\/strong> on the subscription\/resource group.<\/li>\n<li>Restrict access to expensive targets (QPU offerings) using RBAC and internal approval workflows.<\/li>\n<li>Implement job submission guardrails:<\/li>\n<li>Max shots<\/li>\n<li>Max concurrency<\/li>\n<li>Require tags\/metadata for chargeback (where supported)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Batch experiments thoughtfully; avoid submitting thousands of tiny jobs if one parameterized job is supported (target-dependent).<\/li>\n<li>Reduce network overhead by keeping analysis in-region.<\/li>\n<li>Use structured result storage and avoid repeated downloads of large outputs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Design for <strong>retries<\/strong>: transient failures and queue delays are normal.<\/li>\n<li>Use idempotent job submission logic in automation (avoid duplicate runs).<\/li>\n<li>Keep a record of job inputs, target IDs, SDK versions, and random seeds (if applicable) for reproducibility.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Centralize logs and job metadata in a workspace-specific Log Analytics workspace (if diagnostics available).<\/li>\n<li>Tag resources consistently: <code>env<\/code>, <code>owner<\/code>, <code>costCenter<\/code>, <code>dataClassification<\/code>.<\/li>\n<li>Apply <strong>resource locks<\/strong> to prevent accidental deletion of production workspaces.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Naming:<\/li>\n<li><code>aqw-&lt;org&gt;-&lt;env&gt;-&lt;region&gt;-&lt;purpose&gt;<\/code><\/li>\n<li>Tagging:<\/li>\n<li><code>Environment=dev|test|prod<\/code><\/li>\n<li><code>Owner=&lt;team&gt;<\/code><\/li>\n<li><code>Project=&lt;project&gt;<\/code><\/li>\n<li><code>CostCenter=&lt;id&gt;<\/code><\/li>\n<li>Policy:<\/li>\n<li>Enforce required tags<\/li>\n<li>Restrict allowed regions to approved Azure Quantum regions<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Authentication<\/strong>: Microsoft Entra ID.<\/li>\n<li><strong>Authorization<\/strong>: Azure RBAC on the Azure Quantum workspace and related resources.<\/li>\n<li>Recommended approach:<\/li>\n<li>Human users: role-based access + MFA<\/li>\n<li>Automation: managed identity\/service principal with minimal roles<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Azure services typically encrypt data at rest in underlying storage services.<\/li>\n<li>Confirm:<\/li>\n<li>Storage account encryption settings (Microsoft-managed keys vs customer-managed keys)<\/li>\n<li>Whether Azure Quantum supports CMK directly or via storage configuration (verify in official docs)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Access is typically over HTTPS to Azure endpoints.<\/li>\n<li>If private networking is required, <strong>verify<\/strong> support for Private Link\/private endpoints for Azure Quantum in your region.<\/li>\n<li>If private endpoint is not available:<\/li>\n<li>Use Conditional Access<\/li>\n<li>Restrict who can access the workspace via RBAC<\/li>\n<li>Use hardened CI\/CD identities and locked-down build agents<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Store secrets in <strong>Azure Key Vault<\/strong> (or avoid secrets entirely with managed identity).<\/li>\n<li>Never commit credentials or job payloads containing secrets to source control.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>Azure Activity Log<\/strong> to audit control-plane actions.<\/li>\n<li>Enable diagnostic logs if available and route to Log Analytics \/ SIEM.<\/li>\n<li>Track:<\/li>\n<li>Role assignment changes<\/li>\n<li>Workspace updates<\/li>\n<li>Job submission metadata (in your own systems if service logs don\u2019t capture detail)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Provider execution may involve third parties:<\/li>\n<li>Review provider data handling, retention, and processing locations.<\/li>\n<li>Ensure contractual alignment (DPA, compliance requirements).<\/li>\n<li>For regulated workloads, consider:<\/li>\n<li>Data minimization (don\u2019t send sensitive data in job payloads)<\/li>\n<li>Synthetic or anonymized datasets for experiments<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Granting broad roles (Owner\/Contributor) to all developers.<\/li>\n<li>Allowing unrestricted QPU access without approvals or budgets.<\/li>\n<li>Storing secrets in code or notebooks.<\/li>\n<li>No separation between dev\/test experimentation and controlled environments.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Central platform team manages workspace provisioning.<\/li>\n<li>Developers get only the permissions needed to submit jobs and read results.<\/li>\n<li>Budgets and alerts are mandatory on any workspace that can access paid targets.<\/li>\n<li>Use IaC for repeatability and drift control.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<p>Because Azure Quantum is tightly tied to provider offerings, many \u201climits\u201d are contextual.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Known limitation patterns<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Region constraints<\/strong>: Not all regions support Azure Quantum workspaces or the same providers.<\/li>\n<li><strong>Offering enablement<\/strong>: Some targets require enabling offerings and accepting provider terms.<\/li>\n<li><strong>Batch\/queue model<\/strong>: Expect queue times and non-interactive execution patterns.<\/li>\n<li><strong>Provider-specific constraints<\/strong>: Shot limits, circuit depth limits, qubit limits, job payload formats.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Job quotas and concurrency limits may apply at:<\/li>\n<li>Workspace level<\/li>\n<li>Provider\/target level<\/li>\n<li>Verify quotas in provider documentation and Azure Quantum docs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Regional constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Workspace region determines which targets are available.<\/li>\n<li>Moving a workspace between regions is generally not a trivial operation; plan for redeployment.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing surprises<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>QPU targets can incur costs quickly with high shot counts.<\/li>\n<li>Automation can accidentally create large job volumes.<\/li>\n<li>Storage\/log analytics costs can accumulate over time.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compatibility issues<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SDK versions and target input formats evolve.<\/li>\n<li>Pin SDK versions in production and review release notes before upgrades.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational gotchas<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Jobs can fail for non-obvious reasons (invalid circuits, exceeded limits, provider service incidents).<\/li>\n<li>Results parsing is often target-specific; test and validate output schema.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Migration challenges<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Moving from one provider to another can require rewriting circuits or transpilation steps.<\/li>\n<li>Plan abstraction layers in your code to isolate provider-specific code.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Vendor-specific nuances<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cQuantum\u201d is not a single standard runtime today; expect heterogeneity.<\/li>\n<li>Treat Azure Quantum as an orchestration layer; portability still requires engineering discipline.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<p>Azure Quantum competes or overlaps with other quantum cloud platforms and local toolchains.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key alternatives<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Within Azure<\/strong>:<\/li>\n<li>Local-only development using QDK without Azure Quantum (good for learning)<\/li>\n<li>Classical HPC on Azure (Batch\/AKS\/VMs) for optimization problems that don\u2019t need quantum tooling<\/li>\n<li><strong>Other clouds<\/strong>:<\/li>\n<li>AWS Braket<\/li>\n<li>Google Quantum AI (platform access differs; often more research-oriented)<\/li>\n<li><strong>Other platforms<\/strong>:<\/li>\n<li>IBM Quantum Platform<\/li>\n<li><strong>Open-source\/self-managed<\/strong>:<\/li>\n<li>Qiskit (local simulators)<\/li>\n<li>Cirq (local simulators)<\/li>\n<li>PennyLane (hybrid workflows)<\/li>\n<li>Classical solvers (OR-Tools, Gurobi, CPLEX) for optimization<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison table<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Azure Quantum<\/strong><\/td>\n<td>Azure-centric teams needing governance + multi-provider access<\/td>\n<td>Azure-native IAM\/RBAC, workspace model, multiple providers\/targets<\/td>\n<td>Region\/offer availability varies; provider-specific formats persist<\/td>\n<td>You want quantum orchestration inside Azure with enterprise controls<\/td>\n<\/tr>\n<tr>\n<td><strong>Local QDK\/Q# only<\/strong><\/td>\n<td>Learning and prototyping without cloud execution<\/td>\n<td>No cloud cost, fast iteration<\/td>\n<td>No access to cloud QPUs via Azure Quantum workspace features<\/td>\n<td>You only need local simulation and education labs<\/td>\n<\/tr>\n<tr>\n<td><strong>AWS Braket<\/strong><\/td>\n<td>AWS-centric quantum experimentation<\/td>\n<td>AWS integrations, managed notebooks, multiple providers<\/td>\n<td>Different IAM\/governance model than Azure<\/td>\n<td>Your stack is primarily AWS and you want quantum there<\/td>\n<\/tr>\n<tr>\n<td><strong>IBM Quantum Platform<\/strong><\/td>\n<td>IBM hardware and ecosystem users<\/td>\n<td>Strong IBM tooling ecosystem, hardware access<\/td>\n<td>Vendor-focused; different integration model<\/td>\n<td>You specifically want IBM backends and tooling<\/td>\n<\/tr>\n<tr>\n<td><strong>Google Quantum AI<\/strong><\/td>\n<td>Research and experimental access (varies)<\/td>\n<td>Research alignment, quantum expertise<\/td>\n<td>Access model and enterprise integration may differ<\/td>\n<td>You\u2019re aligned with Google\u2019s quantum research ecosystem<\/td>\n<\/tr>\n<tr>\n<td><strong>Open-source simulators + OR-Tools\/Gurobi<\/strong><\/td>\n<td>Classical optimization in production today<\/td>\n<td>Mature, fast, deterministic tooling<\/td>\n<td>Not quantum; different research goals<\/td>\n<td>You need reliable optimization results now, not quantum experimentation<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<p>These examples are representative patterns. Provider\/target availability must be validated for your region and compliance needs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: Supply chain optimization research operations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A manufacturer needs to optimize multi-constraint scheduling across factories. They want to evaluate quantum-inspired solvers and potentially QPU experimentation while keeping governance strict.<\/li>\n<li><strong>Proposed architecture<\/strong>:<\/li>\n<li>Azure Quantum workspaces split by environment: <code>aqw-manufacturing-dev<\/code>, <code>aqw-manufacturing-prod<\/code><\/li>\n<li>AKS or Azure Batch for preprocessing (transforming ERP data into optimization instances)<\/li>\n<li>Azure Storage for job artifacts and instance datasets<\/li>\n<li>Azure Key Vault for pipeline credentials (or managed identity)<\/li>\n<li>Cost budgets + alerts at subscription\/RG scope<\/li>\n<li>CI\/CD pipeline submits jobs and stores outputs for analysis<\/li>\n<li><strong>Why Azure Quantum was chosen<\/strong>:<\/li>\n<li>Central access model inside Azure with RBAC and Activity Logs<\/li>\n<li>Multi-provider strategy for future QPU benchmarking<\/li>\n<li>Integration with existing Azure data and compute estate<\/li>\n<li><strong>Expected outcomes<\/strong>:<\/li>\n<li>Controlled experimentation with auditable access<\/li>\n<li>Repeatable benchmark runs and comparison dashboards<\/li>\n<li>Strong cost controls preventing accidental high-spend runs<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: Quantum education + prototype benchmarking<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: A small team building a decision-support product wants to learn quantum workflows and test small instances on simulators, without maintaining separate accounts across providers.<\/li>\n<li><strong>Proposed architecture<\/strong>:<\/li>\n<li>Single Azure Quantum workspace for the team<\/li>\n<li>GitHub repo + GitHub Actions for repeatable experiments<\/li>\n<li>Local development with Q# or Python SDK; simulator-first<\/li>\n<li>Optional: enable a single paid target for limited benchmarking with strict budget<\/li>\n<li><strong>Why Azure Quantum was chosen<\/strong>:<\/li>\n<li>Low operational overhead (managed workspace)<\/li>\n<li>Familiar Azure authentication and consolidated billing<\/li>\n<li><strong>Expected outcomes<\/strong>:<\/li>\n<li>Faster learning curve and reproducible experiments<\/li>\n<li>Controlled path to paid target benchmarking when ready<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Is Azure Quantum a quantum computer hosted by Microsoft?<\/strong><br\/>\n   No. Azure Quantum is a managed Azure service that provides a workspace and job management layer to access quantum targets (hardware, simulators, solvers) from Microsoft and partner providers.<\/p>\n<\/li>\n<li>\n<p><strong>Do I need a quantum hardware provider account separately?<\/strong><br\/>\n   Sometimes. Some provider offerings require enrollment or accepting additional terms. Check the offering details in Azure Portal and official docs.<\/p>\n<\/li>\n<li>\n<p><strong>Can I use Azure Quantum for free?<\/strong><br\/>\n   You can often learn with local simulators and minimal Azure resources. However, Azure-side resources (like storage) can have costs, and some targets are paid. Always check the official pricing page and your enabled targets.<\/p>\n<\/li>\n<li>\n<p><strong>What is an Azure Quantum workspace?<\/strong><br\/>\n   It\u2019s an Azure resource that represents your quantum \u201cproject boundary\u201d for targets and jobs\u2014similar to how a Machine Learning workspace groups ML assets.<\/p>\n<\/li>\n<li>\n<p><strong>Is Azure Quantum in the Compute category?<\/strong><br\/>\n   Yes in the sense that it orchestrates specialized compute targets (quantum\/optimization). It\u2019s not VM-based compute; it\u2019s a managed orchestration service for quantum compute backends.<\/p>\n<\/li>\n<li>\n<p><strong>Which regions support Azure Quantum?<\/strong><br\/>\n   Region availability changes over time. Use official docs to select a supported region and confirm provider offerings in that region.<\/p>\n<\/li>\n<li>\n<p><strong>Can I run Q# programs in Azure Quantum?<\/strong><br\/>\n   Azure Quantum supports quantum development workflows that include Q#. The exact submission path depends on supported targets and current tooling. Verify the latest QDK and Azure Quantum documentation.<\/p>\n<\/li>\n<li>\n<p><strong>Can I use Python with Azure Quantum?<\/strong><br\/>\n   Yes, Python SDK-based workflows are common for job submission and analysis. Verify the current packages and versions in official docs.<\/p>\n<\/li>\n<li>\n<p><strong>How do I control who can submit expensive QPU jobs?<\/strong><br\/>\n   Use Azure RBAC to limit access to the workspace and establish internal policies\/approvals. Also enforce budgets and alerts.<\/p>\n<\/li>\n<li>\n<p><strong>Does Azure Quantum support private networking (Private Link)?<\/strong><br\/>\n   Support can vary by service and region. Verify current Private Link\/private endpoint support in official docs.<\/p>\n<\/li>\n<li>\n<p><strong>Where are job inputs and outputs stored?<\/strong><br\/>\n   Azure Quantum uses workspace-associated storage mechanisms. Review workspace configuration and documentation to understand storage accounts, encryption, and access patterns.<\/p>\n<\/li>\n<li>\n<p><strong>What\u2019s the difference between a provider and a target?<\/strong><br\/>\n   A provider is the vendor\/integration; a target is a specific backend you submit jobs to (e.g., a simulator or a particular QPU).<\/p>\n<\/li>\n<li>\n<p><strong>Is Azure Quantum suitable for production workloads today?<\/strong><br\/>\n   Many teams use it for production-like research operations and decision-support pipelines. True \u201cproduction quantum advantage\u201d workloads are still emerging; design for experimentation, governance, and cost control.<\/p>\n<\/li>\n<li>\n<p><strong>How do I estimate costs before running jobs?<\/strong><br\/>\n   Use the official Azure Quantum pricing page, provider pricing details, and small-scale tests. Always start with simulators and low shot counts.<\/p>\n<\/li>\n<li>\n<p><strong>What should I log for reproducibility?<\/strong><br\/>\n   Record SDK versions, target IDs, job IDs, job parameters, random seeds, circuit\/program versions, and environment metadata.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Azure Quantum<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official documentation<\/td>\n<td>Azure Quantum documentation (Microsoft Learn) \u2014 https:\/\/learn.microsoft.com\/azure\/quantum\/<\/td>\n<td>Primary source for concepts, regions, targets, SDK guidance, and tutorials<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Azure Quantum pricing \u2014 https:\/\/azure.microsoft.com\/pricing\/details\/azure-quantum\/<\/td>\n<td>Authoritative pricing model and provider pricing references<\/td>\n<\/tr>\n<tr>\n<td>Pricing tools<\/td>\n<td>Azure Pricing Calculator \u2014 https:\/\/azure.microsoft.com\/pricing\/calculator\/<\/td>\n<td>Estimate supporting Azure costs (storage, compute, networking)<\/td>\n<\/tr>\n<tr>\n<td>Getting started<\/td>\n<td>Azure Quantum \u201cget started\u201d paths (in docs hub) \u2014 https:\/\/learn.microsoft.com\/azure\/quantum\/<\/td>\n<td>Step-by-step onboarding with current tooling<\/td>\n<\/tr>\n<tr>\n<td>SDK reference<\/td>\n<td>Azure SDK docs (search \u201cazure-quantum\u201d within Learn) \u2014 https:\/\/learn.microsoft.com\/<\/td>\n<td>Versioned guidance and SDK patterns<\/td>\n<\/tr>\n<tr>\n<td>Samples<\/td>\n<td>Azure Quantum samples (GitHub; verify official org) \u2014 https:\/\/github.com\/microsoft\/quantum<\/td>\n<td>Practical examples and references maintained by Microsoft<\/td>\n<\/tr>\n<tr>\n<td>Q# \/ QDK<\/td>\n<td>Microsoft Quantum Development Kit documentation (via Learn hub) \u2014 https:\/\/learn.microsoft.com\/azure\/quantum\/<\/td>\n<td>Q# language, tooling, local simulation, and workflow guidance<\/td>\n<\/tr>\n<tr>\n<td>Videos<\/td>\n<td>Microsoft Azure \/ Microsoft Quantum content (YouTube) \u2014 https:\/\/www.youtube.com\/@MicrosoftAzure<\/td>\n<td>Talks, demos, and updates (search for Azure Quantum-specific playlists)<\/td>\n<\/tr>\n<tr>\n<td>Architecture guidance<\/td>\n<td>Azure Architecture Center \u2014 https:\/\/learn.microsoft.com\/azure\/architecture\/<\/td>\n<td>Patterns for governance, IAM, logging, and hybrid architectures (apply to quantum solutions)<\/td>\n<\/tr>\n<tr>\n<td>Community learning<\/td>\n<td>Qiskit textbook \u2014 https:\/\/qiskit.org\/learn\/<\/td>\n<td>Strong fundamentals for quantum computing concepts (complementary to Azure Quantum)<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<blockquote>\n<p>Note: GitHub repositories and package names evolve. Prefer links from Microsoft Learn pages to ensure you\u2019re using current samples.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<p>Presented neutrally; verify course availability and outlines on each website.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>DevOpsSchool.com<\/strong><br\/>\n   &#8211; Suitable audience: Cloud\/DevOps engineers, architects, platform teams<br\/>\n   &#8211; Likely learning focus: Azure\/DevOps\/cloud operations foundations; may include emerging tech modules<br\/>\n   &#8211; Mode: check website<br\/>\n   &#8211; Website: https:\/\/www.devopsschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>ScmGalaxy.com<\/strong><br\/>\n   &#8211; Suitable audience: DevOps learners, build\/release engineers, SRE learners<br\/>\n   &#8211; Likely learning focus: SCM\/CI\/CD practices and related tooling<br\/>\n   &#8211; Mode: check website<br\/>\n   &#8211; Website: https:\/\/www.scmgalaxy.com\/<\/p>\n<\/li>\n<li>\n<p><strong>CLoudOpsNow.in<\/strong><br\/>\n   &#8211; Suitable audience: Cloud operations and platform engineering learners<br\/>\n   &#8211; Likely learning focus: CloudOps, monitoring, operations practices<br\/>\n   &#8211; Mode: check website<br\/>\n   &#8211; Website: https:\/\/www.cloudopsnow.in\/<\/p>\n<\/li>\n<li>\n<p><strong>SreSchool.com<\/strong><br\/>\n   &#8211; Suitable audience: SREs, operations teams, reliability engineers<br\/>\n   &#8211; Likely learning focus: Reliability engineering, incident response, monitoring<br\/>\n   &#8211; Mode: check website<br\/>\n   &#8211; Website: https:\/\/www.sreschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>AiOpsSchool.com<\/strong><br\/>\n   &#8211; Suitable audience: Ops teams adopting AIOps patterns, monitoring engineers<br\/>\n   &#8211; Likely learning focus: AIOps concepts, observability, automation<br\/>\n   &#8211; Mode: check website<br\/>\n   &#8211; Website: https:\/\/www.aiopsschool.com\/<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<p>Listed as training resources\/platforms; verify current offerings and backgrounds on each site.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>RajeshKumar.xyz<\/strong><br\/>\n   &#8211; Likely specialization: DevOps\/cloud training and mentoring (verify on site)<br\/>\n   &#8211; Suitable audience: Engineers seeking hands-on coaching<br\/>\n   &#8211; Website: https:\/\/rajeshkumar.xyz\/<\/p>\n<\/li>\n<li>\n<p><strong>devopstrainer.in<\/strong><br\/>\n   &#8211; Likely specialization: DevOps tooling and practices (verify on site)<br\/>\n   &#8211; Suitable audience: Beginners to intermediate DevOps learners<br\/>\n   &#8211; Website: https:\/\/devopstrainer.in\/<\/p>\n<\/li>\n<li>\n<p><strong>devopsfreelancer.com<\/strong><br\/>\n   &#8211; Likely specialization: DevOps consulting\/training content (verify on site)<br\/>\n   &#8211; Suitable audience: Teams or individuals needing project-based guidance<br\/>\n   &#8211; Website: https:\/\/www.devopsfreelancer.com\/<\/p>\n<\/li>\n<li>\n<p><strong>devopssupport.in<\/strong><br\/>\n   &#8211; Likely specialization: DevOps support and training resources (verify on site)<br\/>\n   &#8211; Suitable audience: Practitioners seeking operational troubleshooting help<br\/>\n   &#8211; Website: https:\/\/www.devopssupport.in\/<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<p>Neutral descriptions; validate service offerings directly with the providers.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>cotocus.com<\/strong><br\/>\n   &#8211; Likely service area: Cloud\/DevOps consulting (verify exact scope on site)<br\/>\n   &#8211; Where they may help: Cloud adoption planning, platform engineering, operations enablement<br\/>\n   &#8211; Consulting use case examples: Setting up Azure governance guardrails, CI\/CD pipelines, monitoring baselines<br\/>\n   &#8211; Website: https:\/\/cotocus.com\/<\/p>\n<\/li>\n<li>\n<p><strong>DevOpsSchool.com<\/strong><br\/>\n   &#8211; Likely service area: DevOps consulting and training services (verify current portfolio)<br\/>\n   &#8211; Where they may help: Toolchain standardization, process enablement, platform practices<br\/>\n   &#8211; Consulting use case examples: CI\/CD modernization, infrastructure automation, operational best practices<br\/>\n   &#8211; Website: https:\/\/www.devopsschool.com\/<\/p>\n<\/li>\n<li>\n<p><strong>DEVOPSCONSULTING.IN<\/strong><br\/>\n   &#8211; Likely service area: DevOps\/cloud consulting (verify exact scope on site)<br\/>\n   &#8211; Where they may help: Cloud operations, automation, reliability improvements<br\/>\n   &#8211; Consulting use case examples: Cost optimization initiatives, governance implementation, pipeline hardening<br\/>\n   &#8211; Website: https:\/\/devopsconsulting.in\/<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before Azure Quantum<\/h3>\n\n\n\n<p>To get value from Azure Quantum, build foundations in:\n&#8211; <strong>Azure fundamentals<\/strong>: subscriptions, resource groups, regions, ARM, RBAC\n&#8211; <strong>Security basics<\/strong>: Entra ID, managed identities, Key Vault, least privilege\n&#8211; <strong>Python or .NET basics<\/strong> (depending on your preferred quantum SDK route)\n&#8211; <strong>Optimization fundamentals<\/strong>:\n  &#8211; Linear algebra basics\n  &#8211; Graph problems, constraint satisfaction\n  &#8211; QUBO\/Ising formulations (helpful for optimization use cases)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after Azure Quantum<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Quantum algorithm concepts:<\/li>\n<li>Measurement, superposition, entanglement<\/li>\n<li>Common algorithms (Grover, QAOA concepts, VQE concepts)<\/li>\n<li>Provider-specific tooling:<\/li>\n<li>Qiskit\/Cirq\/PennyLane (if your target requires it)<\/li>\n<li>Hybrid architecture patterns:<\/li>\n<li>Data engineering on Azure<\/li>\n<li>Orchestration with Functions\/Durable Functions, Batch, AKS<\/li>\n<li>Observability and cost governance:<\/li>\n<li>Azure Monitor\/Log Analytics patterns<\/li>\n<li>Budgeting, tagging, chargeback models<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use Azure Quantum<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Solutions Architect (specializing in emerging compute\/quantum)<\/li>\n<li>Platform Engineer \/ DevOps Engineer supporting research platforms<\/li>\n<li>Applied Scientist \/ Research Engineer (quantum\/optimization)<\/li>\n<li>Data Scientist \/ Optimization Engineer<\/li>\n<li>Security Engineer reviewing provider and data handling models<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Azure does not currently have a widely recognized, dedicated \u201cAzure Quantum certification\u201d comparable to core Azure cert tracks (verify in official training catalog). Recommended adjacent certifications:\n&#8211; Azure Fundamentals (AZ-900)\n&#8211; Azure Administrator (AZ-104)\n&#8211; Azure Security Engineer (AZ-500)\n&#8211; Azure Solutions Architect Expert (AZ-305)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build a simulator-first quantum experiment harness that:<\/li>\n<li>Runs a circuit family<\/li>\n<li>Captures metadata and outputs<\/li>\n<li>Produces a reproducible report<\/li>\n<li>Implement a small optimization pipeline:<\/li>\n<li>Generate random graph instances<\/li>\n<li>Encode into a chosen model (QUBO\/Ising)<\/li>\n<li>Run solver experiments (simulated\/classical if quantum solvers aren\u2019t available)<\/li>\n<li>Build a CI workflow that:<\/li>\n<li>Validates code quality<\/li>\n<li>Runs a small test suite on simulators<\/li>\n<li>Publishes results artifacts<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Azure Quantum Workspace<\/strong>: An Azure resource that organizes quantum providers, targets, and jobs.<\/li>\n<li><strong>Provider<\/strong>: A quantum computing vendor\/integration (hardware or solver provider) made available through Azure Quantum.<\/li>\n<li><strong>Target<\/strong>: A specific backend you can submit a job to (e.g., a simulator or a specific QPU).<\/li>\n<li><strong>Job<\/strong>: A submitted unit of work containing an input payload plus metadata, executed on a target.<\/li>\n<li><strong>QPU (Quantum Processing Unit)<\/strong>: Quantum hardware that executes quantum circuits.<\/li>\n<li><strong>Qubit<\/strong>: The basic unit of quantum information.<\/li>\n<li><strong>Shot<\/strong>: One execution of a quantum circuit; jobs often run many shots to sample outcomes.<\/li>\n<li><strong>Circuit<\/strong>: A sequence of quantum gates and measurements defining a quantum computation.<\/li>\n<li><strong>Q# (Q-sharp)<\/strong>: Microsoft\u2019s quantum programming language (part of the Quantum Development Kit).<\/li>\n<li><strong>QDK (Quantum Development Kit)<\/strong>: Microsoft tooling for quantum development, simulation, and related workflows.<\/li>\n<li><strong>RBAC<\/strong>: Role-Based Access Control in Azure for authorizing actions on resources.<\/li>\n<li><strong>Managed Identity<\/strong>: Azure identity for applications to access resources without managing secrets.<\/li>\n<li><strong>QUBO<\/strong>: Quadratic Unconstrained Binary Optimization, a common formulation for optimization problems.<\/li>\n<li><strong>Ising model<\/strong>: A physics-inspired model often used to represent optimization problems similar to QUBO.<\/li>\n<li><strong>Hybrid workflow<\/strong>: A pipeline combining classical compute with quantum\/optimization job submissions and classical postprocessing.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Azure Quantum is Azure\u2019s managed <strong>Compute<\/strong> service for orchestrating quantum computing and optimization workloads through a centralized <strong>workspace<\/strong>. It matters because it brings quantum experimentation into the same operational world as the rest of Azure: Entra ID authentication, RBAC authorization, governance controls, and cost management.<\/p>\n\n\n\n<p>Use Azure Quantum when you need:\n&#8211; Multi-provider access and a consistent job model\n&#8211; Azure-native security and governance\n&#8211; A scalable hybrid architecture where classical Azure compute surrounds specialized quantum targets<\/p>\n\n\n\n<p>Cost and security are driven by:\n&#8211; Which targets you enable (simulator vs paid QPU)\n&#8211; Job volume and shot counts\n&#8211; Supporting Azure costs (storage, monitoring, classical compute)\n&#8211; Strong IAM, budgets, and environment separation<\/p>\n\n\n\n<p>Next step: follow the official Azure Quantum documentation hub to select a supported region, confirm available targets, and run the newest end-to-end sample for your preferred SDK (Q# or Python):<br\/>\nhttps:\/\/learn.microsoft.com\/azure\/quantum\/<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Compute<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[40,26],"tags":[],"class_list":["post-388","post","type-post","status-publish","format-standard","hentry","category-azure","category-compute"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/388","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=388"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/388\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=388"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=388"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=388"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}