Entra Agent User
github/awesome-copilot
Create Agent Users in Microsoft Entra ID from Agent Identities, enabling AI agents to act as digital workers with user identity capabilities in Microsoft 365 and Azure environments.
Write PowerShell scripts using CLI for Microsoft 365 commands to automate Microsoft 365 management tasks.
$ npx skills add pnp/cli-microsoft365-mcp-server --skill cli-microsoft365-script -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pnp/cli-microsoft365-mcp-server cli-microsoft365-script --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pnp/cli-microsoft365-mcp-server.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/cli-microsoft365-script .claude/skills/cli-microsoft365-script && rm -rf skills-srcUse ~/.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/
Install the "cli-microsoft365-script" agent skill from https://github.com/pnp/cli-microsoft365-mcp-server/tree/main/.github/skills/cli-microsoft365-script into .claude/skills/cli-microsoft365-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-microsoft365-script", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pnp/cli-microsoft365-mcp-server/tree/main/.github/skills/cli-microsoft365-scriptType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pnp/cli-microsoft365-mcp-server --skill cli-microsoft365-script -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pnp/cli-microsoft365-mcp-server cli-microsoft365-script --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/cli-microsoft365-mcp-server.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/cli-microsoft365-script .agents/skills/cli-microsoft365-script && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cli-microsoft365-script" agent skill from https://github.com/pnp/cli-microsoft365-mcp-server/tree/main/.github/skills/cli-microsoft365-script into .agents/skills/cli-microsoft365-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-microsoft365-script", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pnp/cli-microsoft365-mcp-server --skill cli-microsoft365-script -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pnp/cli-microsoft365-mcp-server cli-microsoft365-script --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/cli-microsoft365-mcp-server.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/cli-microsoft365-script .cursor/skills/cli-microsoft365-script && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cli-microsoft365-script" agent skill from https://github.com/pnp/cli-microsoft365-mcp-server/tree/main/.github/skills/cli-microsoft365-script into .cursor/skills/cli-microsoft365-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-microsoft365-script", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pnp/cli-microsoft365-mcp-server.git --path .github/skills/cli-microsoft365-script--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pnp/cli-microsoft365-mcp-server --skill cli-microsoft365-script -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pnp/cli-microsoft365-mcp-server cli-microsoft365-script --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/cli-microsoft365-mcp-server.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/cli-microsoft365-script .gemini/skills/cli-microsoft365-script && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cli-microsoft365-script" agent skill from https://github.com/pnp/cli-microsoft365-mcp-server/tree/main/.github/skills/cli-microsoft365-script into .gemini/skills/cli-microsoft365-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-microsoft365-script", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pnp/cli-microsoft365-mcp-server cli-microsoft365-scriptInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pnp/cli-microsoft365-mcp-server --skill cli-microsoft365-script -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pnp/cli-microsoft365-mcp-server.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/cli-microsoft365-script .github/skills/cli-microsoft365-script && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cli-microsoft365-script" agent skill from https://github.com/pnp/cli-microsoft365-mcp-server/tree/main/.github/skills/cli-microsoft365-script into .github/skills/cli-microsoft365-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-microsoft365-script", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pnp/cli-microsoft365-mcp-server --skill cli-microsoft365-script -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pnp/cli-microsoft365-mcp-server cli-microsoft365-script --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/cli-microsoft365-mcp-server.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/cli-microsoft365-script .opencode/skills/cli-microsoft365-script && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cli-microsoft365-script" agent skill from https://github.com/pnp/cli-microsoft365-mcp-server/tree/main/.github/skills/cli-microsoft365-script into .opencode/skills/cli-microsoft365-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-microsoft365-script", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cli-microsoft365-scriptWrite PowerShell scripts using CLI for Microsoft 365 commands to automate Microsoft 365 management tasks.
CLI Microsoft365 Script is an agent skill from pnp/cli-microsoft365-mcp-server. Write PowerShell scripts using CLI for Microsoft 365 commands to automate Microsoft 365 management tasks. Use when: writing PowerShell scripts that use m365 commands, automating SharePoint Online provisioning, automating Entra ID user/group management, automating Teams setup, batch operations on Microsoft 365 resources, CI/CD scripts for Microsoft 365, error handling for m365 commands in PowerShell.
Its SKILL.md is about 3.3k 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 Documents & Office, covering Cloud office suites and Shell scripting. It works with Microsoft 365, PowerShell, Microsoft Entra ID and Microsoft SharePoint. The repository describes itself as: Manage Microsoft 365 using MCP server. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 6d89707. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are powershell).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
contoso.sharepoint.comgraph.microsoft.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
CERT_PASSWORDCLIENT_SECRETFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
CLI Microsoft365 Script loads about 3.3k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 624 words of instructions outside code blocks.
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.
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.
The full file from pnp/cli-microsoft365-mcp-server at commit 6d89707, republished under its MIT licence (© pnp). 624 words, ~3,336 tokens.
.claude/skills/cli-microsoft365-script/SKILL.md (or your agent's skills folder).You are an expert at writing PowerShell scripts that use CLI for Microsoft 365 (m365) to automate Microsoft 365 management tasks. Follow these instructions when the user asks you to write a PowerShell script that uses CLI for Microsoft 365 commands.
Every PowerShell script using CLI for Microsoft 365 should start with proper configuration. Use this template as a starting point:
#!/usr/bin/env pwsh
$ErrorActionPreference = "Stop"
# Configure CLI for scripting
m365 cli config set --key "output" --value "json"
m365 cli config set --key "errorOutput" --value "stdout"
m365 cli config set --key "showHelpOnFailure" --value "false"
m365 cli config set --key "printErrorsAsPlainText" --value "false"
m365 cli config set --key "prompt" --value "false"
$env:CLIMICROSOFT365_NOUPDATE = "1"
# Ensure authentication
m365 login --ensure| Setting | Value | Purpose |
|---|---|---|
output | json | Structured data for reliable parsing |
errorOutput | stdout | Allows PowerShell to capture errors in variables |
showHelpOnFailure | false | Prevents help text from polluting output |
printErrorsAsPlainText | false | Returns errors as JSON for structured handling |
prompt | false | Prevents interactive prompts that block automation |
The $env:CLIMICROSOFT365_NOUPDATE = "1" environment variable disables update checks to avoid delays in automated scripts.
Always use m365 login --ensure at the start of every script. This command checks if you are already authenticated and only prompts for login if necessary:
m365 login --ensureFor unattended scripts, use certificate-based or secret-based authentication:
# Certificate-based (recommended for CI/CD)
m365 login --authType certificate --certificateFile "C:\certs\app.pfx" --password $env:CERT_PASSWORD
# Client secret
m365 login --authType secret --secret $env:CLIENT_SECRET
# Managed identity (Azure-hosted only)
m365 login --authType identityNever hardcode credentials or secrets in scripts. Use environment variables or secure stores instead.
Set these environment variables to avoid passing --appId and --tenant on every login:
$env:CLIMICROSOFT365_ENTRAAPPID = "<app-id>"
$env:CLIMICROSOFT365_TENANT = "<tenant-id>"The simplest approach — run the command and check $LASTEXITCODE:
$siteData = m365 spo site get --url "https://contoso.sharepoint.com/sites/project"
if ($LASTEXITCODE -ne 0) {
Write-Error "Failed to retrieve site"
exit 1
}
$site = $siteData | ConvertFrom-Json
Write-Host "Site: $($site.Title)"For detailed error handling, use the Invoke-CLICommand helper function. This requires the CLI configuration from the Script Setup section above (especially errorOutput set to stdout and printErrorsAsPlainText set to false):
function Invoke-CLICommand {
[CmdletBinding()]
param(
[parameter(Mandatory = $true, ValueFromPipeline = $true)] $input
)
$output = $input
if ($null -eq $output) {
return $null
}
$parsedOutput = $output | ConvertFrom-Json
if ($parsedOutput -isnot [Array] -and $null -ne $parsedOutput.error) {
throw $parsedOutput.error
}
return $parsedOutput
}Usage with try/catch:
try {
$site = m365 spo site get --url "https://contoso.sharepoint.com/sites/project" | Invoke-CLICommand
Write-Host "Site: $($site.Title)"
}
catch {
Write-Error "Failed: $($_.Exception.Message)"
exit 1
}Set --output json (or configure it globally) and parse with ConvertFrom-Json:
$sites = m365 spo site list --output json | ConvertFrom-Json
foreach ($site in $sites) {
Write-Host "Site: $($site.Url) - $($site.Title)"
}When using the Invoke-CLICommand helper, output is already parsed:
$sites = m365 spo site list | Invoke-CLICommand
foreach ($site in $sites) {
Write-Host "Site: $($site.Url) - $($site.Title)"
}m365 spo site list --output csv > sites.csvUse --output none when you do not need the response:
m365 spo site remove --url "https://contoso.sharepoint.com/sites/old" --force --output noneUse the --query option for server-side filtering instead of piping to Where-Object:
# Good — filter with JMESPath
$projectSites = m365 spo site list --query "[?contains(Title, 'Project')]" | Invoke-CLICommand
# Less efficient — filter in PowerShell after fetching everything
$allSites = m365 spo site list | Invoke-CLICommand
$projectSites = $allSites | Where-Object { $_.Title -like "*Project*" } # Select specific fields
m365 spo site list --query "[*].{Title: Title, Url: Url}"
# Filter and project
m365 spo site list --query "[?contains(Title, 'Project')].{Title: Title, Url: Url}"
# Get a single value
m365 entra user get --id "user@contoso.com" --query "id" --output textJMESPath queries are case-sensitive.
@ characterIn PowerShell, @ is a special character. When using the CLI file reference syntax or tokens like @meId, escape with a backtick:
# File reference
m365 spo sitescript add --title "Script" --content `@script.json
# User tokens
m365 entra user get --id "`@meId"Use = to pass values that start with a dash:
m365 planner task get --id=-9rMKQooUjZdxgv1qQVZYABEuwStore complex JSON in files rather than inline strings:
$payload = @{
displayName = "Project Team"
description = "Team for the project"
} | ConvertTo-Json -Depth 10
$payload | Out-File -FilePath "payload.json" -Encoding utf8
m365 request --url "`@graph/teams" --method post --body `@payload.jsonIn PowerShell, you can use $true / $false, or the CLI accepted values: 1, yes, true, on / 0, no, false, off.
try {
$list = m365 spo list get --webUrl $webUrl --title $listTitle | Invoke-CLICommand
Write-Host "List '$($list.Title)' already exists"
}
catch {
Write-Host "List not found, creating..."
m365 spo list add --webUrl $webUrl --title $listTitle --baseTemplate GenericList | Invoke-CLICommand
Write-Host "List '$listTitle' created"
}$users = @("user1@contoso.com", "user2@contoso.com", "user3@contoso.com")
$webUrl = "https://contoso.sharepoint.com/sites/project"
$succeeded = 0
$failed = 0
foreach ($user in $users) {
try {
m365 spo user add --webUrl $webUrl --loginName $user | Invoke-CLICommand
Write-Host "Added: $user" -ForegroundColor Green
$succeeded++
}
catch {
Write-Host "Failed: $user — $($_.Exception.Message)" -ForegroundColor Red
$failed++
}
}
Write-Host "`nCompleted. Succeeded: $succeeded, Failed: $failed"# Get all team IDs and archive each team
$teams = m365 teams team list --query "[?contains(displayName, 'Old')]" | Invoke-CLICommand
foreach ($team in $teams) {
m365 teams team archive --id $team.id
Write-Host "Archived: $($team.displayName)"
}$usersToCreate = Import-Csv -Path "users.csv"
foreach ($user in $usersToCreate) {
try {
m365 entra user add `
--displayName $user.DisplayName `
--userName $user.UserPrincipalName `
--password $user.Password `
--accountEnabled $true | Invoke-CLICommand
Write-Host "Created user: $($user.DisplayName)" -ForegroundColor Green
}
catch {
Write-Host "Failed to create $($user.DisplayName): $($_.Exception.Message)" -ForegroundColor Red
}
} # Set up context for repeated operations on the same site
m365 context init
m365 context option set --name "webUrl" --value "https://contoso.sharepoint.com/sites/project"
# Commands now pick up --webUrl automatically
$lists = m365 spo list list | Invoke-CLICommand
$items = m365 spo listitem list --listTitle "Tasks" | Invoke-CLICommandAfter running any spo command or setting the SPO URL explicitly, you can use server-relative URLs:
m365 spo set --url "https://contoso.sharepoint.com"
# Now use server-relative URLs
$site = m365 spo site get --url "/sites/project" | Invoke-CLICommandThese built-in tokens resolve to the currently authenticated user:
$me = m365 entra user get --id "`@meId" | Invoke-CLICommand
Write-Host "Logged in as: $($me.displayName)"Use m365 request to call any Microsoft API not covered by specific commands:
# GET request with URL tokens
$profile = m365 request --url "`@graph/me" | Invoke-CLICommand
# POST with inline body
m365 request --url "`@graph/me/messages" --method post --body '{"subject":"Test","body":{"content":"Hello"}}'
# POST with body from file
m365 request --url "`@graph/teams" --method post --body `@team-payload.jsonURL tokens:
@graph → https://graph.microsoft.com/v1.0@graphbeta → https://graph.microsoft.com/beta@spo → Current SharePoint URL (set via m365 spo set)For development and troubleshooting:
m365 spo site get --url "https://contoso.sharepoint.com/sites/project" --verboseOr set via environment variable for all commands:
$env:CLIMICROSOFT365_VERBOSE = "1"Shows full HTTP request and response details:
$env:CLIMICROSOFT365_DEBUG = "1"--output none when possible for write operations#!/usr/bin/env pwsh
<#
.SYNOPSIS
Description of what this script does.
.DESCRIPTION
Detailed description.
.EXAMPLE
.\Script.ps1 -SiteUrl "https://contoso.sharepoint.com/sites/project"
#>
param(
[Parameter(Mandatory = $true)]
[string]$SiteUrl
)
$ErrorActionPreference = "Stop"
# --- CLI Configuration ---
m365 cli config set --key "output" --value "json"
m365 cli config set --key "errorOutput" --value "stdout"
m365 cli config set --key "showHelpOnFailure" --value "false"
m365 cli config set --key "printErrorsAsPlainText" --value "false"
m365 cli config set --key "prompt" --value "false"
$env:CLIMICROSOFT365_NOUPDATE = "1"
# --- Helper Function ---
function Invoke-CLICommand {
[CmdletBinding()]
param(
[parameter(Mandatory = $true, ValueFromPipeline = $true)] $input
)
$output = $input
if ($null -eq $output) { return $null }
$parsedOutput = $output | ConvertFrom-Json
if ($parsedOutput -isnot [Array] -and $null -ne $parsedOutput.error) {
throw $parsedOutput.error
}
return $parsedOutput
}
# --- Authentication ---
m365 login --ensure
# --- Script Logic ---
try {
$site = m365 spo site get --url $SiteUrl | Invoke-CLICommand
Write-Host "Site: $($site.Title)" -ForegroundColor Green
}
catch {
Write-Error "Script failed: $($_.Exception.Message)"
exit 1
}
Write-Host "Script completed successfully" -ForegroundColor Green© pnp, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .github/skills/cli-microsoft365-script of pnp/cli-microsoft365-mcp-server.
Open the folder on GitHubat commit 6d89707
CLI Microsoft365 Script 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CLI Microsoft365 Script this skillpnp/cli-microsoft365-mcp-server | 131 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Entra Agent Usergithub/awesome-copilot | 40k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Ms365 Tenant Managerborghei/Claude-Skills | 874 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Workiqmicrosoft/work-iq | 1k | — | ~15k | Automated safety check: Pass | Custom licence | |
| Ms365 Tenant Manageralirezarezvani/claude-skills | 28k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Msgraph Filesautomateyournetwork/netclaw | 674 | — | ~1k | Automated safety check: Pass | Apache-2.0 |
github/awesome-copilot
Create Agent Users in Microsoft Entra ID from Agent Identities, enabling AI agents to act as digital workers with user identity capabilities in Microsoft 365 and Azure environments.
borghei/Claude-Skills
Microsoft 365 tenant administration for Global Administrators.
microsoft/work-iq
WorkIQ tools for Microsoft 365 workplace data and actions. An agent skill from microsoft/work-iq.
alirezarezvani/claude-skills
Microsoft 365 tenant administration for Global Administrators.
automateyournetwork/netclaw
Read OneDrive and SharePoint files via the Microsoft 365 MCP server — list folder contents, fetch item metadata, inspect versions and sharing permissions.
automateyournetwork/netclaw
Upload and retrieve Visio (.vsdx) and other diagram files in OneDrive/SharePoint via the Microsoft 365 MCP server.
pnp/cli-microsoft365-mcp-server
Use CLI for Microsoft 365 to manage Microsoft 365 tenants from the terminal.
Categories
Write PowerShell scripts using CLI for Microsoft 365 commands to automate Microsoft 365 management tasks. CLI Microsoft365 Script is an agent skill from pnp/cli-microsoft365-mcp-server. Write PowerShell scripts using CLI for Microsoft 365 commands to automate Microsoft 365 management tasks.
CLI Microsoft365 Script fits situations like: : writing PowerShell scripts that use m365 commands; automating SharePoint Online provisioning; automating Entra ID user/group management; automating Teams setup.
Run `npx skills add pnp/cli-microsoft365-mcp-server --skill cli-microsoft365-script -a claude-code`. Or copy the skill folder (.github/skills/cli-microsoft365-script in pnp/cli-microsoft365-mcp-server) into .claude/skills/cli-microsoft365-script in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pnp/cli-microsoft365-mcp-server --skill cli-microsoft365-script -a codex`. Or copy the skill folder (.github/skills/cli-microsoft365-script in pnp/cli-microsoft365-mcp-server) into .agents/skills/cli-microsoft365-script in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pnp/cli-microsoft365-mcp-server --skill cli-microsoft365-script -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cli-microsoft365-script, .gemini/skills/cli-microsoft365-script, .github/skills/cli-microsoft365-script and .opencode/skills/cli-microsoft365-script in your project.
Going by SKILL.md and its folder, CLI Microsoft365 Script needs credentials named CERT_PASSWORD and CLIENT_SECRET. Our summary lists: A credential in CLIENT_SECRET.
SKILL.md names 2 domains. In commands or code: contoso.sharepoint.com and graph.microsoft.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
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.
CLI Microsoft365 Script is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with CLI Microsoft365 Script: Entra Agent User (github/awesome-copilot, 40k stars), Ms365 Tenant Manager (borghei/Claude-Skills, 874 stars), Workiq (microsoft/work-iq, 1k stars) and Ms365 Tenant Manager (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
pnp (a GitHub organization) maintains it in pnp/cli-microsoft365-mcp-server, which has 131 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 5, 2026.
Source: pnp/cli-microsoft365-mcp-server on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.