*IMPORTANT* Pleas note this is informational only. A solid solution must be designed and tested by qualified personal. This article simply describes issues seen with cloud joined accounts and some potential work arounds using this information. Support should not be contacted to devise a solution on this matter.  Migration Manager currently is not designed to migrate Cloud linked user accounts. 

When a computer is migrated between domains, the Azure Workplace Join gets partially destroyed but not fully cleaned up.  After migration, when users launch O365 applications such as Outlook, they are asked to register with their organization.  When they attempt to do this a TPM error occurs and this error can be difficult to get around.

Microsoft 365 Apps for enterprise activation state require resetting.

Solution 1:

Reset Microsoft 365 Apps for enterprise activation state - Office

Solution 2:

For clearing Azure app dependency trouble a possible freeware tool at https://www.forensit.com/downloads.html may be able to perform the task leaving Windows Apps connected to O365 intact. 

Solution 3: 

1. Upgrade to MMAD 8.15.8 by installing Update 20240228 which includes improvements to the TPM cleanup.
   Per the 8.15.8 update release notes:
   Reset TPM (Trusted Platform Module) permissions upon first login of the processed user.
   This is done via a scheduled task. Due to the nature of the Windows task scheduler, this task will be triggered on every subsequent login on but the script itself detects that it has been run before and does nothing on subsequent logins. This is recorded via the script creating a file in "%UserProfile%\AppData\Roaming\Quest\tpmfix\tasktriggered.txt" to indicate that the script has already been started at least once.  -  MMAD 285636
2. If using an older Cache Credentials Utility (CCU) see the attached word document "Deploying WPJCleanup with CCU" for a potential workaround under "cloud attachments".