Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Azure Solution Architect

    1

    Plan secure, resilient Azure platforms with clear identity, network, recovery, governance, and cost tradeoffs.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Azure Solution Architect

    Azure Solution Architect

    Example session with this skill installed

    Plan an Azure landing zone and production architecture for a B2B SaaS API being migrated from two on-premises .NET services. Peak load is 600 requests/second with brief bursts, transactional data currently lives in SQL Server, documents live on a file share, users authenticate through Microsoft Entra ID, and the team operates both Azure and on-premises systems. Target 99.9% availability, but RPO/RTO and data residency are not yet approved. Recommend hierarchy/subscriptions, network and hybrid connectivity, app and data services, identity/security, deployment, observability, backup/DR, cost drivers, and the key decisions to validate. Do not claim tenant access or quote unverified current pricing or quotas.

    • Read your context and instructions
    • Compiled the azure solution architect

    Sample Azure migration blueprint

    Recommendation

    Use a governed landing zone with clear production/nonproduction boundaries, private application and data paths, and staged migration waves. Keep the initial design regional and avoid choosing a secondary-region DR pattern until the business approves RPO/RTO and residency.

    Facts and open decisions

    Provided: two on-premises .NET services, 600 requests/second peak with brief bursts, SQL Server transactions, file-share documents, Entra ID authentication, hybrid operation, 99.9% target.

    Unknown: traffic mix and read/write ratio, supported .NET/runtime versions, database size and dependencies, document size/retention, data region/residency, RPO/RTO, tenant isolation, compliance controls, connectivity bandwidth, budget, and team AKS maturity.

    • Treat 99.9% as a target, not an SLA or achieved result.

    Architecture outline

    Governance: Establish management groups aligned to policy and environment boundaries; separate production and nonproduction subscriptions where ownership, blast radius, quotas, or billing justify it. Use consistent resource naming, ownership/data tags, budgets, policy assignments, and documented exception handling. Keep platform, security, and workload responsibilities explicit.
    2.

    Network: Select hub-spoke for controlled shared network services or Virtual WAN if multi-site scale and operations warrant it. Use private subnets, NSGs, explicit route ownership, private endpoints where supported, and private DNS zones. For hybrid connectivity compare VPN and ExpressRoute using bandwidth, latency, redundancy, and operational needs. Document on-prem routes, failover, DNS resolution, and overlapping address-space risks.
    3.

    Application: Begin with App Service or Container Apps for straightforward managed hosting; consider AKS only if Kubernetes capabilities and team operations justify its added responsibility. Place public ingress behind an appropriately configured edge or gateway, protect API routes, apply health checks, bounded concurrency, timeouts, and gradual rollout with rollback.
    4.

    Data and files: Compare Azure SQL/SQL Managed Instance with current SQL Server compatibility and feature requirements before migration. Model connection pooling, storage growth, HA, backup, and restore. Move documents to private Blob Storage or Azure Files according to file semantics, access patterns, retention, and application changes. Enforce encryption, least-privilege managed identity, and lifecycle controls.
    5.

    Identity and security: Use Entra federation for workforce access and managed identities for workloads. Minimize permanent Owner/Contributor assignments; use scoped RBAC and controlled elevation. Store secrets and keys in Key Vault where required. Review public exposure, logging, policy exceptions, threat model, and alert ownership.
    6.

    Operations: Define SLOs and instrument API latency/errors, saturation, SQL connections, dependency health, and migration outcomes. Use Azure Monitor/Application Insights as appropriate, route alerts to an owned response process, and document support runbooks. Manage infrastructure with reviewed Bicep or Terraform, staged environments, smoke tests, and a rollback or forward-recovery plan.

    Migration and recovery

    Inventory dependencies and classify data before selecting a migration method. Pilot a low-risk service, test authentication and network flows, measure representative workload, and validate SQL compatibility. Agree RPO/RTO first; then design backup retention, restore exercises, and any Site Recovery or regional failover. A successful backup job alone does not demonstrate recoverability.

    Cost and validation

    Measure app compute, SQL sizing/storage/IO, network egress, private endpoint and monitoring usage, backup retention, and hybrid connectivity. Validate current regional service availability, quotas, pricing, SQL migration compatibility, and platform limits with Microsoft’s current official documentation and workload tests.

    Next actions

    Approve data residency and RPO/RTO; collect database and file-share inventories; document routes and DNS; choose a representative migration pilot; define security and SLO acceptance tests. This is a sample design only; no tenant was inspected and no resources were deployed.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Azure Solution Architect

    Convert business and technical requirements into practical Microsoft Azure architecture that teams can review, implement, and operate. This advisor supports enterprise and SaaS teams, platform engineering, DevOps/SRE, migration programs, and Microsoft-centered organizations.

    Deliverables

    • Requirements and workload profile with confirmed facts, assumptions, unknowns, and open decisions
    • Tenant, management group, subscription, and resource group structure
    • Region, availability zone, hub-spoke or Virtual WAN networking, DNS, and private connectivity plan
    • Fit-for-purpose compute, data, messaging, integration, and AI service options
    • Entra identity, managed identity, RBAC, Key Vault, policy, and security boundaries
    • SLO, observability, backup, restore, RPO/RTO, and disaster recovery guidance
    • IaC, deployment, migration, rollback, quota, governance, and FinOps recommendations

    Approach

    Start from business outcomes, critical user journeys, workload shape, identity boundaries, and recovery requirements. Clearly distinguish observed facts from targets, assumptions, recommendations, and unknowns. Compare service patterns with explicit tradeoffs and failure modes. Prefer a simple design that satisfies needs while leaving a safe path to evolve.

    Safety and freshness

    Do not infer tenant/subscription access, deployed resources, certification, compliance, quotas, prices, SLAs, regional availability, restore success, or security posture without evidence. Azure features and limits change, so verify freshness-sensitive claims against current official Microsoft documentation. Backups need restore tests; zones and secondary regions solve different problems; managed services still have limits; retries require idempotency and downstream protection. This skill is advisory and does not deploy or modify Azure resources unless separately authorized tools are available.

    This skill provides architecture advice and cannot confirm tenant or subscription state, inspect deployed resources, deploy changes, or prove compliance, certification, availability, or restore success. Validate current Azure pricing, quotas, service availability, region support, and product behavior with official Microsoft sources. Recommendations depend on supplied requirements and require testing and authorized review.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Browser
    Network Access

    File Scopes

    No
    direct
    account
    or
    file
    access
    required

    Architecture advisory from requirements supplied by the user. Browser/network access is optional and should be read-only for official Microsoft documentation. Do not sign in to tenants, inspect subscriptions, change resources, or send customer data unless separately authorized integrations support that action.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    No. It provides design guidance from available information. It does not claim tenant/subscription access and does not deploy or modify Azure resources.

    It can identify the cost and capacity factors to evaluate, but does not invent current prices or limits. Verify region-specific service availability, quotas, and pricing from official Microsoft sources and your workload assumptions.

    Provide service and dependency inventories, runtime and SQL versions, data size, traffic, identity and network requirements, residency, RPO/RTO, maintenance constraints, and success criteria. The skill will label gaps for confirmation.

    New in DevOps & Cloud