How to Disable Outlook Safelinks

2 minute read

Microsoft offer a feature called “Advanced Threat Protection” on their Exchange email offerings. Several months ago, they decided to provide this functionality for free to subscribers of Office 365. Unfortunately, there’s a large reason why you might not be a fan and that is the feature Microsoft calls “Safelinks”. I’ve previously written about the problems with Safelinks and my attempts and eventual success in getting it disabled on my account. You can find that here. Unfortunately, on 31/07/18 for whatever reason, Safelinks was once again active on my account.

How to get ATP disabled

Although I was annoyed that this feature had been reenabled without me knowing, I was happy to see that Microsoft have made it much simpler for people to get it deactivated. After a bit of searching I found this post and at the bottom, they say this:

Can I deactivate Safe Links?

To provide the best protection for your account, these features are on by default, and because they apply to each email alias individually, they are not designed to be turned off. You can contact our customer service team to have them deactivate the features on your behalf, but we do not recommend it. You can only request removal for aliases on your own account.

Copy the following text:

Please disable Safe Links for the following email aliases; [alias_1], [alias_2]…

Open the Help pane.

Paste the text, replacing “[alias_1]” etc. with your own email aliases.

Select Get help.

So, I followed their instructions and the link to the help pane where I pasted their text and entered my email address.


It automatically displays a block of text asking you to confirm the request to disable ATP and displays the following when you click “Yes”.


It took a rather impressive 4 minutes for me to receive this email:


…and then around 12 hours later, I received this and the emails I received following it all add their original links, unaltered links - success!


I’m wondering whether ATP was reenabled because Microsoft changed their process for managing which aliases should have it disabled. Whatever the reasoning was, it was only a slight inconvenience and it’s really not that big of a deal. I’m just glad that Microsoft have a proper process in place for those of us who don’t want it enabled. It’s also nice to see that they handle such requests in a timely manner.

Short link: