When you create a Microsoft 365 external location and click OK, the printer verifies the configuration: it checks the connectivity with the Microsoft 365 cloud server. If this fails, an error is displayed. If it is a Microsoft 365 specific error, then this error message is a Microsoft message. These are always in English.
NOTE
If the verification fails, you can save the configuration in WebTools Express and correct it later. If this external location is used on the printer in the meantime, the Microsoft 365 error message will be displayed on the user panel of the printer.
According to the error message, perform the verifications proposed in the next table in order to fix the issue.
|
Error message |
Action to perform |
|---|---|
|
The connection test to Microsoft 365 failed, see details below: AADSTS90002: Tenant <ID> not found. Check to make sure you have the correct tenant ID and are signing in to the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant. Trace ID: <Trace ID> Correlation ID: <Correlation ID> Timestamp: <timestamp> |
A mistake is made with the Application (client) ID and/or the Directory (tenant) ID when configuring the external location. Check the IDs you configured and/or check with your IT administrator. |
|
The connection test to Microsoft 365 failed, see details below: AADSTS700016: Application with identifier <ID> was not found in the directory <name>. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant. Trace ID: <Trace ID> Correlation ID: <Correlation ID> Timestamp: <timestamp> |
The Application (client) ID is wrong. Check the configured Application (client) ID and/or check with your IT administrator |
|
The connection test to Microsoft 365 failed, see details below: AADSTS900023: Specified tenant identifier <ID> is neither a valid DNS name, nor a valid external domain. Trace ID: <Trace ID> Correlation ID: <Correlation ID> Timestamp: <timestamp> |
The Directory (tenant) ID is wrong. Check the configured Directory (tenant) ID and/or check with your IT administrator. |
|
The test of the external location cannot be performed: an internal error has occurred. Please restart the system and try again. |
This error is generated when a proxy is required but not configured in WebTools Express. Check the proxy settings in WebTools Express. |
|
Sign in Sorry, but we're having trouble signing you in. AADSTS50020: User account <Account> from identity provider <Account tenant ID> does not exist in tenant '<name>' and cannot access the application <Application ID><Application name> in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account. |
The user does not exist in the tenant environment where the account is registered. Please check with your IT administrator to determine whether the user account needs to be invited to the tenant, or use a different account that is already registered in the specified tenant environment. |
|
<External location name> cannot be reached (Microsoft Error: Invalid_client (7000218: (AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'. Trace ID: <Trace ID> Correlation ID: <Correlation ID> Timestamp: <timestamp>)). Please check that the Microsoft 365 environment is configured correctly |
In the Microsoft Entra admin center, navigate to: Applications → App registrations → Your created application → Authentication → Advanced settings. Check whether Allow public client flows is set to Yes. If it is not, change the setting to Yes and save the application. |