How to Disable Microsoft 365 Office Diagnostic and Telemetry Logs
Question details
The user wants to stop Microsoft 365 applications from creating background diagnostic files in the Temp folder, as standard registry and ADMX methods are ineffective.
- Product
- Microsoft 365 Office
- Device & OS
- Windows
- Scenario
- Attempting to enhance data protection and privacy by disabling background diagnostic and telemetry logging in Microsoft 365 apps.
- Observed behavior
- Microsoft 365 apps continue to generate diagnostic logs in the AppData\Local\Temp\Diagnostics folder despite applying standard ADMX templates and registry changes.
Ensure you have administrative privileges for your device and identify your Microsoft 365 tenant administrator, as backend telemetry policies are usually controlled at the organizational level.
Submit a Service Request via Microsoft 365 Admin Center
Since local registry and ADMX template changes do not override backend telemetry, opening a support ticket is the most effective way to address forced diagnostic logging.
Microsoft 365 requires certain diagnostic data to keep the software secure and functioning correctly. Because these required logs often override local settings, they cannot be bypassed with standard local Group Policy (ADMX) or registry edits. Your tenant administrator must work with Microsoft Support to determine which telemetry policies can be modified from the backend.
Contact your IT department or the person who manages your organization's Microsoft 365 subscription.
Have the administrator log in to the Microsoft 365 Admin Center using their admin credentials.
Go to the 'Support' section in the left-hand menu and select 'New service request'.
Provide the support team with details about the AppData\Local\Temp\Diagnostics logs and ask them to verify the tenant's diagnostic policies to disable location or telemetry logs from the backend.
Turn Off Optional Diagnostic Data in Office Trust Center
Ensure that any user-level optional diagnostic data collection is disabled directly within the Office application settings.
Switch to WPS Office for a Lightweight, Privacy-Friendly Experience
If you are concerned about persistent background processes, telemetry logs, and high system resource usage in Microsoft 365, consider switching to WPS Office. It provides a familiar interface, strong privacy controls, and full compatibility with Microsoft formats without the heavy diagnostic overhead.
- 1. Download and Install: Visit the official WPS Office website to download the free installer for your operating system.
- 2. Open Your Files: Launch WPS Office and directly open your existing .docx, .xlsx, or .pptx files seamlessly.
- 3. Manage Privacy Settings: Enjoy a lightweight office suite without forced background telemetry tracking your local document usage.
Frequently Asked Questions
Why do Microsoft 365 apps create files in the Temp Diagnostics folder?
Microsoft 365 applications continuously run telemetry and diagnostic services to monitor software health, track performance, and generate crash reports. These logs are stored temporarily in your AppData directory before being periodically sent to Microsoft servers or cleared.
Can I permanently delete the diagnostic files in AppData\Local\Temp?
Yes, you can safely delete the contents of the AppData\Local\Temp\Diagnostics folder to free up hard drive space without harming the software. However, unless the underlying telemetry policy is disabled by an administrator, the applications will simply recreate the files the next time they run.
Why aren't my ADMX templates or Registry edits working to stop telemetry?
Microsoft frequently updates its telemetry requirements, and certain diagnostic data is categorized as strictly 'Required' for the software to function, update, or stay secure. These required logs generally bypass standard local Group Policy (ADMX) or registry edits, making them difficult to disable without tenant-level intervention from Microsoft Support.
