Network Management

Scheduled report emails in the SolarWinds Platform fail due to expired Microsoft Entra client secret

This article explains how to resolve an issue where SolarWinds scheduled reports fail to send email when the Office 365 / Microsoft Entra SMTP or Graph configuration uses an Azure AD application with an expired client secret.

First published date

4/9/2026 5:41 PM

Last published date

4/9/2026 5:41 PM

Overview

Scheduled reports appear to run on time, but no email is delivered to recipients.

Manually running the same report from the web console succeeds.

The ReportingLogger (or equivalent reporting logs) shows failures during the email sending step via smtp.office365.com or Microsoft Graph, not during report generation.

The error includes a ClientSecretCredential authentication failed message and Azure AD error AADSTS7000222 indicating expired client secret keys.

Product section

Network Performance Monitor

Cause

The Azure AD / Microsoft Entra application used by SolarWinds for Modern Authentication to Office 365 (SMTP or Microsoft Graph) is configured with an expired client secret. 

When SolarWinds attempts to authenticate using this expired secret, Microsoft Entra rejects the request with AADSTS7000222, causing the email delivery step of scheduled reports to fail even though the report content is generated successfully.

Resolution

Step 1 - Confirm the error

  1. Review the reporting logs.
  2. Verify the failure is occurring during the email sending step.
  3. Confirm the log includes ClientSecretCredential authentication failed or AADSTS7000222.

Step 2 – Renew the client secret in Microsoft Entra ID

  1. Sign in to the Microsoft Entra admin center with an account that can manage app registrations.

  2. Go to Microsoft Entra ID > App registrations.

  3. Locate the application used by SolarWinds for Office 365 email (by name or Application (client) ID).

  4. Open the app and select Certificates & secrets.

  5. Under Client secrets, select New client secret.

  6. Enter a description, choose an appropriate Expires value based on your security policy, and select Add.

  7. Immediately copy the Value of the new client secret and store it securely (this value cannot be retrieved later).

Note: Microsoft recommends considering certificate-based credentials as a more secure alternative to client secrets for application authentication.

Step 3 – Update the SolarWinds email configuration

  1. In the SolarWinds Web Console, navigate to Settings > All Settings > Notification Settings / SMTP Servers (or Email Settings, depending on product version).

  2. Edit the email configuration that sends via smtp.office365.com or Microsoft Graph using Modern Authentication / Client ID & Secret.

  3. Replace the old client secret with the new client secret value created in Microsoft Entra ID.

  4. Use the Test button on this configuration to verify that a test email is sent successfully from the configured sender address (for example, a shared mailbox or alerting account).

Step 4 – Re-test scheduled reports

  1. Navigate to Reports > Manage Schedules.

  2. For each previously failing report schedule, select Run Now.

  3. Confirm that:

    • The schedule completes without ClientSecretCredential authentication failed or AADSTS7000222 errors in the logs.

    • All intended recipients receive the emailed report.

Validation:

Use the following checks to confirm the issue is resolved:

  • A test email from the SMTP / Graph configuration succeeds.
  • The scheduled report completes without ClientSecretCredential authentication failed or AADSTS7000222 errors in the logs.
  • All intended recipients receive the report email.

If emails are still failing:

  • Verify that SolarWinds is using the correct app registration and the latest client secret.

  • Check that the app registration has the appropriate permissions for SMTP or Graph send operations.

  • Review Microsoft Entra sign-in logs for additional errors beyond AADSTS7000222 to identify other configuration or permission issues.