In Deployment: Directory Based Edge Blocking for Exchange Online Protection

I originally read this article and agreed with the sentiments on the replies, thinking that perhaps the best solution would be to have an "Exchange Online" blog that is different than an "Exchange On-Premisis" blog, since a lot of the blog posts tend to be online-centric, or at least - respectfully - somewhat antisocial to the onpremesis crowd.

But then I realized that the unification of the code kind of prohibits that. There really is no difference from a "online/onprem" codebase solution, so some articles tend to focus on an aspect of the code.

So having said that, respectfully, ALL articles need to be written from BOTH customer viewpoints, otherwise I agree with the original poster who claimed that articles like these start to sound like a selling point. If the team is going to write a article detailing the features of a product in one context and ignore the other contexts, then you're effectively pushing the sale. And to that end, while I've never posted here before, have to agree that this is not helping the strategy.

I know there are good people on the team just throwing out good information as they can, but as you can tell from the replies - and I count myself amongst them - I am getting tired of hearing about features I don't have from a so-called "unified code-base product", and the message gets cloudy. Please stop this...