We’re approaching the one-year anniversary of the release of Exchange Server 2013. This is traditionally the time when people start asking questions like: When is Service Pack 1 coming? ...
Updated Jul 01, 2019
Version 2.0
Blog Post
While I can appreciate this post and the message within (even if not all questions raised in it are answered and it's still IMHO very focused on O365), I do have some suggestions i hope you take into consideration going forward.
Like multiple commentators mention, there are bugs in Exchange 2013. With a complex product, that's not weird. I am however disappointed because there is less information publicly available compared to older Exchange versions (it is a subjective feeling). I also haven't seen a complete list with fixes with CU1 and CU2. I don't need a solution or a workaround. Just an acknowledgement could help IT Pros with explaining the situation to non-technical key persons (and prevent being wrongly blamed for incompetence...). More concrete information on new CU or SP release dates could help accepting a current sub-optimal situation.
It proves in my view that Microsoft is still invested in on-premises deployments and not chasing customers in the cloud because on-premises deployments have become too difficult.
But it is also possible that customers see/hear/read about issues with Exchange 2013 (whether they are correct or not) and hesitate to move to Office 365 as it is relatively well known on-premises shares the same code base as the cloud version.
Basically, on-premises Exchange is still very important for Microsoft and certainly for those IT-Pro's that design, implement and administer them. I do believe that with a bit more effort you could help IT-Pro's a lot.
These where my 2 cents and I hope you appreciate my attempt to reply with constructive comments/criticisms and that you find them helpful.