Network Management
How to configure SMTP using Microsoft Graph (OAuth 2.0) for email notifications in the SolarWinds Platform 2025.2 and above
This article explains how to configure SMTP email notifications in the SolarWinds Platform using Microsoft Graph (OAuth 2.0), the modern and recommended replacement for Exchange Web Services (EWS). Microsoft Graph provides enhanced security through least-privilege permissions (Mail.Send), mailbox-scoping policies, and alignment with Microsoft's current authentication standards.
First published date
Last published date
Overview
Microsoft has officially announced that on October 1, 2026, EWS requests to Exchange Online will be blocked. Additionally, Microsoft is retiring Basic Authentication for SMTP Client Submission (SMTP AUTH) in Exchange Online, with enforcement beginning March 2026 and reaching 100% rejection by April 30, 2026.
If you are currently using EWS OAuth 2.0 or Basic Authentication for SMTP in the SolarWinds Platform, you must migrate to Microsoft Graph before these deadlines to avoid email notification failures.
The Microsoft Graph SMTP client option is available starting with SolarWinds Platform 2025.2.
Why Microsoft Graph over EWS?
|
Capability |
EWS OAuth 2.0 |
Microsoft Graph |
|---|---|---|
|
Permission model |
|
|
|
Mailbox scoping |
Not natively supported |
Application Access Policies limited to specific mailboxes |
|
Microsoft investment |
Deprecated — blocked Oct 2026 |
Actively maintained and recommended |
|
Security posture |
Higher blast radius if credentials are compromised |
Reduced blast radius with granular permissions |
|
Conditional Access & audit |
Limited |
Full integration with Entra ID Conditional Access and audit logs |
Product section
Cause
Microsoft is deprecating legacy authentication methods for Exchange Online:
-
Basic Authentication (username/password) for SMTP AUTH retired March–April 2026.
-
Exchange Web Services (EWS) blocked October 1, 2026.
Applications must migrate to OAuth 2.0 with Microsoft Graph API to continue sending email notifications through Exchange Online.
Reference: Retirement of Exchange Web Services in Exchange Online
Resolution
Step 1: Register your application in Microsoft Entra ID
-
Open a browser and navigate to the Microsoft Entra admin center. Log in with an admin account.
-
Navigate to Identity → Applications → App registrations.
-
Click + New registration.
-
Configure the registration:
-
Name: Enter a friendly name (e.g.,
SolarWinds-SMTP-Graph). -
Supported account types: Select the option appropriate for your organization (typically Accounts in this organizational directory only).
-
Redirect URI: Set to Public client (mobile & desktop) and enter:
https://login.microsoftonline.com/common/oauth2/nativeclient
-
-
Click Register.
-
On the Overview page, copy and save:
-
Application (Client) ID
-
Directory (Tenant) ID
-
Step 2: Configure API permissions (Mail.Send)
-
In the app registration, go to API permissions under Manage.
-
Click + Add a permission → Microsoft Graph → Application permissions.
-
Search for
Mail.Sendand select it. -
Click Add permissions.
-
Click Grant admin consent for [your organization] and confirm.
|
Note: Unlike EWS, which required |
Step 3: Create a Client Secret
-
Go to Certificates & secrets under Manage.
-
Click + New client secret.
-
Enter a description and select an expiration period.
-
Click Add.
-
Copy the Secret Value at this step as it will not be shown again.
Step 4: Limit application permissions to specific mailboxes (recommended)
Following Microsoft best practices, restrict the app to send only from approved mailboxes:
-
Create a mail-enabled security group in Exchange Online containing the mailbox(es) the app should send from.
-
Connect to Exchange Online PowerShell:
Install-Module -Name ExchangeOnlineManagement Import-Module ExchangeOnlineManagement Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com -
Create an Application Access Policy:
New-ApplicationAccessPolicy -AppId "<Your_Client_ID>" ` -PolicyScopeGroupId "<security_group_email>" ` -AccessRight RestrictAccess ` -Description "SolarWinds SMTP Graph - restricted to approved mailboxes" -
Test the policy:
Test-ApplicationAccessPolicy -Identity "<mailbox_email>" -AppId "<Your_Client_ID>"Expected result:
Grantedfor mailboxes in the group,Deniedfor all others.
Step 5: Configure Microsoft Graph in the SolarWinds Platform Web Console
-
Log in to the SolarWinds Platform Web Console as an administrator.
-
Navigate to Settings → All Settings → Manage SMTP Servers.
-
Click Add SMTP Server.
-
In the SMTP Client dropdown, select Microsoft Graph.
-
Enter the following values:
-
Application (Client ID): The Client ID from Step 1.
-
Directory (Tenant ID): The Tenant ID from Step 1.
-
Client Secret: The secret value from Step 3.
-
-
Click Send Test Email to verify the configuration.
-
Click Save.
Step 6: Remove legacy EWS configuration (if applicable)
If you previously used EWS OAuth 2.0:
-
After confirming Microsoft Graph is working, go back to Manage SMTP Servers.
-
Remove or disable the old EWS OAuth 2.0 SMTP server entry.
-
In Microsoft Entra ID, remove the
full_access_as_apppermission from the old EWS app registration (or delete the old app registration entirely if it is no longer needed).