Arckit Azure Research

• Look in: projects/{project}/external/
• File types: PDF (.pdf), Word (.docx), Markdown (.md), CSV (.csv)
• What to extract: Current Azure usage, cost reports, Azure Advisor findings, migration assessments
• Examples: azure-cost-report.csv, azure-advisor-findings.pdf, cloud-assessment.docx

User prompt: If no external Azure docs found but they would improve recommendations, ask: "Do you have any existing Azure cost reports, Azure Advisor findings, or cloud assessments? Place them in projects/{project}/external/ and re-run, or skip."

Important: This agent works without external documents. They enhance output quality but are never blocking.

• Citation traceability: When referencing content from external documents, follow the citation instructions in .arckit/references/citation-instructions.md. Place inline citation markers (e.g., [PP-C1]) next to findings informed by source documents and populate the "External References" section in the template.

Step 2: Read Available Documents

Find the project directory in projects/ (user may specify name/number, otherwise use most recent). Scan for existing artifacts:

MANDATORY (warn if missing):

• ARC-*-REQ-*.md in projects/{project}/ — Requirements specification
  • Extract: FR (compute/AI), NFR-P (performance), NFR-SEC (security), INT (integration), DR (data) requirements for Azure service matching
  • If missing: STOP and report that $arckit-requirements must be run first
• ARC-000-PRIN-*.md in projects/000-global/ — Architecture principles
  • Extract: Cloud policy, approved services, compliance requirements, security standards
  • If missing: warn user to run $arckit-principles first

RECOMMENDED (read if available, note if missing):

• ARC-*-STKE-*.md in projects/{project}/ — Stakeholder analysis
  • Extract: User personas, scalability expectations, compliance stakeholders

OPTIONAL (read if available, skip silently if missing):

• ARC-*-RISK-*.md in projects/{project}/ — Risk register
  • Extract: Technology risks, vendor lock-in risks, compliance risks
• ARC-*-DATA-*.md in projects/{project}/ — Data model
  • Extract: Data storage needs, data governance, retention requirements

What to extract from each document:

• Requirements: FR/NFR/INT/DR IDs for Azure service category mapping
• Principles: Cloud-first policy, approved platforms, compliance constraints
• Stakeholders: Scale expectations, compliance requirements

Detect if UK Government project (look for "UK Government", "Ministry of", "Department for", "NHS", "MOD").

Step 3: Read Template

• Read .arckit/templates/azure-research-template.md for output structure

Step 4: Extract Requirements for Azure Mapping

Read the requirements document and identify Azure service needs across these categories. Use the MCP tools to dynamically discover the best-fit Azure services for each requirement — do not limit yourself to the examples below:

• Compute (FR-xxx, NFR-P-xxx, NFR-S-xxx): e.g. containers, web apps, serverless, VMs, scale sets
• Data (DR-xxx, NFR-P-xxx): e.g. relational, NoSQL, caching, search, data warehouse, data lake
• Integration (INT-xxx): e.g. API management, messaging, event streaming, workflow orchestration
• Security (NFR-SEC-xxx): e.g. identity, secrets management, network security, threat protection
• AI/ML (FR-xxx): e.g. AI models, ML platforms, cognitive services, conversational AI

Use microsoft_docs_search to discover which Azure services match each requirement rather than assuming a fixed mapping. Azure frequently launches new services and features — let the MCP documentation guide your recommendations.

Step 5: Research Azure Services Using MCP

Mode detection: Attempt a single microsoft_docs_search call. If it succeeds, continue in SUPERCHARGED mode using MCP tools as described below. If MCP tools are unavailable, switch to STANDALONE mode using these substitutions for ALL research in this step:

For each requirement category, use MCP tools extensively (or their STANDALONE equivalents):

Service Discovery:

• microsoft_docs_search: "[requirement] Azure service" for each category
• Follow up with microsoft_docs_fetch for detailed service pages

Service Deep Dive (for each identified service):

• microsoft_docs_fetch: Fetch full docs from learn.microsoft.com/azure/[service-name]/
• Extract: features, pricing tiers (Basic/Standard/Premium), SLA, security features, integration capabilities, UK region availability

Architecture Patterns:

• microsoft_docs_search: "Azure architecture [pattern type]"
• microsoft_docs_fetch: Fetch Azure Architecture Center reference architectures

Well-Architected Assessment (all 5 pillars):

• microsoft_docs_search: "Azure Well-Architected [pillar] [service]"
• Pillars: Reliability, Security, Cost Optimization, Operational Excellence, Performance Efficiency

Security Benchmark Mapping:

• microsoft_docs_search: "Azure Security Benchmark [control domain]"
• Control Domains: NS (Network Security), IM (Identity Management), PA (Privileged Access), DP (Data Protection), AM (Asset Management), LT (Logging and Threat Detection), IR (Incident Response), PV (Posture and Vulnerability Management), ES (Endpoint Security), BR (Backup and Recovery), DS (DevOps Security), GS (Governance and Strategy)

Code Samples:

• microsoft_code_sample_search: "Azure [service] bicep", "Azure [service] terraform", "Azure [service] [language]"
• Languages: bicep, terraform, csharp, python, javascript, powershell

Step 6: UK Government Specific Research (if applicable)

• G-Cloud: Search Digital Marketplace for "Microsoft Azure", note framework reference
• Data Residency: Confirm UK South and UK West availability, check geo-replication stays within UK
• Classification: OFFICIAL = standard Azure, OFFICIAL-SENSITIVE = additional controls, SECRET = Azure Government UK (separate sovereign cloud)
• NCSC: microsoft_docs_fetch: https://learn.microsoft.com/azure/compliance/offerings/offering-uk-ncsc

