Error Code 70003 Azure: How to Resolve Intune and Azure AD Issues

The good news is that resolving this issue is often a matter of checking a few key settings. One of the most common causes of Error Code 70003 Azure is a misconfigured Azure AD tenant.

To fix this, you'll want to check the Azure AD portal and ensure that the correct permissions are set for your Intune users. This includes making sure that the "Intune service principal" has the necessary permissions to access Azure AD.

The error code 70003 Azure issue is often a mystery, but it's not always an Intune problem. Jason Sandys, a Microsoft Employee, weighed in on the discussion, stating that Intune has nothing to do with identity, so it's not a direct issue with Intune.

The error message itself is a dead giveaway - someone deleted the device object out of Azure Active Directory (AAD). By default, when signing into Microsoft 365 apps, the device is automatically registered with AAD, unless the user unchecks the checkbox that does this. Most users never do this, so the device gets registered.

This is why the issue is happening on non-BYOD devices as well. Jason Sandys suspects that someone at your organization, or maybe a script, is deleting these device objects leading to the issue.

Here are some possible reasons why this might be happening:

To resolve the issue, you'll need to investigate and identify the cause of the deleted device objects. Once you've identified the problem, you can take steps to prevent it from happening again.

The error code 70003 Azure can be frustrating, but understanding the possible causes can help you troubleshoot the issue.

One possible cause of error code 70003 Azure is a corrupted application object. Azure AD doesn't recognize the certificate configured for the application, which can prevent authentication from working properly.

Office 365 doesn't get errors very often, but one error that can occur is Error Code 0x426-0x0, which prevents you from using the apps due to corrupt files.

Corrupt files can be a major issue, but you can try to resolve the issue by unblocking macros, which can be a little tricky.

To unblock macros, you'll need to go through specific menus, but it's worth the effort to get your apps up and running again.

Macros can be a great way to speed up data entry, but they may be flagged as untrustworthy, which can cause problems.

If you're experiencing issues with Error Code 0x426-0x0, try checking for corrupt files and unblocking macros to get your Office 365 apps working smoothly again.