Agent skill · Security

azure-iot-operations

Expert knowledge for Azure IoT Operations development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when building MQTT data flows, OPC UA integrations, WASM transforms, ONNX edge inference, or ISA‑95 namespaces, and other Azure IoT Operations related development tasks. Not for Azure IoT (use azure-iot), Azure IoT Hub (use azure-iot-hub), Azure IoT Edge (use azure-iot-edge), Azure IoT Central (use azure-iot-central).

MicrosoftDocsgithub.com/MicrosoftDocsGitHub ↗
claude-codecopilotcodexCC-BY-4.0
Install
npx skills add MicrosoftDocs/Agent-Skills --skill azure-iot-operations --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 20 KB
Bundled scripts: none
Requires: Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
Path: skills/azure-iot-operations/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 682 · +8 this week
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Gives expert guidance for Azure IoT Operations across troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.

How it works

The skill instructs the agent to use a Category Index to locate relevant sections. For categories with line ranges, the agent should call read_file with the specified lines. For categories with file links, the agent should call read_file on the linked reference file. It also requires network access to fetch documentation content via mcp_microsoftdocs:microsoft_docs_fetch (preferred) or fetch_webpage (fallback). If the metadata timestamp is older than 3 months, the agent should suggest pulling the latest version. It relies on the tools mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve Markdown documentation and presents content organized under categories such as Troubleshooting, Best Practices, Decision Making, Architecture & Design Patterns, Limits & Quotas, Security, Configuration, Integrations & Coding Patterns, and Deployment.

When to use it

Use when dealing with Azure IoT Operations development tasks related to MQTT data flows, OPC UA integrations, WASM transforms, ONNX edge inference, ISA‑95 namespaces, and related areas. The skill is not intended for Azure IoT Hub, Edge, Central, or the broader Azure IoT family.

What it can touch

Identified tools and interfaces include: "mcp_microsoftdocs:microsoft_docs_fetch" and "fetch_webpage" to retrieve documentation content. The agent should perform reads like "read_file" on section references or linked files as instructed by the Category Index. No other execution or editing capabilities are specified.

Caveats

Requires network access to fetch documentation content. If the preferred tool is unavailable, fallback to fetch_webpage. The skill deploys under CC-BY-4.0 license. Content references external Microsoft Learn documentation, and the metadata indicates generated_at: "2026-08-02". If the timestamp is stale, the agent should suggest refreshing from the repository.

From the SKILL.md

# Azure IoT Operations Skill This skill provides expert guidance for Azure IoT Operations. Covers troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, 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 `fe

What's inside
Steps it walks through
  1. How to Use This Skill
  2. Category Index
  3. Troubleshooting
  4. Best Practices
  5. Decision Making
  6. Architecture & Design Patterns
  7. Limits & Quotas
  8. Security
  9. Configuration
  10. Integrations & Coding Patterns
  11. Deployment
More from Agent-Skills
All skills →
About this skill
What does the azure-iot-operations skill do?

Expert knowledge for Azure IoT Operations development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when building MQTT data flows, OPC UA integrations, WASM transforms, ONNX edge inference, or ISA‑95 namespaces, and other Azure IoT Operations related development tasks. Not for Azure IoT (use azure-iot), Azure IoT Hub (use azure-iot-hub), Azure IoT Edge (use azure-iot-edge), Azure IoT Central (use azure-iot-central).

How do I install it?

Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-iot-operations --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From MicrosoftDocs/Agent-Skills, a repository with 682 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going