Telemetry in PnP PowerShell

Up to September 4th, 2026, PnP PowerShell reported its usage anonymously to the PnP team. We collected information about the version of PnP PowerShell, the operation system version and the cmdlet executed. Notice that we did not include parameters used and we did not include any values of parameters. We were also not be able to trace the execution back to the specific tenant it ran on, the organization it was used for or the person it was run by. Having had telemetry in place allowed us to get insight in the usage of cmdlets and thereby prioritize work towards the most popular cmdlets. Over the years the popularity of PnP PowerShell has grown to a level where the costs of collecting and storing all this data became a substantial amount. We have therefore decided to stop collecting this data as the costs no longer outweighed the advantages of us having insights into the usage. The endpoint for the telemetry collection has been removed. Starting with version 3.4.2 the sending of telemetry has been removed from the PowerShell module. Any prior versions will still try to submit telemetry, but submitting the telemetry will no longer succeed. It will not interfere with the normal execution of your PowerShell scripts.

The telemetry PnP PowerShell cmlets Get-PnPPowerShellTelemetryEnabled, Disable-PnPPowerShellTelemetry and Enable-PnPPowerShellTelemetry have been marked as obsolete in version 3.4.2. They will throw a warning when used and will no longer function, but are being kept in the v3 releases for backwards compatibility so existing scripts using them will not break. In version 4.0.0 onwards, these cmdlets have been removed entirely as they no longer serve purpose.