Easiest way to create an Office 365 profanity block list

[chrisjako]

I specifically want it for exchange but it wouldn't hurt to have the DLP running over sharepoint and onedrive files too

 

How do you do yours?

[AngryITGuy]

When we first deployed 365 I was surprised this function wasn’t built in by design or at the very least the functionality to simply enable it.

 

We ended up scouring google for various profanity lists and we created our own list from these and imported it in to Exchange online with Powershell.

 

The Powershell essentially created mailflow rules designed to block messages based on content taken from the csv files we created.

[round2it]

I created a mail flow rule.

 

 

good team building I had to add each word that might be classed as bad language but seeing as I have no team it was up to me to add them.

 

We have securus so I add any words that get picked up by that.

 

not the best solution but at least I am doing something.

Edited July 26, 2018 by round2it

[chrisjako]

I created a mail flow rule. [ATTACH=CONFIG]49817[/ATTACH]

 

 

good team building I had to add each word that might be classed as bad language but seeing as I have no team it was up to me to add them.

 

We have secures so I add any words that get picked up by that.

 

not the best solution but at least I am doing something.

 

and you used powershell to import the words from a CSV? all i can see is one work entries

[round2it]

unfortunately not I will be investigating how to do that once I migrate over, yep one word entries it was a not so quick fix bigger fish to fry

[AngryITGuy]

unfortunately not I will be investigating how to do that once I migrate over, yep one word entries it was a not so quick fix bigger fish to fry

 

You can use Powershell to import the files from a csv.

 

I’ll dig up the commands and post they’re here for you.

[round2it]

thanks for that

[AngryITGuy]

So the command is as follows

 

New-TransportRule "#RULENAME" -SubjectOrBodyContainsWords (Get-Content

#PathToCSV) -RejectMessageReasonText "Profanity Detected Message Not

Delivered."

 

Just replace the #RULENAME with something to identity the rule in Exchange Online and #PathToCSV needs to exist on the local machine you’re using to connect to Exchange Online with.

[round2it]

will give that a go thankyou.

 

New to o365 no cpd for anything these days

[chaplic]

Also note there is a maximum rule size, so you may need multiple rules, e.g. profanity a-f, profanity g-l and so on.

 

I would also build an exception DL in so that some people can swear