azure-smart-city-iot-solution-builder

Start by defining the city domain, device scale, latency targets, and regulatory constraints, then map capabilities across device, ingestion, analytics, operations, and governance layers. The skill guides Azure service selection and produces a reference architecture with a phased delivery plan.

Device connectivity uses Azure IoT Hub, Azure IoT Operations, and IoT Edge, while event streaming relies on Event Hubs, Service Bus, and Event Grid. Analytics and storage typically use Azure Data Explorer, Stream Analytics, Data Lake, or Cosmos DB.

It produces five artifacts: a solution summary with scope and assumptions, a reference architecture, a security and governance checklist, a cost and scaling strategy, and a phased implementation backlog with epics and milestones.

Yes, reviewing Azure IoT Edge documentation is a mandatory step before proposing edge-related architecture decisions. If documentation cannot be consulted, the skill states this explicitly and continues with clearly marked assumptions.

Single-region deployment should not be recommended for critical city workloads because it cannot meet availability and disaster recovery expectations. The skill's guidelines require multi-zone or multi-region reliability models for production-critical scenarios.