Home

Disable auto forwarding email to external recipients using Microsoft Flow

%3CLINGO-SUB%20id%3D%22lingo-sub-426609%22%20slang%3D%22en-US%22%3EDisable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-426609%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20several%20ways%20to%20block%20auto%20forwarding%20of%20email%20to%20external%20recipients%20via%20Exchange%20Online.%20However%20there's%20also%20an%20option%20to%20create%20a%20flow%20for%20new%20email%20enabling%20auto%20forwarding%20to%20external%20recipients%20using%20Microsoft%20Flow!%3CBR%20%2F%3EProblem%20with%20this%20method%20is%20that%20none%20of%20the%20existing%20methods%20of%20blocking%20these%20emails%20is%20applicable.%20These%20emails%20are%20directly%20sent%20form%20the%20users%20mailbox%20and%20therefor%20not%20apply%20to%20the%20existing%20rules.%3CBR%20%2F%3EThe%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fflow%2Fprevent-data-loss%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDLP%20option%20for%20flow%3C%2FA%3E%20is%20also%20not%20able%20to%20prevent%20this%20because%20it%20only%20blocks%20sharing%20data%20between%20connectors.%3CBR%20%2F%3EBecause%20everyone%20with%20enabled%20Azure%20AD%20account%20is%20able%20to%20use%20Microsoft%20Flow%20(even%20if%20they%20don't%20have%20the%20feature%20enabled%20within%20their%20license%20plan)%2C%20there's%20no%20way%20to%20block%20this%20(as%20far%20as%20I%20know).%3CBR%20%2F%3EIs%20there%20any%20way%20to%20avoid%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-426609%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-430962%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-430962%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20most%20likely%20because%20Flow%20doesn't%20do%20an%20actual%20%22forward%22%20action%2C%20but%20simply%20prepares%20a%20new%20message%20and%20copies%20all%20the%20relevant%20details.%20You%20as%20the%20admin%20are%20able%20to%20see%20the%20types%20of%20Flows%20your%20users%20are%20using%2C%20and%20delete%20them%20if%20needed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-437290%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-437290%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3EI%20agree%20that%20as%20an%20Admin%20you're%20able%20to%20(re)view%20flows%20which%20users%20have%20created%20but%20the%20problem%20with%20that%20is%20that%20it%20will%20always%20be%20reactive.%20We%20need%20to%20be%20able%20to%20prevent%20users%20to%20use%20this%20functionality%20and%20with%20that%20prevent%20all%20mailbox%20data%20to%20leave%20the%20organization.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-438918%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-438918%22%20slang%3D%22en-US%22%3E%3CP%3EWell%20you've%20proactively%20enabled%20the%20users%20to%20use%20Flow%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20don't%20disagree%20with%20you%2C%20it%20would%20be%20nice%20to%20be%20able%20to%20control%20such%20flows%2C%20but%20as%20you%20noted%20above%20this%20one%20doesn't%20seem%20to%20be%20captured%20by%20the%20Flow%20DLP%20capabilities.%20You%20can%20crawl%20the%20Unified%20audit%20log%20for%20any%20events%20corresponding%20to%20the%20Flow%20or%20even%20attach%20an%20alert%20to%20them%2C%20but%20that's%20still%20reactive.%20Then%20again%2C%20there%20are%20potentially%20dozen%20other%20Flows%20that%20can%20be%20abused%20to%20send%2Fsave%20data%20to%20an%20external%20location%2C%20so%20you%20might%20as%20well%20re-evaluate%20the%20need%20to%20enable%20Flow.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-440542%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-440542%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3Ethat's%20just%20it.%20Like%20I%20explained%20in%20the%20post%2C%20we've%20not%20actively%20enabled%20Flow%20(feature%20is%20not%20enabled%20within%20the%20licensing%20plan)%20but%20users%20are%20still%20able%20to%20use%20Flow.%3CBR%20%2F%3EThe%20only%20way%2C%20I%20currently%20see%2C%20to%20proactively%20prevent%20users%20from%20using%20Flow%20to%20auto%20forward%20messages%2C%20is%20to%20block%20acces%20using%20Conditional%20Access%20for%20example.%20There's%20no%20known%20other%20way%20to%20disable%20the%20service%3F!%3CBR%20%2F%3EAnd%20more%20importantly%20there's%20no%20way%20to%20block%20the%20users%20from%20auto%20forwarding%20using%20Flow%20without%20completely%20blocking%20access.%3CBR%20%2F%3EOr%20is%20there%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-442792%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-442792%22%20slang%3D%22en-US%22%3E%3CP%3EDisabling%20the%20license%20should%20at%20least%20remove%20the%20app%20tiles%20for%20Flow%2C%20but%20yeah%20that's%20security%20by%20obscurity.%20Let%20me%20ping%20few%20folks...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-442826%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-442826%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20looking%20at%20the%20audit%20logs%2C%20it%20seems%20that%20Flow%20makes%20direct%20connection%20to%20the%20mailbox%20in%20order%20to%20forward%20each%20message%2C%20meaning%20you%20can%20just%20block%20the%20IP%20ranges%20by%20any%20feature%20that%20allows%20such%20control%20(CA%2C%20auth%20policies%2C%20etc)%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fflow%2Flimits-and-config%23ip-address-configuration%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fflow%2Flimits-and-config%23ip-address-configuration%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-446634%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-446634%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F10576%22%20target%3D%22_blank%22%3E%40Michel%20van%20Vliet%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CDIV%3ENot%20sure%20about%20how%20to%20block%20forwarding%20using%20Microsoft%20Flow!%20Have%20heard%20this%20first%20time.%20I%20had%20a%20word%20with%20my%20O365CloudExperts%20team%20and%20they%20answered%20me%20that%20you%20can%20block%20it%20EXO%20as%20there%20are%20several%20options%3A%3CBR%20%2F%3Eblogs.technet.microsoft.com%2Fexchange%2F2017%2F12%2F22%2Fthe-many-ways-to-block-automatic-email-forwarding-in-exchange-online%2F%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3ERegards%2C%3C%2FDIV%3E%3CDIV%3EAkshay%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-453215%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-453215%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318732%22%20target%3D%22_blank%22%3E%40Akshay_Mane%3C%2FA%3EThe%20Exchange%20part%20is%20clear%20(and%20in%20place)%20but%20this%20does%20not%20prevent%20Flow%20form%20using%20EXO%20to%20forward%20emails%20to%20external%20recipients.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-453217%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-453217%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3Ethanks%20for%20the%20suggestion.%20The%20downside%20of%20going%20down%20this%20road%20is%20that%20when%20IP%20addresses%2Frangers%20change%20(or%20are%20added)%20these%20are%20not%20automatically%20reflected%20tot%20the%20block%20configuration%2C%20which%20leaves%20gaps.%20And%20we'd%20like%20to%20only%20block%20forwarding%20to%20external%20recipients%20but%20let%20users%20be%20able%20to%20forward%20to%20internet%20recipients.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-484581%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-484581%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3EAfter%20several%20test%20scenario's%20it%20seems%20there's%20no%20way%20to%20block%20the%20connection%20from%20Flow%20to%20Exchange%20Online%20using%20Conditional%20Access%20policies.%3CBR%20%2F%3EHowever%2C%20I%20managed%20to%20get%20an%20active%20block%20for%20Flow%20using%20a%20Client%20Access%20Rule%20within%20Exchange%20Online.%3CBR%20%2F%3EI%20used%20the%20following%20PowerShell%20code%20to%20block%20the%20US%20en%20Europe%20IP%20addresses%20from%20Flow%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CDIV%3E%3CFONT%3E%24IPRanges%3D%2213.69.227.208-13.69.227.223%22%2C%2252.178.150.68%22%2C%2213.69.64.208-13.69.64.223%22%2C%2252.174.88.118%22%2C%2252.166.241.149%22%2C%2252.166.244.232%22%2C%2252.166.245.173%22%2C%2252.166.243.169%22%2C%2252.178.37.42%22%2C%2240.69.45.126%22%2C%2240.69.45.11%22%2C%2240.69.45.93%22%2C%2240.69.42.254%22%2C%2252.164.249.26%22%2C%22137.117.161.181%22%2C%2213.89.171.80-13.89.171.95%22%2C%2252.173.245.164%22%2C%2240.71.11.80-40.71.11.95%22%2C%2240.71.249.205%22%2C%2240.70.146.208-40.70.146.223%22%2C%2252.232.188.154%22%2C%2252.162.107.160-52.162.107.175%22%2C%2252.162.242.161%22%2C%2240.112.243.160-40.112.243.175%22%2C%22104.42.122.49%22%2C%22104.43.232.28%22%2C%22104.43.232.242%22%2C%22104.43.235.249%22%2C%22104.43.234.211%22%2C%2252.160.93.247%22%2C%2252.160.91.66%22%2C%2252.160.92.131%22%2C%2252.160.95.100%22%2C%2240.117.101.91%22%2C%2240.117.98.246%22%2C%2240.117.101.120%22%2C%2240.117.100.191%22%2C%2213.71.195.32-13.71.195.47%22%2C%2252.161.102.22%22%2C%2213.66.140.128-13.66.140.143%22%2C%2252.183.78.157%22%2C%2252.161.26.191%22%2C%2252.161.27.42%22%2C%2252.161.29.40%22%2C%2252.161.26.33%22%2C%2252.161.31.35%22%2C%2213.66.213.240%22%2C%2213.66.214.51%22%2C%2213.66.210.166%22%2C%2213.66.213.29%22%2C%2213.66.208.24%22%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CP%3E%3CFONT%3ENew-ClientAccessRule%20-Name%20%22Block%20Flow%20Access%22%20-Action%20DenyAccess%26nbsp%3B%20-AnyOfClientIPAddressesOrRanges%20%24IPRanges%3CBR%20%2F%3E%3C%2FFONT%3E%3C%2FP%3E%3CFONT%3E%3CBR%20%2F%3EWhich%20resulted%20in%20an%20error%20within%20Flow%20(%3Dgood%20in%20this%20case%20%3A-))%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F110573i2E8CDAF1F8FE4B45%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22Flow-Error.png%22%20title%3D%22Flow-Error.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CFONT%3EIt%20would%20be%20nice%20if%20we%20can%20get%20a%20formal%20procedure%20to%20get%20this%20blocked%20for%20example%20using%20DLP%20but%20for%20now%20this%20does%20the%20trick.%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-487027%22%20slang%3D%22en-US%22%3ERe%3A%20Disable%20auto%20forwarding%20email%20to%20external%20recipients%20using%20Microsoft%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-487027%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20CA%20policies%20you%20can%20block%20those%20exact%20IP%20ranges%2C%20although%20it's%20a%20tedious%20process.%20CARs%20are%20indeed%20another%20option%2C%20as%20is%20blocking%20the%20connectors'%20user-agent%20string%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fconnectors%2Foffice365%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fconnectors%2Foffice365%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Michel van Vliet
Occasional Contributor

