Make sure on initial setup on a workstation that you go back into settings and choose all email in offline settings instead of 1 year
For Hybrid Exchange:
o update the username, follow these additional steps:
Open PowerShell
Connect to the online service with the following commands:
$msolcred = get-credential
connect-msolservice -credential $msolcred
(Note: Enter your Office 365 credentials when prompted)
Enter the command to update the user name:
Set-MsolUserPrincipalName -UserPrincipalName mary.osgood@contoso.onmicrosoft.com -NewUserPrincipalName mary.smith@contoso.com
Solution 1: Delete the Files in the NGC Folder
The NGC folder contains PIN and security-related credentials. If these files are damaged, it can lead to this error. Follow these steps to clear the NGC folder:
Access the NGC Folder:
Open Open File Explorer and navigate to: and navigate to: C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC
If the AppData folder is not visible, enable hidden folders:
Click on File > Change folder and search options.
Go to the View tab and select Show hidden folders, files, and drives.
Click Apply, then OK.
Take Ownership of the NGC Folder:
Right-click the NGC folder and select Properties.
Then, go to the Security tab and click Advanced.
Click the Change option next to Owner.
Enter your current account username, click Check Names, and then OK.
Ensure the box Replace owner on sub-containers and objects is checked.
Click Apply and OK.
Delete Files in the NGC Folder:
Open the NGC folder and delete all its contents.
Restart your system and re-enter your PIN.
Hope, this solution helped you to fix Outlook 365 TPM error. If not, try another procedure.
Solution 2: Rename the Microsoft AAD Broker Plugin Folder
This solution bypasses authentication issues caused by the AAD Broker Plugin. Follow the steps given:
Navigate to the following directory: C:\Users\%username%\AppData\Local\Packages\ Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy.
Rename the folder to: Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy.old.
Log out of your system and log in again to see if the issue persists.