{"generated":"2026-10-18T00:33:42.391Z","source":"https://azureblog.co.uk","count":116,"codes":[{"code":"0x8018000A","decimal":-2145910774,"area":"Enrollment","name":"The device is already enrolled.","meaning":"The device is already enrolled. Usually a different user has already enrolled the device in Intune or joined it to Microsoft Entra ID.","fix":"Sign in as the account that enrolled or joined the device, remove the work or school account under Settings > Accounts > Access work or school, then sign in with your own account and enrol again.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/troubleshoot-windows-enrollment-errors","url":"https://azureblog.co.uk/intune-errors/0x8018000a/"},{"code":"0x8007064C","decimal":-2147023284,"area":"Enrollment","name":"The machine is already enrolled.","meaning":"Enrolment fails because the computer was previously enrolled, was built from a cloned image of an enrolled computer, or still holds the previous account certificate.","fix":"Delete the Intune certificate issued by Sc_Online_Issuing from the computer Personal store and the HKLM\\SOFTWARE\\Microsoft\\OnlineManagement registry key (back up the registry first), then try to enrol again.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/troubleshoot-windows-enrollment-errors","url":"https://azureblog.co.uk/intune-errors/0x8007064c/"},{"code":"0x80180026","decimal":-2145910746,"area":"Enrollment","name":"Something went wrong. Confirm you are using the correct sign-in information...","meaning":"Joining a Windows device to Microsoft Entra ID fails because MDM automatic enrolment is enabled and the legacy Intune PC software client (PC agent) is installed on the device.","fix":"Either uninstall the Intune PC software client from the computer, or set MDM user scope to None under Microsoft Entra ID > Mobility (MDM and MAM) > Microsoft Intune.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/troubleshoot-windows-enrollment-errors","url":"https://azureblog.co.uk/intune-errors/0x80180026/"},{"code":"0x8018002B","decimal":-2145910741,"area":"Enrollment","name":"Auto MDM Enroll: Failed\" (Event ID 76)","meaning":"Automatic MDM enrolment through Group Policy failed. The user UPN uses an unverified or non-routable domain (such as .local), or MDM user scope is set to None.","fix":"Give affected users a valid, verified UPN suffix and let Microsoft Entra Connect sync, or set MDM user scope to All or Some under Microsoft Entra ID > Mobility (MDM and MAM) > Microsoft Intune.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/troubleshoot-windows-enrollment-errors","url":"https://azureblog.co.uk/intune-errors/0x8018002b/"},{"code":"0x80180003","decimal":-2145910781,"area":"Enrollment","name":"This user is not authorized to enroll.","meaning":"The user is not allowed to enrol. Causes include reaching the device enrolment limit, a device platform restriction blocking Windows (MDM), Windows Home edition, or users not being allowed to join devices to Microsoft Entra ID.","fix":"Remove unused devices or raise the device limit, set Windows (MDM) to Allow in enrolment restrictions, upgrade Home to Pro or higher, and check that \"Users may join devices to Microsoft Entra ID\" allows the user.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/windows-user-cannot-enroll","url":"https://azureblog.co.uk/intune-errors/0x80180003/"},{"code":"0x801C0003","decimal":-2145648637,"area":"Enrollment","name":"This user is not authorized to enroll.","meaning":"The same user-not-authorised condition as 0x80180003: device limit reached, platform restriction, Windows Home edition, or Entra device join not permitted for the user.","fix":"Remove unused devices or raise the device limit, allow Windows (MDM) in enrolment restrictions, upgrade from Home edition, and allow the user to join devices to Microsoft Entra ID.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/windows-user-cannot-enroll","url":"https://azureblog.co.uk/intune-errors/0x801c0003/"},{"code":"0x80180018","decimal":-2145910760,"area":"Enrollment","name":"Something went wrong.","meaning":"Enrolment in Intune or another MDM fails. Common causes are incorrect or missing licences assigned to the user, or too many devices enrolled for the user.","fix":"Check the user has the correct Intune licence assigned and has not reached the device enrolment limit.","source":"https://learn.microsoft.com/en-us/autopilot/troubleshooting-faq","url":"https://azureblog.co.uk/intune-errors/0x80180018/"},{"code":"0x80180002","decimal":-2145910782,"area":"Enrollment","name":"MENROLL_E_DEVICE_AUTHENTICATION_ERROR","meaning":"The MDM server failed to authenticate the user during enrolment.","fix":"Confirm the user is signing in with the correct work account. Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180002/"},{"code":"0x80180001","decimal":-2145910783,"area":"Enrollment","name":"MENROLL_E_DEVICE_MESSAGE_FORMAT_ERROR","meaning":"Invalid schema or message format error returned from the server during enrolment.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180001/"},{"code":"0x80180004","decimal":-2145910780,"area":"Enrollment","name":"MENROLL_E_DEVICE_CERTIFCATEREQUEST_ERROR","meaning":"The user has no permission for the certificate template or the certificate authority is unreachable.","fix":"Check the user's permissions on the certificate template and that the certificate authority is reachable.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180004/"},{"code":"0x80180005","decimal":-2145910779,"area":"Enrollment","name":"MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR","meaning":"There was a failure at the management server, such as a database access error.","fix":"This is a server-side failure. Retry the enrolment later and check the service health in the Intune admin centre if it persists.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180005/"},{"code":"0x80180006","decimal":-2145910778,"area":"Enrollment","name":"MENROLL_E_DEVICE_INTERNALSERVICE_ERROR","meaning":"There was an unhandled exception on the management server.","fix":"This is a server-side failure. Retry the enrolment later and check the service health in the Intune admin centre if it persists.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180006/"},{"code":"0x80180008","decimal":-2145910776,"area":"Enrollment","name":"MENROLL_E_DEVICE_UNKNOWN_ERROR","meaning":"Unknown server error during enrolment.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180008/"},{"code":"0x80180009","decimal":-2145910775,"area":"Enrollment","name":"MENROLL_E_ENROLLMENT_IN_PROGRESS","meaning":"Another enrolment operation is already under way on the device.","fix":"Wait for the current enrolment to finish, then retry. Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180009/"},{"code":"0x8018000B","decimal":-2145910773,"area":"Enrollment","name":"MENROLL_E_DEVICE_NOT_ENROLLED","meaning":"The device is not enrolled, so an operation that needs an existing enrolment could not run.","fix":"Confirm the device enrolment state under Settings > Accounts > Access work or school and enrol the device if needed.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x8018000b/"},{"code":"0x8018000E","decimal":-2145910770,"area":"Enrollment","name":"MENROLL_E_PASSWORD_NEEDED","meaning":"A password is needed for enrolment but was not supplied.","fix":"Retry the enrolment and complete the sign-in prompt with the user's credentials.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x8018000e/"},{"code":"0x80180010","decimal":-2145910768,"area":"Enrollment","name":"MENROLL_E_CONNECTIVITY","meaning":"A network error occurred during enrolment, such as a DNS failure or a network timeout.","fix":"Check DNS resolution, proxy and firewall access to the Intune enrolment endpoints, then retry.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180010/"},{"code":"0x80180012","decimal":-2145910766,"area":"Enrollment","name":"MENROLL_E_INVALIDSSLCERT","meaning":"The SSL certificate presented during enrolment was not valid.","fix":"Check that nothing on the network path is presenting a different certificate for the enrolment endpoints. Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180012/"},{"code":"0x80180013","decimal":-2145910765,"area":"Enrollment","name":"MENROLL_E_DEVICECAPREACHED","meaning":"The user has already enrolled too many devices.","fix":"Delete or unenrol old devices for the user (the user can do this without admin help), or raise the device limit restriction.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180013/"},{"code":"0x80180015","decimal":-2145910763,"area":"Enrollment","name":"MENROLL_E_NOTSUPPORTED","meaning":"Mobile device management is not supported for this device.","fix":"The device cannot be MDM enrolled as it stands. Check the Windows edition and version are supported for Intune enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180015/"},{"code":"0x80180017","decimal":-2145910761,"area":"Enrollment","name":"MENROLL_E_INMAINTENANCE","meaning":"The account is in maintenance.","fix":"Retry the enrolment later.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180017/"},{"code":"0x80180019","decimal":-2145910759,"area":"Enrollment","name":"MENROLL_E_ENROLLMENTDATAINVALID","meaning":"The server rejected the enrolment data. The server may not be configured correctly.","fix":"The server may not be configured correctly. Check the MDM application settings under Microsoft Entra ID > Mobility (MDM and MAM). Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180019/"},{"code":"0x8018001B","decimal":-2145910757,"area":"Enrollment","name":"MENROLL_E_PLATFORM_WRONG_STATE","meaning":"An invalid operation was attempted, such as trying to enrol the same device twice or unenrol an unknown device.","fix":"Check whether the device is already enrolled under Settings > Accounts > Access work or school before retrying.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x8018001b/"},{"code":"0x8018001C","decimal":-2145910756,"area":"Enrollment","name":"MENROLL_E_PLATFORM_LICENSE_ERROR","meaning":"The version (edition) of Windows installed on the device does not support this enrolment type.","fix":"Upgrade the device to a Windows edition that supports the enrolment type, such as Pro or higher.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x8018001c/"},{"code":"0x8018001D","decimal":-2145910755,"area":"Enrollment","name":"MENROLL_E_PLATFORM_UNKNOWN_ERROR","meaning":"An unknown error occurred on the client during enrolment.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x8018001d/"},{"code":"0x8018001E","decimal":-2145910754,"area":"Enrollment","name":"MENROLL_E_PROV_CSP_CERTSTORE","meaning":"Provisioning failed in the certificate store CSP during enrolment.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x8018001e/"},{"code":"0x80180020","decimal":-2145910752,"area":"Enrollment","name":"MENROLL_E_PROV_CSP_DMCLIENT","meaning":"Provisioning failed in a DM client CSP during enrolment.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180020/"},{"code":"0x80180021","decimal":-2145910751,"area":"Enrollment","name":"MENROLL_E_PROV_CSP_PFW","meaning":"Provisioning failed in a Passport for Work (Windows Hello for Business) CSP during enrolment.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180021/"},{"code":"0x80180022","decimal":-2145910750,"area":"Autopilot","name":"Autopilot device enrollment failed with error HRESULT = 0x80180022","meaning":"Autopilot enrolment failed because the device being provisioned is running Windows Home edition.","fix":"Upgrade the device to Pro edition or higher.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/troubleshoot-windows-enrollment-errors","url":"https://azureblog.co.uk/intune-errors/0x80180022/"},{"code":"0x80180023","decimal":-2145910749,"area":"Enrollment","name":"MDM Enroll: Provisioning failed","meaning":"Enrolment of a Microsoft Entra hybrid joined device failed because the dmwappushservice service is missing from the device. Often logged together with 0x800706D9.","fix":"Export HKLM\\SYSTEM\\CurrentControlSet\\Services\\dmwappushservice from a working device on the same Windows version, import it on the affected device, restart, remove the old Entra registration and run a Group Policy update.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/comanage-configmgr/troubleshoot-co-management-auto-enrolling","url":"https://azureblog.co.uk/intune-errors/0x80180023/"},{"code":"0x800706D9","decimal":-2147023143,"area":"Enrollment","name":"MDM Enroll: OMA-DM client configuration failed. RAWResult: (0x800706D9)","meaning":"Seen alongside 0x80180023 when a Microsoft Entra hybrid joined device fails to enrol because the dmwappushservice service is missing.","fix":"Restore the dmwappushservice service registry key from a working device on the same Windows version, restart, then re-register the device and update Group Policy.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/comanage-configmgr/troubleshoot-co-management-auto-enrolling","url":"https://azureblog.co.uk/intune-errors/0x800706d9/"},{"code":"0x80180024","decimal":-2145910748,"area":"Enrollment","name":"MENROLL_E_PROV_SSLCERTNOTFOUND","meaning":"When binding the public certificate to the private key during provisioning, the public certificate was not found.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180024/"},{"code":"0x80180025","decimal":-2145910747,"area":"Enrollment","name":"MENROLL_E_PROV_CSP_APPMGMT","meaning":"Provisioning failed in the EnterpriseAppManagement CSP during enrolment.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180025/"},{"code":"0x80180027","decimal":-2145910745,"area":"Enrollment","name":"MENROLL_E_CERTPOLICY_PRIVATEKEYCREATION_FAILED","meaning":"The device failed to create the private key during enrolment.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180027/"},{"code":"0x80180028","decimal":-2145910744,"area":"Enrollment","name":"MENROLL_E_CERTAUTH_FAILED_TO_FIND_CERT","meaning":"Certificate authentication was requested, but the device failed to find a certificate to use.","fix":"Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180028/"},{"code":"0x80180029","decimal":-2145910743,"area":"Enrollment","name":"MENROLL_E_EMPTY_MESSAGE","meaning":"The server responded with HTTP 200, but the message was empty.","fix":"Retry the enrolment. Check the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device for the failing step and retry the enrolment.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180029/"},{"code":"0x80180030","decimal":-2145910736,"area":"Enrollment","name":"MENROLL_E_USER_CANCELED","meaning":"The user cancelled the enrolment operation.","fix":"Ask the user to restart the enrolment and complete all prompts.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180030/"},{"code":"0x80180031","decimal":-2145910735,"area":"Enrollment","name":"MENROLL_E_MDM_NOT_CONFIGURED","meaning":"Mobile device management is not configured.","fix":"Check that Microsoft Intune is configured as the MDM application under Microsoft Entra ID > Mobility (MDM and MAM) with the correct MDM user scope.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x80180031/"},{"code":"0x8018002A","decimal":-2145910742,"area":"Enrollment","name":"Auto MDM Enroll: Failed (Unknown Win32 Error code: 0x8018002a)","meaning":"Microsoft Entra hybrid joined (co-managed) devices fail to auto-enrol because per-user MFA is set to Enforced, which stops the Configuration Manager client enrolling with the signed-in user's credentials.","fix":"Set per-user MFA to Enabled rather than Enforced, or temporarily bypass MFA during enrolment using Trusted IPs.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/comanage-configmgr/troubleshoot-co-management-auto-enrolling","url":"https://azureblog.co.uk/intune-errors/0x8018002a/"},{"code":"0xCAA2000C","decimal":-895352820,"area":"Enrollment","name":"The request requires user interaction.\" (interaction_required)","meaning":"Logged in the Microsoft Entra ID Operational log when MFA blocks the token needed for automatic enrolment or MDM sync of a co-managed device (AADSTS50076).","fix":"Remove per-user MFA enforcement or use Trusted IPs, or exclude the Microsoft Intune app (0000000a-0000-0000-c000-000000000000) from Conditional Access policies that require MFA.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/comanage-configmgr/troubleshoot-co-management-auto-enrolling","url":"https://azureblog.co.uk/intune-errors/0xcaa2000c/"},{"code":"0xCAA9001F","decimal":-894894049,"area":"Enrollment","name":"Integrated Windows authentication supported only in federation flow.","meaning":"MDM enrolment of co-managed, hybrid joined devices fails because the Configuration Manager client tried integrated Windows authentication against Entra ID while the domain is not federated.","fix":"Configure Azure Services for Cloud Management in Configuration Manager and enable both AD User Discovery and Microsoft Entra user Discovery for the users.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/mdm-enrollment-error-0xcaa9001f","url":"https://azureblog.co.uk/intune-errors/0xcaa9001f/"},{"code":"0x801C03F2","decimal":-2145647630,"area":"Enrollment","name":"DSREG_E_DIRECTORY_FAILURE","meaning":"Microsoft Entra hybrid join failed with a DirectoryError, typically \"The public key user certificate is not found on the device object\". The device object is missing in Entra ID or its userCertificate attribute is not populated.","fix":"Make sure the userCertificate attribute is populated on the on-premises computer object and synced. If missing, run dsregcmd /leave, delete the MS-Organization-Access certificate, restart, then run a delta sync.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/comanage-configmgr/troubleshoot-co-management-auto-enrolling","url":"https://azureblog.co.uk/intune-errors/0x801c03f2/"},{"code":"0x80090016","decimal":-2146893802,"area":"Enrollment","name":"NTE_BAD_KEYSET / \"Keyset does not exist","meaning":"Device registration could not save the device key because the TPM keys were not accessible, usually because Windows is not the owner of the TPM.","fix":"Clear the TPM (Windows Security > Device security > Security processor details > Security processor troubleshooting) and restart the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/comanage-configmgr/troubleshoot-co-management-auto-enrolling","url":"https://azureblog.co.uk/intune-errors/0x80090016/"},{"code":"0x80280036","decimal":-2144862154,"area":"Enrollment","name":"TPM_E_NOTFIPS","meaning":"Automatic device registration failed because the TPM has FIPS mode enabled, which is not supported for Azure device registration.","fix":"Do not use FIPS mode on the TPM for devices that need to register with Microsoft Entra ID.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/comanage-configmgr/troubleshoot-co-management-auto-enrolling","url":"https://azureblog.co.uk/intune-errors/0x80280036/"},{"code":"0x801C001D","decimal":-2145648611,"area":"Enrollment","name":"DSREG_AUTOJOIN_ADCONFIG_READ_FAILED","meaning":"Hybrid join could not read the service connection point (SCP) object to get the Microsoft Entra tenant information.","fix":"Check the service connection point is configured correctly for Microsoft Entra hybrid join.","source":"https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current","url":"https://azureblog.co.uk/intune-errors/0x801c001d/"},{"code":"0x801C0021","decimal":-2145648607,"area":"Enrollment","name":"DSREG_AUTOJOIN_DISC_FAILED","meaning":"Generic discovery failure: the device could not get discovery metadata from the device registration service (DRS).","fix":"Look at the sub-error (often a network code such as 0x80072EE2) to find the underlying cause.","source":"https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current","url":"https://azureblog.co.uk/intune-errors/0x801c0021/"},{"code":"0x801C0002","decimal":-2145648638,"area":"Enrollment","name":"DSREG_E_DEVICE_AUTHENTICATION_ERROR","meaning":"The device registration service returned an AuthenticationError (with a sub-code other than DeviceNotFound).","fix":"Check the server error code in the User Device Registration Admin event log for the specific reason.","source":"https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current","url":"https://azureblog.co.uk/intune-errors/0x801c0002/"},{"code":"0x801C0006","decimal":-2145648634,"area":"Enrollment","name":"DSREG_E_DEVICE_INTERNALSERVICE_ERROR","meaning":"The device registration service returned an error response during registration.","fix":"Check the server error code in the User Device Registration Admin event log for the specific reason.","source":"https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current","url":"https://azureblog.co.uk/intune-errors/0x801c0006/"},{"code":"0x80290407","decimal":-2144795641,"area":"Enrollment","name":"TPM_E_PCP_INTERNAL_ERROR","meaning":"Generic TPM error during Microsoft Entra hybrid join.","fix":"Disable the TPM on affected devices. Windows 10 1809 and later detect TPM failures and complete hybrid join without the TPM.","source":"https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current","url":"https://azureblog.co.uk/intune-errors/0x80290407/"},{"code":"0x80090031","decimal":-2146893775,"area":"Enrollment","name":"NTE_AUTHENTICATION_IGNORED","meaning":"The TPM is locked out (anti-hammering) during device registration.","fix":"This is transient. Wait for the TPM cool-down period and the join should succeed afterwards.","source":"https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current","url":"https://azureblog.co.uk/intune-errors/0x80090031/"},{"code":"0x80CF4017","decimal":-2133901289,"area":"Enrollment","name":"The software cannot be installed\" / \"The account certificate is not valid and may be expired","meaning":"The legacy Intune PC client software on the device is out of date.","fix":"Download the current client software from the admin console (Admin > Client Software Download) and install it.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/troubleshoot-windows-enrollment-errors","url":"https://azureblog.co.uk/intune-errors/0x80cf4017/"},{"code":"0x80180014","decimal":-2145910764,"area":"Autopilot","name":"Enrollment blocked for AP device by SDM One Time Limit Check\" (DeviceNotSupported)","meaning":"Re-enrolment of a previously enrolled device is blocked. Either the Intune device record from an earlier self-deploying or pre-provisioning run still exists, or Windows MDM enrolment is blocked by a platform restriction.","fix":"In Intune go to Devices > Windows > Enrollment > Windows Autopilot > Devices, select the device and choose Unblock device, then redeploy. Also check that Windows (MDM) is set to Allow in device platform restrictions.","source":"https://learn.microsoft.com/en-us/autopilot/troubleshooting-faq","url":"https://azureblog.co.uk/intune-errors/0x80180014/"},{"code":"0x80070774","decimal":-2147022988,"area":"Autopilot","name":"Something went wrong... error code 80070774","meaning":"Hybrid Autopilot fails because the domain controller cannot be reached or the device cannot join the domain. Common causes are using Assign user with a hybrid join profile, a deleted Entra device object, or wrong OU permissions for the Intune Connector.","fix":"Unassign the user from the Autopilot device, check the ODJ connector log for event 30132 and delegate Create/Delete computer objects on the OU to the connector server. If the Entra device was deleted, remove and reimport the hardware hash.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/troubleshoot-windows-enrollment-errors","url":"https://azureblog.co.uk/intune-errors/0x80070774/"},{"code":"0x800705B4","decimal":-2147023436,"area":"Autopilot","name":"Securing your hardware (Failed: 0x800705b4)","meaning":"A general timeout. In self-deploying mode it is commonly because the device is not TPM 2.0 capable, for example a virtual machine.","fix":"Use a device with a physical TPM 2.0 for self-deploying mode or pre-provisioning. Virtual TPMs and TPM 1.2 are not supported.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0x800705b4/"},{"code":"0x801C03EA","decimal":-2145647638,"area":"Autopilot","name":"Registering your device for mobile management (Failed: 3, 0x801C03EA)","meaning":"TPM attestation failed, so the device could not join Microsoft Entra ID with a device token. The TPM supports 2.0 but has not been upgraded to it.","fix":"Upgrade the TPM to version 2.0. If it persists, make sure the device is not in two groups with different Autopilot profiles assigned.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/troubleshoot-windows-enrollment-errors","url":"https://azureblog.co.uk/intune-errors/0x801c03ea/"},{"code":"0x81039001","decimal":-2130472959,"area":"Autopilot","name":"E_AUTOPILOT_CLIENT_TPM_MAX_ATTESTATION_RETRY_EXCEEDED","meaning":"TPM attestation intermittently failed during the Securing your hardware step of pre-provisioning or self-deploying mode.","fix":"Retry provisioning. Subsequent attempts might succeed.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0x81039001/"},{"code":"0x81039023","decimal":-2130472925,"area":"Autopilot","name":"","meaning":"TPM attestation failed on Windows 11 during pre-provisioning or self-deploying mode.","fix":"Apply the May 2022 cumulative update for Windows 11 21H2 (KB5013943) or later to the device.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0x81039023/"},{"code":"0x81039024","decimal":-2130472924,"area":"Autopilot","name":"","meaning":"TPM attestation failed on Windows 11 because known vulnerabilities were detected in the TPM.","fix":"Update the TPM firmware from the PC manufacturer's website.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0x81039024/"},{"code":"0x80070490","decimal":-2147023728,"area":"Autopilot","name":"","meaning":"TPM attestation failed on AMD platforms using the ASP firmware TPM (fTPM).","fix":"Update to a later AMD firmware version. Check the device manufacturer's firmware release notes.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0x80070490/"},{"code":"0xC1036501","decimal":-1056742143,"area":"Autopilot","name":"","meaning":"The device cannot do automatic MDM enrolment because there are multiple MDM configurations in Microsoft Entra ID.","fix":"Review Microsoft Entra ID > Mobility (MDM and MAM) so that only one MDM application applies to the users being enrolled.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0xc1036501/"},{"code":"0x801C03F3","decimal":-2145647629,"area":"Autopilot","name":"","meaning":"Pre-provisioning shows an error because Microsoft Entra ID cannot find the device object, typically because it was deleted manually.","fix":"Remove the device from Entra ID, Intune and Windows Autopilot, then re-register it with Autopilot to recreate the Entra device object.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0x801c03f3/"},{"code":"0x800706FD","decimal":-2147023107,"area":"Autopilot","name":"The trust relationship between this workstation and the primary domain failed.","meaning":"Hybrid join pre-provisioning fails when a policy (for example a User Rights setting) needs domain controller connectivity during the technician flow and the device has no line of sight to a DC.","fix":"Do not assign policies needing domain controller connectivity during the technician flow, or pre-provision on a network that can reach a domain controller.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0x800706fd/"},{"code":"0x80004005","decimal":-2147467259,"area":"Autopilot","name":"","meaning":"Microsoft Entra hybrid join Autopilot deployments can time out with this generic error during the deployment.","fix":"Install the fix: KB5065789 or later for 25H2, KB5065426 or later for 24H2, or KB5070312 or later for 23H2.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0x80004005/"},{"code":"0x8007202F","decimal":-2147016657,"area":"Autopilot","name":"A constraint violation occurred.\" (DirectoryServicesCOMException)","meaning":"Known issue with the Intune Connector for Active Directory version 6.2501.2000.5 when creating computer objects for hybrid Autopilot.","fix":"See the Intune Connector for Active Directory guidance in the Windows Autopilot troubleshooting FAQ for the mitigation.","source":"https://learn.microsoft.com/en-us/autopilot/known-issues","url":"https://azureblog.co.uk/intune-errors/0x8007202f/"},{"code":"0x87D1041C","decimal":-2016345060,"area":"App install","name":"The application was not detected after installation completed successfully.","meaning":"Intune installed the app, but it is no longer detected. The user may have uninstalled it, the package identity does not match what the device reports, or a self-updating MSI changed version outside Intune.","fix":"Ask the user to reinstall from Company Portal (required apps reinstall at the next check-in), and check the app's detection details match what is actually installed.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d1041c/"},{"code":"0x80073CFF","decimal":-2147009281,"area":"App install","name":"(client error)","meaning":"The Windows app needs a sideloading-enabled system to install.","fix":"Make sure the package is signed with a trusted signature and the device has the AllowAllTrustedApps policy enabled (domain-joined or with a sideloading licence).","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x80073cff/"},{"code":"0x80CF201C","decimal":-2133909476,"area":"App install","name":"(client error)","meaning":"The Windows app needs a sideloading-enabled system to install.","fix":"Make sure the package is signed with a trusted signature and the device has the AllowAllTrustedApps policy enabled (domain-joined or with a sideloading licence).","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x80cf201c/"},{"code":"0x80073CF0","decimal":-2147009296,"area":"App install","name":"","meaning":"The Windows app package could not be opened. It may be unsigned, or the publisher name does not match the signing certificate subject.","fix":"Check the AppxPackagingOM event log, and confirm the package is signed and the publisher matches the certificate subject.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x80073cf0/"},{"code":"0x80073CF3","decimal":-2147009293,"area":"App install","name":"","meaning":"The Windows app package failed update, dependency or conflict validation, for example a conflicting installed package, a missing dependency or the wrong processor architecture.","fix":"Check the AppXDeployment-Server event log for the specific validation failure.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x80073cf3/"},{"code":"0x80073CFB","decimal":-2147009285,"area":"App install","name":"","meaning":"The package is already installed and reinstallation is blocked, usually because a rebuilt or re-signed package is not identical to the installed one.","fix":"Increment the app version and rebuild and re-sign the package, or remove the old package for every user before installing the new one.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x80073cfb/"},{"code":"0x8000FFFF","decimal":-2147418113,"area":"App install","name":"","meaning":"An unexpected error occurred during installation.","fix":"Check the installation logs on the device for more detail.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x8000ffff/"},{"code":"0x87D13BA2","decimal":-2016330846,"area":"App install","name":"One or more apps contain invalid bundleIDs.","meaning":"A macOS LOB package contains several apps and not all of them report installation status back to Intune, so it shows as failed even if the app installed.","fix":"Run \"sudo /usr/libexec/mdmclient QueryInstalledApps\" on a Mac with the app, remove any included apps in the Intune app information that are not in that list, save and sync.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/error-0x87d13ba2-deploy-macos-lob-app","url":"https://azureblog.co.uk/intune-errors/0x87d13ba2/"},{"code":"0x87D1313D","decimal":-2016333507,"area":"App install","name":"Could not retrieve license for the app with iTunes Store ID","meaning":"iOS/iPadOS: Intune could not get a VPP licence for the app.","fix":"Sync the VPP token then the device. If it persists, reassign as device-licensed, revoke and reassign the licence, or revoke all VPP licences for the device and re-enrol.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d1313d/"},{"code":"0x87D11388","decimal":-2016341112,"area":"App install","name":"iOS/iPadOS device is currently busy.","meaning":"iOS/iPadOS: the device was busy (locked), so the app could not install.","fix":"The user needs to unlock the device for the app to install.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d11388/"},{"code":"0x87D13B64","decimal":-2016330908,"area":"App install","name":"The app installation has failed.","meaning":"iOS/iPadOS: an app installation failure occurred.","fix":"Collect the iOS/iPadOS console logs to troubleshoot.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b64/"},{"code":"0x87D13B66","decimal":-2016330906,"area":"App install","name":"The app is managed, but has expired or been removed by the user.","meaning":"iOS/iPadOS: the user uninstalled the app, the app expired but failed to download, or detection does not match the response from the device.","fix":"Check whether the user removed the app and re-push it. Confirm the app is still valid and downloadable.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b66/"},{"code":"0x87D13B7D","decimal":-2016330883,"area":"App install","name":"Unknown error.","meaning":"iOS/iPadOS: an unknown app installation error. One known cause is an expired VPP token in Intune.","fix":"Check that the Apple VPP token is current and working.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b7d/"},{"code":"0x87D13B62","decimal":-2016330910,"area":"App install","name":"The user rejected the offer to install the app.","meaning":"iOS/iPadOS: the user tapped Cancel at the initial install prompt.","fix":"Ask the user to accept the install request next time.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b62/"},{"code":"0x87D13B63","decimal":-2016330909,"area":"App install","name":"The user rejected the offer to update the app.","meaning":"iOS/iPadOS: the user tapped Cancel during the update.","fix":"Deploy the app as required or ask the user to accept the update prompt.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b63/"},{"code":"0x87D103E8","decimal":-2016345112,"area":"App install","name":"Unknown error","meaning":"An unknown app installation error occurred when no other error applied.","fix":"Retry the installation and collect device logs if it persists.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d103e8/"},{"code":"0x87D13B95","decimal":-2016330859,"area":"App install","name":"Can't find VPP license for app.","meaning":"iOS/iPadOS: no VPP licence was found for the app.","fix":"Try revoking and reassigning the app licence.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b95/"},{"code":"0x87D13B7E","decimal":-2016330882,"area":"App install","name":"License Assignment failed with Apple error 'No VPP licenses remaining'","meaning":"iOS/iPadOS: there are no VPP licences left to assign. This is by design.","fix":"Buy more VPP licences or reclaim licences from users who are no longer targeted.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b7e/"},{"code":"0x87D13B7F","decimal":-2016330881,"area":"App install","name":"Needed app configuration policy not present, ensure policy is targeted to same groups.","meaning":"iOS/iPadOS: the app requires an app configuration policy but none is targeted.","fix":"Target the required app configuration policy to the same groups as the app.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b7f/"},{"code":"0x87D13B8F","decimal":-2016330865,"area":"App install","name":"The application is installed on the device but is unmanaged.","meaning":"iOS/iPadOS LOB app: the app was installed outside Intune.","fix":"Uninstall the app from the device. Intune will install the managed copy at the next sync.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b8f/"},{"code":"0x87D13B68","decimal":-2016330904,"area":"App install","name":"User declined app management","meaning":"iOS/iPadOS: the user declined to let the app be managed.","fix":"Ask the user to accept app management.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b68/"},{"code":"0x87D13B9D","decimal":-2016330851,"area":"App install","name":"The latest version of the app failed to update from an earlier version.","meaning":"iOS/iPadOS: the app is installed and managed but at the wrong version, for example the update command has been sent but the new version has not yet been reported.","fix":"Wait for the device to report the new version, which clears the error, or investigate any different error it fails with.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b9d/"},{"code":"0x87D13B9F","decimal":-2016330849,"area":"App install","name":"The VPP App has an update available","meaning":"iOS/iPadOS: the VPP app is installed but a newer version is available.","fix":"No error as such. The app will update when the newer version is deployed.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b9f/"},{"code":"0x87D13B9E","decimal":-2016330850,"area":"App install","name":"Can't enforce app uninstall setting. Retry installing the app.","meaning":"iOS/iPadOS: the app is installed but its \"uninstall on retire\" setting does not match the configured value.","fix":"Ask the user to request the app from Company Portal so the setting can be applied again.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b9e/"},{"code":"0x87D13BA9","decimal":-2016330839,"area":"App install","name":"The app installation has failed. (ErrorUserEnrollmentUnsupported)","meaning":"A VPP app is deployed with device licensing, but account-driven Apple User Enrollment (BYOD) only supports user licensing.","fix":"Change the assignment licensing type to user licensing, or create a separate assignment for these users.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13ba9/"},{"code":"0x87D12906","decimal":-2016335610,"area":"App install","name":"Apple MDM Agent error: App installation command failed with no error reason specified.","meaning":"iOS/iPadOS: the Apple MDM agent reported the installation command failed without a reason.","fix":"Retry the app installation.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d12906/"},{"code":"0x87D1313C","decimal":-2016333508,"area":"App install","name":"Network connection on the client was lost or interrupted.","meaning":"iOS/iPadOS: the network connection was lost while the download service URL was sent to the device (host not found).","fix":"Retry when the device has a better network connection.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d1313c/"},{"code":"0x87D13B80","decimal":-2016330880,"area":"App install","name":"CannotConnectToITunesStoreError","meaning":"iOS/iPadOS: the app install failed because the device could not connect to the iTunes Store.","fix":"Check the device can reach the App Store and retry.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b80/"},{"code":"0x87D13B6F","decimal":-2016330897,"area":"App install","name":"Your connection to Intune timed out.","meaning":"iOS/iPadOS: app manifest validation failed because of a network timeout.","fix":"Check network connectivity on the device and retry.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0x87d13b6f/"},{"code":"0xC7D14FB5","decimal":-942583883,"area":"App install","name":"The app failed to install.","meaning":"Android (DA/Knox): Intune cannot find the root cause. The APK downloaded but did not install, often a bad APK, Google Play Protect blocking it, or the device not supporting the app.","fix":"Check the APK is valid and supports the device's Android API level, and whether Play Protect blocked it.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0xc7d14fb5/"},{"code":"0xC7D14FB1","decimal":-942583887,"area":"App install","name":"The end user canceled the app installation.","meaning":"Android (DA): the user cancelled or clicked away from the OS install prompt.","fix":"Ask the user not to cancel the install. Intune shows a notification so they can retry.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0xc7d14fb1/"},{"code":"0xC7D14FB2","decimal":-942583886,"area":"App install","name":"The download failed because of an unknown error.","meaning":"Android (DA): the APK download failed, commonly because of Wi-Fi issues or a slow connection.","fix":"Retry from the notification once the device has a reliable connection.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0xc7d14fb2/"},{"code":"0xC7D14FB7","decimal":-942583881,"area":"App install","name":"The app installation APK file used for the upgrade does not match the signature for the current app on the device.","meaning":"Android: the upgrade APK is signed with a different certificate from the installed version.","fix":"Sign the new version with the same certificate, or uninstall the existing app and deploy the new one instead of upgrading.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0xc7d14fb7/"},{"code":"0xC7D14FBB","decimal":-942583877,"area":"App install","name":"The app installation was canceled because the process was restarted during installation.","meaning":"Android (DA/Knox): the device rebooted during APK installation.","fix":"Retry from the Intune notification.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0xc7d14fbb/"},{"code":"0xC7D15015","decimal":-942583787,"area":"App install","name":"The file download process was unexpectedly stopped.","meaning":"Android (DA): the OS stopped the download, for example on low battery or because it took too long.","fix":"Make sure the device has a reliable network connection and retry.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/app-management/app-install-error-codes","url":"https://azureblog.co.uk/intune-errors/0xc7d15015/"},{"code":"0x87D1FDE8","decimal":-2016281112,"area":"Other","name":"Remediation failed (-2016281112)","meaning":"Intune could not confirm the setting was applied, because the device response did not match the policy. Seen for example with custom OMA-URI VPN profiles even when the VPN works.","fix":"For custom VPN profiles it can be ignored, or use a standard VPN profile instead of OMA-URI. For other settings, check the value applied on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-configuration/device-configuration-profile-reports-error-2016281112","url":"https://azureblog.co.uk/intune-errors/0x87d1fde8/"},{"code":"0x87D1FDE9","decimal":-2016281111,"area":"Other","name":"Not applicable for this device","meaning":"The policy or setting does not apply to this device.","fix":"Check the setting is supported on the device's platform, edition and OS version.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d1fde9/"},{"code":"0x87D1FDEE","decimal":-2016281106,"area":"Other","name":"Not applicable because it lost in conflict resolution","meaning":"The setting was not applied because another policy setting won conflict resolution.","fix":"Find the conflicting policies targeting the device and remove or align the duplicate setting.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d1fdee/"},{"code":"0x87D1FDEF","decimal":-2016281105,"area":"Other","name":"Failed to evaluate the Rule","meaning":"Intune failed to evaluate a rule for the setting.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d1fdef/"},{"code":"0x87D1FDEB","decimal":-2016281109,"area":"Other","name":"Data type conversion failed","meaning":"The setting value could not be converted to the expected data type.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d1fdeb/"},{"code":"0x8007065D","decimal":-2147023267,"area":"Other","name":"E_DATATYPE_MISMATCH","meaning":"The data type does not match the expected data type.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/windows/win32/mdmreg/mdm-registration-constants","url":"https://azureblog.co.uk/intune-errors/0x8007065d/"},{"code":"0x87D101F4","decimal":-2016345612,"area":"Other","name":"Syncml(500)","meaning":"OMA-DM status 500: the device encountered an unexpected condition that prevented it fulfilling the request.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d101f4/"},{"code":"0x87D10190","decimal":-2016345712,"area":"Other","name":"Syncml(400)","meaning":"OMA-DM status 400: the command could not be performed because of malformed syntax.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d10190/"},{"code":"0x87D10194","decimal":-2016345708,"area":"Other","name":"Syncml(404)","meaning":"OMA-DM status 404: the requested target (setting node) was not found on the device.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d10194/"},{"code":"0x87D10195","decimal":-2016345707,"area":"Other","name":"Syncml(405)","meaning":"OMA-DM status 405: the requested command is not allowed on the target.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d10195/"},{"code":"0x87D10196","decimal":-2016345706,"area":"Other","name":"Syncml(406)","meaning":"OMA-DM status 406: an optional feature in the request was not supported.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d10196/"},{"code":"0x87D1019C","decimal":-2016345700,"area":"Other","name":"Syncml(412)","meaning":"OMA-DM status 412: the command failed because it was incomplete or incorrectly formed.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d1019c/"},{"code":"0x87D101A2","decimal":-2016345694,"area":"Other","name":"Syncml(418)","meaning":"OMA-DM status 418: the Put or Add command failed because the target already exists.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d101a2/"},{"code":"0x87D101A9","decimal":-2016345687,"area":"Other","name":"Syncml(425)","meaning":"OMA-DM status 425: the sender does not have adequate access control permissions (ACL) on the target.","fix":"Check the setting's OMA-URI, value and data type against the relevant CSP documentation, and review the DeviceManagement-Enterprise-Diagnostics-Provider Admin event log on the device.","source":"https://learn.microsoft.com/en-us/troubleshoot/mem/intune/general/troubleshoot-company-resource-access-problems","url":"https://azureblog.co.uk/intune-errors/0x87d101a9/"},{"code":"0x80072EE2","decimal":-2147012894,"area":"Other","name":"WININET_E_TIMEOUT","meaning":"General network timeout, for example while discovering or registering the device with the device registration service.","fix":"Check network connectivity to https://enterpriseregistration.windows.net and the other required Microsoft endpoints.","source":"https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current","url":"https://azureblog.co.uk/intune-errors/0x80072ee2/"},{"code":"0x80072EFD","decimal":-2147012867,"area":"Other","name":"WININET_E_CANNOT_CONNECT","meaning":"A connection with the server could not be established.","fix":"Check network connectivity to the required Microsoft endpoints.","source":"https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current","url":"https://azureblog.co.uk/intune-errors/0x80072efd/"},{"code":"0x80072F8F","decimal":-2147012721,"area":"Other","name":"WININET_E_DECODING_FAILED","meaning":"The network stack could not decode the server response.","fix":"Make sure a network proxy is not interfering with or modifying the server response.","source":"https://learn.microsoft.com/en-us/entra/identity/devices/troubleshoot-hybrid-join-windows-current","url":"https://azureblog.co.uk/intune-errors/0x80072f8f/"}]}