Introduction
Support for OAuth 2.0 is available for Pulseway users with an Office 365 mailbox as their outbound ID for email notifications.
Pulseway enhances the security of Microsoft Office 365 SMTP integration for outbound emails by replacing the legacy username/password authentication with OAuth authorization code flow. The update eliminates the need to store user credentials and aligns with Microsoft’s planned deprecation of basic authentication, ensuring continued email delivery and compliance.
Important: Migration to this new authentication method should be completed prior to Microsoft’s deprecation of basic authentication to ensure continued functionality of outbound emails from the VSA 10 platform. At the time of writing, deprecation is expected to start on December 31st, 2026. Check here for up to date details.
The Office 365 account used for this configuration must have a valid license for this integration to work.
Setup in Microsoft Azure
To connect your mailbox using OAuth 2.0 in Pulseway, you will set up the RMM app in your Azure portal.
Step 1: App Registration
Log in to the Azure portal using your global administration credentials.
In the Azure services section on the home page, click Microsoft Entra ID.
From the left navigation menu, navigate to Manage > App registrations.
Enter a name for the app in the Name field.
In the Supported account types section, select Multiple Entra ID Tenants.
Configure the Redirect URL, set the platform to Web, and enter your redirect URI, formatted as https://[your Pulseway URL]app/main/configuration/settings
Click Register
Copy the Application (client) ID and Directory (tenant) ID from the confirmation page and save them to any accessible notes app on your device. You will paste these tokens in Pulseway later on.
Step 2: Authentication
From the left navigation menu, navigate to Manage > Authentication
In the Settings section, Enable the Allow public client flows.
Click Save.
Step 3: Create a client secret
From the left navigation menu, go to Manage > Certificate & Secrets
Select Client Secrets tab, click New Client Secret
Enter a description and set the expiration date, then click on Add.
Copy the Value for the client secret you just created
Important: Client secret values cannot be retrieved after creation. Be sure to save the Value
Step 4: API permissions
From the left navigation menu, navigate to API permissions.
Click Add a permission.
In the Request API permissions pane that opens, select Microsoft Graph.
Select Delegated permissions.
Add the following permission Mail.Send and SMTP.Send
Click Grant admin consent for a user, and the status for all the permissions will be active.
Setup in Pulseway RMM
IMPORTANT: OAuth 2.0 does not support MFA-enabled accounts because the Microsoft Graph API does not support this.
Go to Pulseway RMM, navigate to Configuration > Settings.
Expand the Email drop-down menu and select Server Settings.
Select OAuth and enter the Application ID, Directory ID and Client Secret Value you saved during app registration on Entra.
Click Setup OAuth, a window will pop for you to confirm the email permissions for Pulseway. Click Accept.
Save and test your connection.