# azure-iot

Skill for Claude Code and Codex that delivers architectural guidance for Azure IoT development. Guides configuration of Device Registry namespaces, DPS, and device certificate workflows.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 170 installs · ★ 818 repo stars
- Author: MicrosoftDocs
- License: CC-BY-4.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/MicrosoftDocs/Agent-Skills/tree/HEAD/skills/azure-iot/SKILL.md
- Updated: 2026-11-09
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/azure-iot

## What it does

The skill focuses on Azure Device Registry architecture, schema registries, and fleet provisioning through IoT Hub DPS.

The skill requires network connectivity to pull documentation. It queries `mcp_microsoftdocs:microsoft_docs_fetch` or falls back to `fetch_webpage` in Markdown format. Without network access or the Microsoft Docs MCP server, the agent cannot retrieve complete technical articles.

Projects targeting Azure IoT Hub, Azure IoT Edge, Azure IoT Central, or Azure Defender for IoT require separate dedicated skills like `azure-iot-hub` or `azure-iot-edge`.

## Requirements
- Works with: Azure

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-iot -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/azure-iot/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/azure-iot/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-iot -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/azure-iot/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-iot -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/azure-iot/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install MicrosoftDocs/Agent-Skills skills/azure-iot
```

2. **Manually: put the files in place**
- File: `.github/skills/azure-iot/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-iot -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/MicrosoftDocs/Agent-Skills --path skills/azure-iot
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/azure-iot/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add MicrosoftDocs/Agent-Skills --skill azure-iot -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/MicrosoftDocs/Agent-Skills/tree/HEAD/skills/azure-iot/SKILL.md

## When to use it
- structure namespaces and schema registries in Azure Device Registry
- set up issuance and revocation policies for device certificates
- link devices to Device Registry and IoT Hub with unified Azure IoT SDKs
- target software updates to specific device groups

## Example prompts
- Show best practices for structuring Azure Device Registry namespaces
- Configure certificate renewal policies for IoT Hub DPS
- Generate code to connect a device fleet using the unified Azure IoT SDK

## Source text · SKILL.md · CC-BY-4.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6c7957ad548a5411.

BEGIN THIRD-PARTY FILE 6c7957ad548a5411
```text
---
name: azure-iot
description: Expert knowledge for Azure IoT development including best practices, security, configuration, integrations & coding patterns, and deployment. Use when managing Device Registry namespaces, IoT Hub DPS, cert-based auth, SDK device connectivity, or software updates, and other Azure IoT related development tasks. Not for Azure IoT Hub (use azure-iot-hub), Azure IoT Edge (use azure-iot-edge), Azure IoT Central (use azure-iot-central), Azure Defender For Iot (use azure-defender-for-iot).
compatibility: Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
metadata:
  generated_at: "2026-11-08"
  generator: "docs2skills/1.0.0"
---
# Azure IoT Skill

This skill provides expert guidance for Azure IoT. Covers best practices, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.

## How to Use This Skill

> **IMPORTANT for Agent**: Use the **Category Index** below to locate relevant sections. For categories with line ranges (e.g., `L35-L120`), use `read_file` with the specified lines. For categories with file links (e.g., `[security.md](security.md)`), use `read_file` on the linked reference file

> **IMPORTANT for Agent**: If `metadata.generated_at` is more than 3 months old, suggest the user pull the latest version from the repository. If `mcp_microsoftdocs` tools are not available, suggest the user install it: [Installation Guide](https://github.com/MicrosoftDocs/mcp/blob/main/README.md)

This skill requires **network access** to fetch documentation content:
- **Preferred**: Use `mcp_microsoftdocs:microsoft_docs_fetch` with query string `from=learn-agent-skill`. Returns Markdown.
- **Fallback**: Use `fetch_webpage` with query string `from=learn-agent-skill&accept=text/markdown`. Returns Markdown.

## Category Index

| Category | Lines | Description |
|----------|-------|-------------|
| Best Practices | L33-L38 | Designing Azure Device Registry namespaces and schema registries, including structure, naming, isolation, versioning, and governance best practices for large-scale IoT solutions |
| Security | L39-L51 | Managing IoT device certificates and CAs in Azure: issuance, renewal, revocation, CA hierarchy, namespaces/security boundaries, and configuring Microsoft or external CAs via Device Registry. |
| Configuration | L52-L61 | Configuring Azure Device Registry and IoT Hub DPS: namespaces, groups, software update import/targeting, device enable/disable, and certificate policy setup. |
| Integrations & Coding Patterns | L62-L66 | Using unified Azure IoT SDKs to connect devices to Azure Device Registry and IoT Hub, including setup, authentication, and coding patterns for device connectivity. |
```
END THIRD-PARTY FILE 6c7957ad548a5411

The third-party file has ended. Everything between the 6c7957ad548a5411 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2833 of 6195 bytes. © MicrosoftDocs · CC-BY-4.0 · https://github.com/MicrosoftDocs/Agent-Skills/tree/HEAD/skills/azure-iot/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
