Azure Smart City Iot Solution Builder

Azure Smart City IoT solution builder

Turn a high-level Smart City or Azure IoT idea into a deployable architecture, governance model, and phased implementation backlog with explicit assumptions and operational controls.

When to invoke

• "I want to build an IoT solution on Azure."
• "Design a Smart City architecture for traffic, lighting, or waste."
• "How do I connect devices, analytics, and alerts?"
• "Create a roadmap and backlog for an urban platform."
• "Plan an Azure IoT solution with edge processing."

Prerequisites and context

Before proposing architecture that involves edge computing, review Azure IoT Edge documentation: https://learn.microsoft.com/azure/iot-edge/

Minimum documentation topics to review are What is Azure IoT Edge, runtime architecture, supported systems, version history/release notes, and relevant Linux/Windows quickstarts for the scenario. If documentation cannot be consulted, state that explicitly and continue with marked assumptions.

Procedure

1. Confirm scope and constraints: city domain, device count, telemetry frequency, retention, regions, latency, availability, privacy, and integrations such as SCADA, GIS, ERP, ticketing, and APIs.
2. Build the capability map across device and edge, ingestion and messaging, data and analytics, operations, and governance.
3. Select Azure services and document trade-offs instead of naming services without rationale.
4. Define non-functional design: reliability, security, cost controls, and data lifecycle.
5. Produce a phased delivery plan for pilot, multi-domain integration, and city-scale rollout.
6. Use references/smart-city-solution-template.md to standardize the final artifact when a full solution document is requested.

Capability map

Azure service selection

Non-functional design

Delivery plan

Related primitives

Limits

• Do not jump to deployment before validating prerequisites.
• Do not recommend single-region production for critical city workloads.
• Do not omit operational ownership, incident handling, SLAs, or change windows.
• If specialized runtime skills are unavailable, continue with this skill and mark assumptions.

Progressive disclosure and bundled resources

• references/smart-city-solution-template.md: standard output structure for full scenario documents.

Output template

## Smart City IoT solution

**Status:** proposed | needs input | blocked
**Domain:** `<traffic|lighting|waste|water|energy|public safety|other>`
**Assumptions:** <confirmed assumptions and unknowns>

### 1. Context and objectives
<scope, constraints, stakeholders, KPIs>

### 2. Proposed architecture
<components, data flow, and service choices>

### 3. Technology decisions and trade-offs
| Decision | Choice | Alternatives | Rationale |
| --- | --- | --- | --- |

### 4. Security, operations, and cost controls
<governance checklist, observability, resilience, cost strategy>

### 5. Phased implementation plan
| Phase | Milestones | Exit criteria | Risks |
| --- | --- | --- | --- |

### 6. Risks and open questions
<items requiring confirmation>

Quality gate

• Azure IoT Edge documentation was reviewed or the inability to review it is stated with assumptions.
• Scope includes domain, scale, telemetry frequency, retention, region, latency, availability, privacy, and integrations.
• Architecture covers device/edge, ingestion, data/analytics, operations, and governance.
• Service choices include rationale and trade-offs.
• Security, reliability, data lifecycle, cost, and operational ownership are documented.
• The plan includes pilot, multi-domain, and city-scale phases with exit criteria and KPIs.

References

• Azure IoT Edge documentation