skill

telemetry

Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of power-automate telemetry / usage data. Triggers: "disable telemetry", "turn off tel

microsoft/power-platform-skills/plugins/power-automate/skills/telemetryofficiallistedunreviewed

Use skill

Set up

Skills are installed by placing their folder where your agent loads skills.

Download ZIP from GitHub Open the skill folder

The download comes from github.com/microsoft/power-platform-skills itself, not from our server, so what you get is exactly what its author published. The ZIP holds the whole collection; take the folder plugins/power-automate/skills/telemetry out of it for telemetry.

Part of the collection microsoft/power-platform-skills.

npx skills add microsoft/power-platform-skills --skill telemetry

Or by hand: Copy the folder plugins/power-automate/skills/telemetry from github.com/microsoft/power-platform-skills into ~/.claude/skills/telemetry/ (Claude Code) or your agent's skills folder. Check the collection's own README for other agents.

README

synced Oct 14, 2026

Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of power-automate telemetry / usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".

Power Automate Telemetry Control

Enable, disable, or check the status of pseudonymous usage telemetry for the power-automate plugin.

What is collected

Telemetry is pseudonymous. It records operational fields — skill name, plugin version, OS/Node versions, agent name/version, Dataverse organization and Entra tenant IDs, and the signed-in user's Entra object ID when PAC exposes it. It never includes file paths, prompts, tool inputs, flow names, URLs, credentials, usernames, hostnames, or error messages. Plugin hook events have a local diagnostic log, one file per session, under ~/.power-platform-skills/telemetry/power-automate/sessions/<sessionId>/events.jsonl (nothing is transmitted when telemetry is OFF). Session logs older than 14 days are pruned automatically. This hook log is separate from FlowAgent CLI/MCP telemetry, whose local mirror is ~/.flowagent/telemetry.jsonl by default (FLOWAGENT_TELEMETRY_LOG overrides the path) and is not automatically pruned. The status command below reports the plugin hook's setting and session logs; it also prints the core log's path and whether the file exists, not whether a particular CLI/MCP call is eligible for remote collection.

Workflow

Determine the action from the user's request / $ARGUMENTS:
- on — opt in
- off — opt out (nothing transmitted; local log still kept)
- status (default) — report current state

Run the bundled config CLI and show its output verbatim:

node "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/scripts/lib/telemetry/lib/telemetry-config.js" --action <on|off|status> --plugin power-automate

For status, also show the FlowAgent CLI/MCP local log location:

node -e 'const fs = require("node:fs"); const os = require("node:os"); const path = require("node:path"); const log = process.env.FLOWAGENT_TELEMETRY_LOG || path.join(os.homedir(), ".flowagent", "telemetry.jsonl"); console.log(`FlowAgent CLI/MCP local log: ${log}${fs.existsSync(log) ? "" : " (not created yet)"}`);'

Confirm the result to the user in one sentence.