Additionally, if Trend Micro antivirus software is installed, it might interfere with the AAD Broker Plugin, leading to this error. No matter the cause, the following methods have helped many users. Follow these steps one by one to find the solution that works for you.
1. Add Scan Exclusion in Trend Micro Antivirus (if applicable)
Trend Micro Antivirus can sometimes interfere with the AAD Broker Plugin, which handles sign-in and identity processes for Microsoft applications. This interference can cause error code 1001 by disrupting the plugin’s authentication tasks. To resolve this, you can add a scan exclusion for the AAD Broker Plugin in Trend Micro Antivirus, preventing the antivirus from scanning or blocking the plugin. The AAD Broker Plugin folder is now added to the scan exclusion list in your antivirus software. Check if the issue has been resolved.
2. Recreate User Profile
Over time, Microsoft 365 user profiles can become corrupted or misconfigured due to unexpected system shutdowns, incomplete or faulty updates, antivirus interference, or other issues. Creating a new user profile removes the corrupted or misconfigured files and forces Microsoft 365 to generate fresh ones. This process resets all user-specific configurations, enabling Microsoft 365 to establish a clean and functional authentication process. Once the new user is created, sign in with the new account and try signing in to Microsoft 365 to check if the issue has been resolved.
3. Clear OneAuth and IdentityCache
The OneAuth and IdentityCache folders store sign-in tokens and authentication data used by Microsoft 365. If these folders become outdated or corrupted, they can interfere with the login process, preventing successful authentication. Clearing these folders forces Microsoft 365 to generate fresh authentication data, resolving any conflicts and allowing you to log in without issues.
4. Open Microsoft 365 Application in Safe Mode
Corrupted settings or conflicting add-ins can prevent Microsoft 365 applications from authenticating properly, leading to errors like this one. Launching applications in Safe Mode temporarily disables all third-party add-ins and custom settings, allowing the application to load only essential components. This method helps identify whether the issue is caused by an external plugin or a deeper system-level problem.