There are several ways to block auto forwarding of email to external recipients via Exchange Online. However there's also an option to create a flow for new email enabling auto forwarding to external recipients using Microsoft Flow!
Problem with this method is that none of the existing methods of blocking these emails is applicable. These emails are directly sent form the users mailbox and therefor not apply to the existing rules.
The DLP option for flow is also not able to prevent this because it only blocks sharing data between connectors.
Because everyone with enabled Azure AD account is able to use Microsoft Flow (even if they don't have the feature enabled within their license plan), there's no way to block this (as far as I know).
Is there any way to avoid this?

11 Replies

That's most likely because Flow doesn't do an actual "forward" action, but simply prepares a new message and copies all the relevant details. You as the admin are able to see the types of Flows your users are using, and delete them if needed.

@Vasil MichevI agree that as an Admin you're able to (re)view flows which users have created but the problem with that is that it will always be reactive. We need to be able to prevent users to use this functionality and with that prevent all mailbox data to leave the organization.

Well you've proactively enabled the users to use Flow :)

 

I don't disagree with you, it would be nice to be able to control such flows, but as you noted above this one doesn't seem to be captured by the Flow DLP capabilities. You can crawl the Unified audit log for any events corresponding to the Flow or even attach an alert to them, but that's still reactive. Then again, there are potentially dozen other Flows that can be abused to send/save data to an external location, so you might as well re-evaluate the need to enable Flow.

@Vasil Michevthat's just it. Like I explained in the post, we've not actively enabled Flow (feature is not enabled within the licensing plan) but users are still able to use Flow.
The only way, I currently see, to proactively prevent users from using Flow to auto forward messages, is to block acces using Conditional Access for example. There's no known other way to disable the service?!
And more importantly there's no way to block the users from auto forwarding using Flow without completely blocking access.
Or is there?

Disabling the license should at least remove the app tiles for Flow, but yeah that's security by obscurity. Let me ping few folks...

So looking at the audit logs, it seems that Flow makes direct connection to the mailbox in order to forward each message, meaning you can just block the IP ranges by any feature that allows such control (CA, auth policies, etc): https://docs.microsoft.com/en-us/flow/limits-and-config#ip-address-configuration

@Michel van Vliet  

Not sure about how to block forwarding using Microsoft Flow! Have heard this first time. I had a word with my O365CloudExperts team and they answered me that you can block it EXO as there are several options:
blogs.technet.microsoft.com/exchange/2017/12/22/the-many-ways-to-block-automatic-email-forwarding-in-exchange-online/
 
Regards,
Akshay

@Akshay_ManeThe Exchange part is clear (and in place) but this does not prevent Flow form using EXO to forward emails to external recipients.

@Vasil Michevthanks for the suggestion. The downside of going down this road is that when IP addresses/rangers change (or are added) these are not automatically reflected tot the block configuration, which leaves gaps. And we'd like to only block forwarding to external recipients but let users be able to forward to internet recipients. 

@Vasil MichevAfter several test scenario's it seems there's no way to block the connection from Flow to Exchange Online using Conditional Access policies.
However, I managed to get an active block for Flow using a Client Access Rule within Exchange Online.
I used the following PowerShell code to block the US en Europe IP addresses from Flow:

$IPRanges="13.69.227.208-13.69.227.223","52.178.150.68","13.69.64.208-13.69.64.223","52.174.88.118","52.166.241.149","52.166.244.232","52.166.245.173","52.166.243.169","52.178.37.42","40.69.45.126","40.69.45.11","40.69.45.93","40.69.42.254","52.164.249.26","137.117.161.181","13.89.171.80-13.89.171.95","52.173.245.164","40.71.11.80-40.71.11.95","40.71.249.205","40.70.146.208-40.70.146.223","52.232.188.154","52.162.107.160-52.162.107.175","52.162.242.161","40.112.243.160-40.112.243.175","104.42.122.49","104.43.232.28","104.43.232.242","104.43.235.249","104.43.234.211","52.160.93.247","52.160.91.66","52.160.92.131","52.160.95.100","40.117.101.91","40.117.98.246","40.117.101.120","40.117.100.191","13.71.195.32-13.71.195.47","52.161.102.22","13.66.140.128-13.66.140.143","52.183.78.157","52.161.26.191","52.161.27.42","52.161.29.40","52.161.26.33","52.161.31.35","13.66.213.240","13.66.214.51","13.66.210.166","13.66.213.29","13.66.208.24"

New-ClientAccessRule -Name "Block Flow Access" -Action DenyAccess  -AnyOfClientIPAddressesOrRanges $IPRanges


Which resulted in an error within Flow (=good in this case :-))
Flow-Error.png
 
It would be nice if we can get a formal procedure to get this blocked for example using DLP but for now this does the trick.

With CA policies you can block those exact IP ranges, although it's a tedious process. CARs are indeed another option, as is blocking the connectors' user-agent string: https://docs.microsoft.com/en-us/connectors/office365/

Related Conversations
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Teams no longer auto launches
trandall in Microsoft Teams on
4 Replies
Teams error code - 6
damnit95 in Office 365 on
4 Replies
Email Domain for Posts to a Channel
Jim Hill in Microsoft Teams on
17 Replies