Microsoft 365 Error Codes

How to Fix Moodle Sign-In Error AADSTS700016 Application Not Found

Partner EditorPartner Editor Oct 10, 2026 869 views

Question details

The user is unable to sign into the Moodle portal using Microsoft 365 credentials because the system returns an AADSTS700016 error.

How to Resolve Moodle Sign-In Error AADSTS700016
Product
Microsoft 365
Device & OS
not provided
Scenario
Attempting to log into a third-party application portal (Moodle.apc.com) via Microsoft 365 Single Sign-On (SSO).
Observed behavior
The login fails with error AADSTS700016, indicating that the application identifier was not found in the directory or the sign-in request was routed to the wrong tenant.
Before you start

Before proceeding, take a screenshot or copy the entire error message from the sign-in screen, making sure to capture the application identifier, correlation ID, and timestamp to provide to your IT support team.

Solution 1Recommended

Contact Your Organization's IT Administrator

This is a tenant-level configuration issue that requires administrative access to Microsoft Entra ID (Azure AD) to fix.

Error AADSTS700016 occurs when the application (in this case, Moodle) has not been properly registered in your organization's Microsoft 365 directory. Because end users do not have permission to register enterprise applications, you cannot resolve this on your own.

Microsoft Community or regular Microsoft Support cannot access your organization's backend systems to fix this.

1
Copy the error details

Highlight and copy the full text of the AADSTS700016 error, especially the Application Identifier (Client ID) and Correlation ID.

2
Identify your support contact

Find the contact information for your school or company's IT helpdesk, or the website administrator for Moodle.apc.com.

3
Submit a support ticket

Send an email or submit a ticket to your IT administrator including the copied error details, your affected account email address, and the exact time you attempted to sign in.

Contact Your Organization's IT Administrator
Why Admin Access is Necessary: Administrators need to log into the Microsoft Entra admin center to manually add the application to the tenant or fix the routing configuration for the SSO integration.
Free Microsoft Office alternative

Experience Hassle-Free Productivity with WPS Office

While you wait for your IT administrator to resolve cloud sign-in and directory errors, you can keep your local work uninterrupted. WPS Office is a highly compatible, feature-rich alternative to Microsoft Office that doesn't require complex tenant configurations to edit your local files.

  1. 1. Download the Installer: Visit the official WPS Office website and click the Free Download button.
  2. 2. Install WPS Office: Run the downloaded installer file and follow the on-screen instructions to set up the software.
  3. 3. Open Your Files: Launch WPS Office and open your Word, Excel, or PowerPoint documents directly from your local drive.
100% compatible with Microsoft Office formats, including DOCX, XLSX, and PPTX.Work completely offline without dealing with Microsoft 365 login errors or tenant directory issues.Lightweight architecture ensures fast installation and smooth performance even on older computers.Familiar interface lets you transition seamlessly without any learning curve.
microsoft office alternative - wps office

Frequently Asked Questions

What exactly does Microsoft 365 error AADSTS700016 mean?

This error signifies that the application you are attempting to log into has not been registered in your organization's Microsoft Entra ID (formerly Azure AD) tenant, or your sign-in request was misrouted to a different organization's directory.

Can I fix the AADSTS700016 error by resetting my Microsoft 365 password?

No. Password resets will not fix this issue because it is a backend configuration problem between the third-party application (Moodle) and the organization's cloud directory, not an issue with your user credentials.

Why does Microsoft Community refuse to fix this directory error?

Microsoft Community support agents do not have administrative access to individual organizational tenants. Privacy and security policies dictate that only your organization's verified global administrators can manage enterprise applications and resolve tenant-specific configuration errors.