In a December 24 announcement, Microsoft says that the roll-out of DNSSEC and DANE support in Exchange Online will start in mid-January 2022. Because this is a big change for the Exchange Online infrastructure, Microsoft is using a phased deployment which won’t complete until mid-May. Support for DNSSEC and DANE has been coming for a long time, but it’s good that the extra security which these standards bring will be available to Exchange Online tenants.
About Tony Redmond
How to Use Office 365 Audit Data with Microsoft Sentinel
Microsoft Sentinel is Microsoft’s log aggregator. Along with other data, Sentinel can ingest events from the Office 365 audit log. Once ingested, we can visualize the data through workbooks. If you have an Azure subscription, it’s surprisingly easy to take advantage of the 31-day trial to see if Sentinel can do a job for your organization. Follow our steps and you’ll be visualizing quickly.
Five New Year Resolutions for Microsoft 365 Tenant Administrators
The Microsoft 365 ecosystem is a big place and it’s hard to keep on top of everything. But to start 2022 off with a bang, here are five areas for tenant administrators to consider when they plan how they’ll spend their time in the new year. As always, feel free to disagree and add comments describing what you plan to do in 2022.
Can Azure AD Custom Security Attributes Replace Exchange Custom Attributes?
Microsoft launched the preview of Azure AD custom security attributes on December 1. Custom attributes are well known to Exchange administrators. In this article, we look at how to create and add Azure AD custom security attributes, how to transfer data from Exchange to Azure AD, and how to retrieve information from the attributes. Azure AD custom security attributes have some advantages, but they also have some downsides.
Engineering Snafu Causes Mail Delays for Exchange Server
A version checking problem for malware engine signature files caused on-premises Exchange servers to fail to process inbound email. The issue appears to be due to a date validation problem caused when the checking routine couldn’t deal with 2022 when the new year rolled around. Microsoft fixed the problem, but the issue poses questions about Microsoft’s commitment to on-premises Exchange Server.