Agent skill

Intune Device Mgmt

by vinayaklatthe in vinayaklatthe/microsoft-security-skills

Guidance for Microsoft Intune device management — enrollment, configuration, compliance, and security baselines across Windows, macOS, iOS/iPadOS, and Android.

MITAuto-check passedLegal & Compliance

Install Intune Device Mgmt

skills CLI
$ npx skills add vinayaklatthe/microsoft-security-skills --skill intune-device-mgmt -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vinayaklatthe/microsoft-security-skills intune-device-mgmt --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/intune-device-mgmt .claude/skills/intune-device-mgmt && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
intune-device-mgmt
GitHub stars
175
Token cost
~1.8k tokens
SKILL.md length
738 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Guidance for Microsoft Intune device management — enrollment, configuration, compliance, and security baselines across Windows, macOS, iOS/iPadOS, and Android.

  • Works in 7 steps: Enrollment — Configure platform-specific… → Configuration profiles — Use the… → Compliance policies feed Conditional… → …
  • App-only protection on BYOD (use intune-app-protection)
  • SKILL.md covers When to use, Pick the enrollment method by…, Approach and Guardrails, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Intune Device Mgmt is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Intune device management — enrollment, configuration, compliance, and security baselines across Windows, macOS, iOS/iPadOS, and Android. Covers Autopilot vs corporate-vs-BYOD enrollment, compliance policies that feed Conditional Access, Intune security baselines, update rings / Autopatch, and using filters and ring-based rollouts to avoid lockouts. WHEN: Microsoft Intune, MDM, device enrollment, Autopilot, Apple ABM, Android Enterprise, compliance policy, security baseline, configuration…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Legal & Compliance, covering Regulatory compliance. It works with iOS, Android, macOS and Microsoft Defender. The repository describes itself as: Curated Microsoft Security skills for AI agents - Defender, Sentinel, Entra, Purview, Intune, Security Copilot. The licence is MIT.

When your agent uses it

  • App-only protection on BYOD (use intune-app-protection)
  • Endpoint detection / EDR (use defender-for-endpoint)
  • Disk encryption only (use bitlocker-design)

