Previous laptop cloud image that had been on company network previously

Using a cloud backup image from a previous Windows 10 device that had been joined to a company network can definitely carry over organization-related settings and device registrations. These can affect sign-in, compliance, and access to work or school resources.

From the provided information, there are two main areas where remnants of the old company setup can cause issues:

1. Device compliance / access to work or school resources
   If the restored image still has the device registered to the old organization, you may see messages like:

• "Device is not compliant" when accessing work or school apps or services.
• Prompts that the device must be joined or compliant with organizational policy.

In such cases, the guidance is:

• Make sure the device is properly joined to the correct organization’s network and account, and that the sign-in account matches the intended work or school account.
• If the device is still associated with an old organization, contact that organization’s helpdesk or IT to remove or disable the old device registration and policies, then rejoin the device to the correct organization.

2. Device identity / sign-in issues after restore
   If the restored image includes an old domain or Microsoft Entra (Azure AD) registration, the machine account password or device identity may no longer match what the directory expects. This can cause sign-in or authentication errors after a restore. The documented behavior is:

• Cloud or domain-joined devices maintain a machine account password that changes periodically. If a device is restored to an older state, the stored password may be out of sync, preventing domain sign-in.
• The recommended fix in such cases is to recover or re-register the device with the directory (for example, by leaving and rejoining the domain or Microsoft Entra join, depending on how the device is configured) so that the device identity and password are refreshed.

If the laptop is now intended for personal or different business use, and remnants of the old company configuration continue to cause problems (compliance errors, sign-in prompts tied to the old tenant, or device management issues), the most reliable options are:

• Fully remove the old work or school account and device registration, then join the device to the correct work or school account and network; or
• Perform a clean install and set up the device directly with the desired account/tenant, avoiding reuse of an image that was previously joined to another organization.

References:

• Troubleshooting compliance error messages for a work or school account
• Windows 365 Enterprise and Windows 365 Flex known issues
• Known issues: Windows 365 Business
• Connection issues when signing in after updating to Office 2016 build 16.0.7967 on Windows 10
• Can’t switch my Microsoft account from personal to work details - Microsoft Q&A
• Entra-only users cannot log into hybrid joined Windows 11 device | syncing 400 bad request problems and Number of retry attempts exceeds expectation - Microsoft Q&A
• Device management could not be enabled - Microsoft Q&A