Manage Telemetry Settings for Power Platform CLI Code Commands
Manage Telemetry Settings for Power Platform CLI Code Commands
Telemetry in the Power Platform CLI (PAC CLI) helps improve reliability, performance, and usability of CLI code commands.
- PAC CLI code commands collect limited telemetry data
- Telemetry applies only to CLI commands, not runtime app usage
Why Telemetry Is Used
- Track command execution and usage scenarios
- Capture errors and failures for diagnostics
- Measure performance and execution timing
- Understand environment context (non-PII only)
⚠️ Important Note: Telemetry failures never block CLI operations.
Types of Telemetry Data Collected
- Activity events (command execution, code generation)
- Error events (error names and messages)
- Scenario timing (start and end durations)
- Environment metadata (region, geo, cluster)
- Tenant ID (collected only after authentication, non-PII)
Telemetry Configuration Scope
- From PAC CLI version 1.51.1, telemetry can be managed specifically for code commands
- Telemetry settings are stored locally on the developer machine
Telemetry Control Options
- enabled – Controls whether telemetry is sent remotely
- consoleOnly – Logs telemetry locally without sending it externally
- outputToConsole – Displays telemetry in the terminal in addition to remote sending
Telemetry Modes
- Enabled (default) – Telemetry is sent remotely with no console output
- Disabled – No telemetry is collected or sent
- Remote + Console – Telemetry is sent remotely and displayed in the console
- Console-only – Telemetry is logged locally only
Logging Telemetry to a File
- Console telemetry output can be redirected to a file
- Useful for troubleshooting, debugging, and support scenarios