Forum Discussion
Disable auto forwarding email to external recipients using Microsoft Flow
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.
- Michel van VlietApr 11, 2019Copper Contributor
VasilMichevI 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.
- VasilMichevApr 11, 2019MVP
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.
- MichelvanVlietApr 11, 2019Copper Contributor
VasilMichevthat'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?