Step 7: Cost Estimation

• microsoft_docs_search: "Azure [service] pricing" for each service
• Map requirements to service tiers
• Calculate based on projected usage with UK region pricing
• Include optimization: Reserved Instances, Azure Hybrid Benefit, Spot VMs, auto-scaling

Step 7b: Government Implementation Patterns

Search govreposcrape for existing UK government implementations using the Azure services recommended above:

1. Search by service: For each recommended Azure service, query govreposcrape:
   • "[Azure service] UK government", "Azure [service] implementation"
   • Example: "Azure Functions UK government", "Cosmos DB government"
   • Use resultMode: "snippets" and limit: 5 per query
2. Note findings: For each relevant result:
   • Which department/organisation uses this service
   • Architecture patterns observed (serverless, containerised, etc.)
   • Common configurations or companion services
3. Include in output: Add a "Government Precedent" subsection to each service recommendation:
   • If precedent found: "[Org] uses [service] for [purpose]" — adds confidence to recommendation
   • If no precedent found: "No UK government precedent identified" — note as a consideration (not a blocker)

If govreposcrape tools are unavailable, skip this step silently and proceed.

Step 8: Generate Architecture Diagram

Create a Mermaid diagram showing:

• Azure services and relationships
• UK region placement (UK South primary, UK West DR)
• Network topology (VNet, subnets, private endpoints)
• Security boundaries (NSGs, WAF, Firewall)
• Data flows

Step 9: Detect Version and Determine Increment

Check if a previous version of this document exists in the project directory:

Use Glob to find existing projects/{project-dir}/research/ARC-{PROJECT_ID}-AZRS-*-v*.md files. If matches are found, read the highest version number from the filenames.

If no existing file: Use VERSION="1.0"

If existing file found:

1. Read the existing document to understand its scope (Azure services researched, architecture patterns, recommendations made)
2. Compare against the current requirements and your new research findings
3. Determine version increment:
   • Minor increment (e.g., 1.0 → 1.1, 2.1 → 2.2): Use when the scope is unchanged — refreshed pricing, updated service features, corrected details, minor additions within existing categories
   • Major increment (e.g., 1.0 → 2.0, 1.3 → 2.0): Use when scope has materially changed — new requirement categories, removed categories, fundamentally different service recommendations, significant new requirements added since last version
4. Use the determined version for ALL subsequent references:
   • Document ID and filename: ARC-{PROJECT_ID}-AZRS-v${VERSION}.md
   • Document Control: Version field
   • Revision History: Add new row with version, date, "AI Agent", description of changes, "PENDING", "PENDING"

Before writing the file, read .arckit/references/quality-checklist.md and verify all Common Checks plus the AZRS per-type checks pass. Fix any failures before proceeding.

Step 10: Write Output

Use the Write tool to save the complete document to projects/{project-dir}/research/ARC-{PROJECT_ID}-AZRS-v${VERSION}.md following the template structure.

Auto-populate fields:

• [PROJECT_ID] from project path
• [VERSION] = determined version from Step 9
• [DATE] = current date (YYYY-MM-DD)
• [STATUS] = "DRAFT"
• [CLASSIFICATION] = "OFFICIAL" (UK Gov) or "PUBLIC"

Include the generation metadata footer:

**Generated by**: ArcKit `$arckit-azure-research` agent
**Generated on**: {DATE}
**ArcKit Version**: {ArcKit version from context}
**Project**: {PROJECT_NAME} (Project {PROJECT_ID})
**AI Model**: {Actual model name}

DO NOT output the full document. Write it to file only.

Step 11: Return Summary

Return ONLY a concise summary including:

• Project name and file path created
• Azure services recommended (table: category, service, tier, monthly estimate)
• Architecture pattern used
• Security alignment (Security Benchmark controls, Well-Architected pillars)
• UK Government suitability (G-Cloud, UK regions, classification)
• Estimated monthly cost
• What's in the document
• Next steps ($arckit-diagram, $arckit-secure, $arckit-devops)

Quality Standards

• Official Sources Only: Prefer Microsoft Learn documentation via MCP (SUPERCHARGED mode). If MCP is unavailable, use WebSearch/WebFetch targeting learn.microsoft.com (STANDALONE mode). Avoid third-party blogs in both modes
• UK Focus: Always check UK South/West region availability
• Well-Architected: Assess every recommendation against all 5 pillars
• Security Benchmark: Map recommendations to Azure Security Benchmark controls (12 domains)
• Cost Accuracy: Use Azure Pricing Calculator data where possible
• Code Samples: Prefer Bicep (Azure-native) or Terraform for IaC

Edge Cases

• No requirements found: Stop, tell user to run $arckit-requirements
• Service not in UK regions: Flag as a blocker for UK Government projects, suggest alternatives
• SECRET classification: Note that standard Azure is not suitable, suggest Azure Government UK

Important Notes

• Markdown escaping: When writing less-than or greater-than comparisons, always include a space after < or > (e.g., < 3 seconds, > 99.9% uptime) to prevent markdown renderers from interpreting them as HTML tags or emoji

User Request

$ARGUMENTS

Suggested Next Steps

After completing this command, consider running:

• $arckit-diagram -- Create Azure architecture diagrams
• $arckit-devops -- Design Azure DevOps pipeline
• $arckit-finops -- Create Azure cost management strategy
• $arckit-adr -- Record Azure service selection decisions