Mailbox auditing seems like a pretty good thing to have in an email product, if only to answer the eternal question of who deleted a particular message from the mailbox. Exchange 2010 was the first version of the product to include mailbox auditing. The sad news is that not much has changed since in either the cloud or on-premises product, which is both worrying and not particularly good when considered in the context of Microsoft’s overall compliance strategy.
Last week I looked back on what happened in the world of on-premises and cloud Exchange during 2015. This week it’s time to consider what might come along in 2016. Of course, I don’t work for Microsoft, so anything outlined here is total speculation, all done in the best possible taste.
In two earlier posts I attempted to outline why a self-monitoring and healing capability is useful in software applications and provide an overview of how the Managed Availability framework provides these capabilities in Exchange 2013.