Showing results for 
Search instead for 
Did you mean: 
Frequent Visitor

Unable to create connection to SMTP server (on-prem Exchange)

Hello. I am trying to use on-prem Exchange server for email notifications from a flow.  However, when I try to create a connection to an SMTP server (providing the public IP of the on-prem Exchange server, credentials, port, and SSL option), it fails with the error "Something went wrong. Please try again later." It doesn't tell me why it fails. I have referenced  the article ( and added the IP addresses to be allowed for SMTP traffic in our firewall.


What else do I need to do to make this connection? Once I make the connection, would I be able to select the sender email address to send from?


I am able to use my Office 365 account to send email from the flow but I do not want the notifications to come from my address hence this attempt to use an on-prem Exchange server.




Resident Rockstar
Resident Rockstar

Most people create a service account and use that to send emails, you can also create a shared mailbox if it is only for emails and grant yourself permission to send from that and use that in your flow.


For your other question if you do it get working, it will send email as the mailbox you have authenticated with in the connection.

Frequent Visitor

Thank you. I am currently using my Office 365 login and my mailbox to test the flow. However, I am trying to set up the same flow for a client that doesn't have Office 365 (but has on-prem Exchange). We will be purchasing a license for the client to have access to Power Automate but we are trying to avoid setting up a mailbox with it for the same domain because we already have on-prem Exchange and did not want to set up a hybrid environment. Therefore, I would like to use the on-prem Exchange as the SMTP server to send email from .... if it is possible.

Resident Rockstar
Resident Rockstar

i dont think you roffice 365 login will login to the on prem exchange, will need to be a user with a mailbox locally i suspect.


perhaps your best bet is to add a exchange online license to that account and just use the domain

Frequent Visitor

I do have a domain account for the client's network. We are trying to use the client's primary or secondary domain name for the sender rather than

Hi @AK42.


if your client runs Exchange on-premise, just don't use Power Automate.

You can create a so called transport agent to send notifications.




Helpful resources

Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Microsoft Ignite

Microsoft Power Platform: 2021 Release Wave 1 Plan

Power Platform release plan for the 2021 release wave 1 describes all new features releasing from April through September 2021.

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Top Kudoed Authors
Users online (66,828)