Example prompts

  • “/intune-device-mgmt”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Enrollment — Configure platform-specific enrollment (Autopilot deployment profiles,
  2. Configuration profiles — Use the settings catalog (not legacy templates). Deploy
  3. Compliance policies feed Conditional Access — Define compliance per platform
  4. Apply security baselines — Start from Intune security baselines (Windows, Defender
  5. Rollout with rings and filters — Pilot ring (5%) → fast ring (20%) → broad ring (75%).
  6. Updates — Windows: Autopatch or update rings. iOS/macOS: managed software updates.
  7. Monitor + remediate — Encryption / compliance / configuration reports daily. Drift on

What it can do on your machine

Read from SKILL.md and the folder at commit 15f16df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • learn.microsoft.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Intune Device Mgmt loads about 1.8k tokens when it runs. Until then it costs about 212 tokens; SKILL.md has 738 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~212
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vinayaklatthe/microsoft-security-skills at commit 15f16df, republished under its MIT licence (© vinayaklatthe). 738 words, ~1,810 tokens.

Download SKILL.mdSave it as .claude/skills/intune-device-mgmt/SKILL.md (or your agent's skills folder).
name
intune-device-mgmt
description
Guidance for Microsoft Intune device management — enrollment, configuration, compliance, and security baselines across Windows, macOS, iOS/iPadOS, and Android. Covers Autopilot vs corporate-vs-BYOD enrollment, compliance policies that feed Conditional Access, Intune security baselines, update rings / Autopatch, and using filters and ring-based rollouts to avoid lockouts. WHEN: Microsoft Intune, MDM, device enrollment, Autopilot, Apple ABM, Android Enterprise, compliance policy, security baseline, configuration profile, settings catalog, manage devices, device compliance for Conditional Access, endpoint management, Windows Autopatch, update rings. DO NOT USE for app-only protection on BYOD (use intune-app-protection), endpoint detection / EDR (use defender-for-endpoint), or disk encryption only (use bitlocker-design).
license
MIT
metadata.author
Microsoft
metadata.version
0.1.0

Microsoft Intune - Device Management

Microsoft Intune is the cloud-based endpoint management service for enrolling, configuring, securing, and monitoring devices across Windows, macOS, iOS/iPadOS, Android, and Linux. It is the source of device compliance signal that Conditional Access uses for access decisions.

When to use

Managing corporate and BYOD device fleets and producing the compliance signal Conditional Access depends on. Use this skill to plan enrollment, compliance, baselines, and rollout rings.

Do not use this skill for app-only protection on personal devices (intune-app-protection), EDR (defender-for-endpoint), or disk encryption (bitlocker-design).

Pick the enrollment method by platform and ownership

PlatformCorporate-ownedPersonal (BYOD)
WindowsAutopilot + Entra join (pre-provisioned or user-driven)Entra registration + MAM or co-managed
macOSApple Business Manager (ABM) + ADE enrollmentUser-enrolled (limited management)
iOS/iPadOSABM + ADE supervisedUser enrollment (account-driven preferred)
AndroidAndroid Enterprise fully managed (corporate)Android Enterprise work profile

Rule of thumb: if the device is corporate-owned, full MDM via Autopilot / ABM / Android Enterprise fully managed. If personal, prefer work profile (Android) or user enrollment (iOS) for clean separation of corporate and personal data. Never enroll personal devices into full MDM - users push back and you carry liability for personal data.

Approach

  1. Enrollment — Configure platform-specific enrollment (Autopilot deployment profiles, ABM token + ADE profiles, Android Enterprise binding). Block personal-platform enrollment for corporate users if that's the policy (enrollment restrictions). Verify: an Autopilot device hits the Out-of-Box Experience and lands joined + Intune- enrolled in one pass without IT touch.

  2. Configuration profiles — Use the settings catalog (not legacy templates). Deploy Wi-Fi / VPN / certificate profiles, OS hardening, browser policies. One profile per purpose; don't bundle unrelated settings.

  3. Compliance policies feed Conditional Access — Define compliance per platform: encryption, OS version, secure boot, Defender signals, jailbreak/root detection. The compliance status drives CA grant control "Require device to be marked as compliant". Verify: a non-compliant device is blocked by CA What If; a compliant one is allowed.

  4. Apply security baselines — Start from Intune security baselines (Windows, Defender for Endpoint, Edge). They're a hardened starting point - then tune deltas. Don't author security settings from scratch. Verify: baseline applied and reported as compliant on the pilot ring; deltas documented.

  5. Rollout with rings and filters — Pilot ring (5%) → fast ring (20%) → broad ring (75%). Use filters to target policies precisely across device types (e.g. only Windows 11, only corporate-owned). Verify: policy reports show staged rollout; pilot ring 2 weeks ahead of broad.

  6. Updates — Windows: Autopatch or update rings. iOS/macOS: managed software updates. Plan update deferral per ring; don't push the same day Microsoft releases.

  7. Monitor + remediate — Encryption / compliance / configuration reports daily. Drift on compliance is a CA-blocking event - act fast.

Show full SKILL.md (300 more words)Show less

Guardrails

  • Pilot configuration and compliance with rings; avoid org-wide day-one enforcement. A bad compliance policy at org scale locks everyone out of email by lunchtime.
  • Set a compliance grace period and clear user remediation guidance to avoid lockouts. 24-72 hour grace; tell users what to fix and where.
  • Use filters to target policies precisely across device types. A Windows-only policy hitting iOS reports failures forever.
  • Enrollment restrictions matter. Allow only the platforms / ownership types you actually manage; otherwise users self-enroll personal devices and you inherit them.
  • Baseline first, custom settings second. Custom-from-scratch security policies drift from Microsoft guidance immediately.
  • Don't put Defender for Endpoint EDR onboarding in a config profile. Use the Defender endpoint security policy or MDE integration path.

Common anti-patterns

  • "Enable compliance policies tenant-wide on Day 1" - Day 2 lockout incident.
  • "All settings in one giant Windows configuration profile" - Unmaintainable; one setting failure marks the whole profile as failed.
  • "Compliance policy with no grace period" - Single network blip = user blocked. Grace period required.
  • "Enroll iPhones into full MDM for BYOD" - User outrage; data-protection exposure. User enrollment instead.
  • "Skip security baselines, write our own" - Slower, less secure, immediately outdated.
  • "No filters - target all devices" - macOS and iOS reports failures on Windows-only policies and vice versa. Targeted with filters.

Example prompts

  • Plan device enrollment with Autopilot for Windows and ABM for macOS.
  • Create compliance policies for Windows, iOS, and Android that feed Conditional Access.
  • Apply Intune security baselines and tune deltas for our environment.
  • Set up update rings with Windows Autopatch and a pilot-fast-broad cadence.
  • Use filters to scope an iOS-only configuration profile.
  • Roll out a new compliance policy with grace period and ring strategy.

Microsoft Learn

© vinayaklatthe, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/intune-device-mgmt of vinayaklatthe/microsoft-security-skills.

Open the folder on GitHubat commit 15f16df

Compare with similar skills

Intune Device Mgmt next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Intune Device Mgmt compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Intune Device Mgmt this skillvinayaklatthe/microsoft-security-skills175—~1.8kAutomated safety check: PassMIT
Engine Whats Newflutter/flutter180k—~978Automated safety check: PassBSD-3-Clause
App Store Screenshots GeneratorParthJadhav/app-store-screenshots7.2k—~16kAutomated safety check: PassMIT
Cindy Skill Creatormakecindy/cindy3k—~4.2kAutomated safety check: PassApache-2.0
Phoneagentrounak/PhoneAgent800—~2.2kAutomated safety check: PassMIT
Brigade Node Connection Diagnosticsspinabot/brigade11k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Engine Whats New

    flutter/flutter

    Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44).

    180k GitHub stars~978 tokensUpdated today
    MobileAuto-check passed
  • App Store Screenshots Generator

    ParthJadhav/app-store-screenshots

    Scaffolds a Next.js editor for designing App Store and Google Play screenshots as ads and exporting them at every required size, for iOS, Mac and Android.

    7.2k GitHub stars~16k tokensUpdated yesterday
    MobileAuto-check passed
  • Cindy Skill Creator

    makecindy/cindy

    Create or edit a Cindy Skill, search the SkillHub public marketplace or your organization's Skills, upload your own Skill, or publish a new version of a Skill you authored.

    3k GitHub stars~4.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Phoneagent

    rounak/PhoneAgent

    Control a connected iPhone, iOS simulator, Android emulator, or Android device from macOS through PhoneAgent's JSON-RPC bridge.

    800 GitHub stars~2.2k tokensUpdated 1 mo ago
    MobileAuto-check passed
  • Diagnoses why a Brigade companion app can't pair or connect, by first identifying the real node-to-gateway route and then fixing auth.

    11k GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Kane CLI Browser Testing

    LambdaTest/kane-cli

    Drives a real browser through the kane-cli tool and designs requirement-linked test suites from a PRD or a plain description, with mobile and cloud-grid runs.

    249 GitHub stars~8.4k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from vinayaklatthe/microsoft-security-skills

All 50 skills in this repo
  • API Security Design

    vinayaklatthe/microsoft-security-skills

    Guidance for designing secure APIs on Azure - authentication, authorization, gateway controls, input validation, rate limiting, secret management, and runtime threat detection - aligned to OWASP API…

    175 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure App Service Security

    vinayaklatthe/microsoft-security-skills

    Guidance for securing Azure App Service web apps and APIs — managed identity, Easy Auth with Microsoft Entra ID, network isolation via private endpoints + VNet integration, HTTPS / TLS hardening…

    175 GitHub stars~1.9k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Arc

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure Arc — projecting on-premises, multicloud (AWS/GCP), and edge servers, Kubernetes, and data services into Azure Resource Manager for unified governance, security, and management.

    175 GitHub stars~1.9k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Bastion Jit

    vinayaklatthe/microsoft-security-skills

    Guidance for secure remote VM management in Azure using Azure Bastion combined with Defender for Cloud just-in-time (JIT) VM access.

    175 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Confidential Computing

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure Confidential Computing — protecting data in use through hardware-based Trusted Execution Environments (TEEs).

    175 GitHub stars~2.4k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Ddos Protection

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure DDoS Protection — Network Protection (per-VNet) and IP Protection (per public IP) tiers built on the same always-on Microsoft platform.

    175 GitHub stars~2k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Intune Device Mgmt

What does Intune Device Mgmt do?

Guidance for Microsoft Intune device management — enrollment, configuration, compliance, and security baselines across Windows, macOS, iOS/iPadOS, and Android. Intune Device Mgmt is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Intune device management — enrollment, configuration, compliance, and security baselines across Windows, macOS, iOS/iPadOS, and Android.

When should I use Intune Device Mgmt?

Intune Device Mgmt fits situations like: app-only protection on BYOD (use intune-app-protection); endpoint detection / EDR (use defender-for-endpoint); disk encryption only (use bitlocker-design).

How do I install Intune Device Mgmt in Claude Code?

Run `npx skills add vinayaklatthe/microsoft-security-skills --skill intune-device-mgmt -a claude-code`. Or copy the skill folder (skills/intune-device-mgmt in vinayaklatthe/microsoft-security-skills) into .claude/skills/intune-device-mgmt in your project. Claude Code loads it when a task matches its description.

How do I install Intune Device Mgmt in Codex?

Run `npx skills add vinayaklatthe/microsoft-security-skills --skill intune-device-mgmt -a codex`. Or copy the skill folder (skills/intune-device-mgmt in vinayaklatthe/microsoft-security-skills) into .agents/skills/intune-device-mgmt in your project. Codex loads it when a task matches its description.

Can I use Intune Device Mgmt in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vinayaklatthe/microsoft-security-skills --skill intune-device-mgmt -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/intune-device-mgmt, .gemini/skills/intune-device-mgmt, .github/skills/intune-device-mgmt and .opencode/skills/intune-device-mgmt in your project.

What does Intune Device Mgmt need to run?

SKILL.md names no scripts, command-line tools or credentials: Intune Device Mgmt is instructions for the agent only.

Does Intune Device Mgmt access the network?

SKILL.md names 1 domain. As links in the text: learn.microsoft.com. This is read from the text; nothing was executed.

Is Intune Device Mgmt safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Intune Device Mgmt use?

Intune Device Mgmt is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Intune Device Mgmt use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Intune Device Mgmt?

Skills that share tags, products or a category with Intune Device Mgmt: Engine Whats New (flutter/flutter, 180k stars), App Store Screenshots Generator (ParthJadhav/app-store-screenshots, 7.2k stars), Cindy Skill Creator (makecindy/cindy, 3k stars) and Phoneagent (rounak/PhoneAgent, 800 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Intune Device Mgmt?

vinayaklatthe (a GitHub user) maintains it in vinayaklatthe/microsoft-security-skills, which has 175 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on June 18, 2026.

Source: vinayaklatthe/microsoft-security-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.