I just updated our Pulseway to OAuth for outbound email. Now instead of our dedicated do-not-reply email account sending out emails, all messages for the past few days from Pulseway have been using my own email as the from or reply to address. Is there a way to change that? We currently have those alerting emails create a ticket on our system but if it is from "me" then it creates havoc in that system.

Edited March 24Mar 24 by Martin U.

Hey @Martin U. - Thanks for reaching out. It is suggested to have a dedicated email for Pulseway notifications If your using your own account the notifications would be sent to your email.

We're running into this same issue.
I've come across a few bugs in regard to the OAuth 2.0 Email Settings.

Firstly, when you attempt to "Re-Configure OAuth", it won't even open the login.microsoftonline.com window, to allow you to Select an alternative Account.



It simply activates the "Application Id", "Directory Id" and "Client Secret" Fields, but after re-submitting, it assumes that you want to use the same Email Account/Credentials.



I actually had to completely Delete our original "Pulseway RMM" App Registration and create a new one, from scratch, with a new "Application Id", "Directory Id" and "Client Secret", before it would the Pulseway Email Settings Web UI would actually open the login.microsoftonline.com Window, allowing me to select another Email Account.

Unfortunately, there is a bug in this process, as well. I say this because after successfully signing into the correct O365 Account, it doesn't return to the original Pulseway Email Settings window, but rather, it loads the Email Settings page directly into the Microsoft Sign-in window.





Worse yet, when I maximize this window, I find that the OAuth Form contains the "Application Id", "Directory Id" and "Client Secret" from the old/Deleted App Registration, which still says that it is "Configured", for some reason.



Of course, when you attempt to click on the "Send Test Email" option, it immediately fails, with an "Access Token was Not Granted" Message.



I've gone over the App Registration Settings multiple times and I am confident that the App Registration Settings are correct.

That being said, there appears to be no working method for changing an OAuth SMTP Email Address, at least for the present time.

Any assistance you can provide with this issue, will be greatly appreciated.

Thank you, in advance.

P.S. It might also be a good idea to update your documentation to inform admins that the account you're authenticating with, will be the account from which Emails/Alert messages will be sent (since many apps require "Application" MS Graph API Permissions, as opposed to "Delegated" Permissions).

Edited 23 hours ago23 hr by MrMattiPants

On 4/2/2026 at 10:03 AM, Mariale_Pulseway said:

Hey @Martin U. - Thanks for reaching out. It is suggested to have a dedicated email for Pulseway notifications If your using your own account the notifications would be sent to your email.

Sure, I get that. I was simply testing via my account, with the assumption that it could be changed later.

Unfortunately, there seems to be no way to change the outbound email address once you've authenticated for the first time.

Fortunately, I was able to restore the original App Registration and re-connect it to my personal account.

I suppose I'll try generating a new Client Secret to see if it will let me authenticate via our dedicated SMTP Account.

Edited 1 hour ago1 hr by MrMattiPants