We have received consistent feedback from our customers that the ability to reject messages for invalid recipients at the service network perimeter is important. We are aggressively working to desi...
Updated Jul 01, 2019
Version 2.0
Blog Post
Well this is unnerving. Why isn't the fact that this feature is missing from EOP stated anywhere on the communications I've received from Microsoft about the transition? Those emails, and the website they direct me to, make no mention about losing any features that are currently present in FOPE. In fact, the email I received says "As part of the transition we will move all of your policy settings and configuration to the new service". Apparently "all" doesn't mean what I thought it meant. Recipient validation I would think is part of "all" the policies we have set up today. And another commentor, Kevin, strongly implies EUQ being gone too, is that true? If so, that will be a huge problem for us. I have to plan to retrain 10,000 users if that's the case, as well as find another product to re-implement that functionality.
What else haven't you told us? What else is missing from EOP that we are using today in FOPE? I *NEED* to know this to plan effectively. "Leave the work to us" suddenly sounds like a good way to be in front of management the day after the transition explaining why things aren't working the way they did previously.
My confidence is a bit shaken, to say the least. Maybe it's time to shop for another service that has better communication with their customers. Or that doesn't put you through an "upgrade" that removes features you are already paying for, and rely upon.