Using Exchange Online (Office 365) For OpsMgr Email Notification

I haven’t been able to use OpsMgr email notifications in my lab since the beginning, because I do not have an on-prem Exchange server (nor that I want to). I have been using my enhanced email notification script and mobile device push notification scripts in the past.

Few weeks ago, I needed to setup a GSM monitor for a website and send notification to few other MVP friends via Email. Cameron pointed me to an old blog post from Marnix on setting up SMTP relay for OpsMgr notifications:

I also managed to find another post by a fellow MVP Anton Gritsenko on setting up SCSM notification using Exchange Online (Office 365) via SMTP relay:

with the help of these 2 posts, I managed to quickly configure email notifications in my OpsMgr management group using Office 365.

As more and more organisations have moved from having On-Prem Exchange environments to using Office 365, I thought this setup could be useful for the community when someone need to use email notification in an environment without Exchange servers.

Since Marnix and Anton has already blogged this solution, I’ll only briefly go through what I’ve done in my lab:

01. In one of my Office 365 subscriptions (Enterprise E3), I create a user and assigned a license to it:


This user ID will be used to authenticate to Office 365 and email notifications will be send via this account.

02. Get the SMTP setting for your Office 365 subscription:


03. Add the “SMTP Server” feature on one of my Windows Server 2012 R2 VMs:


04. Open IIS 6.0 manager and you can see the SMTP Virtual Server:


05. Configure SMTP Relay:

Outbound Security:


Outbound Connections:




06. Created a DNS alias smtp.<domain name> and pointed to the server where I installed SMTP server.

07. Setup SMTP notification channel in OpsMgr:


that’s it, it should take no longer than 10 minutes. Although I haven’t tried with other email provider, theoretically, it should also work of Gmail,, etc. as long as you have a valid account and the correct SMTP settings.


  1. If you have an on-prem exchange server, you really ought not use that for your only OpsMgr SMTP anyway because how would you know anything was wrong if mail flow was affected unless you are staring at the console? We use a local SMTP on the management servers with on-prem Exchange as the backup SMTP should that service fail. Then we use a third party notification / escalation service (OpsGenie) to relay alerts to text messages, phone calls, and alternate email addresses. This way we are never relying solely on a single point of failure for notification. Sadly, as handy as it is, the local SMTP feature is deprecated and may be removed after Windows Server 2012 R2. 🙁 I hope it sticks around because it is SO HANDY.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: