Lots of excitement was generated when Guardicore revealed a purported vulnerability with the Exchange Autodiscover service. However, the almost total lack of detail about the configuration used for testing and to generate the reported results makes it impossible for Exchange administrators to check the theory against their own deployment. I don’t think a problem exists with Exchange Online, but it’s possible that poor DNS practice or flawed third-party clients could cause an issue with on-premises servers. The case remains to be proved.
The Microsoft Graph SDK for PowerShell exists to help developers use Graph API calls from PowerShell. It works, but like anything in life, there’s a right way to connect and use the SDK and a wrong way. In this article we explore topics like how to connect to the right tenant, how permissions are managed (or not), and why running Graph SDK cmdlets interactively isn’t something you should do in production. Good as the SDK is, Microsoft has some big issues to solve to address some obvious security issues.
From November 1, 2021, Microsoft requires Outlook 2013 Service Pack 1 (with fixes) as the minimum client version to connect to Exchange Online. Given all the publicity about attacks against the on-premises version of Exchange earlier this year, it’s a wonder why organizations continue to allow people to use outdated client software to connect to Exchange Online. In any case, the drop-dead date is November 1. If you have any old Outlook 2007, Outlook 2010, or Outlook 2013 (before SP1) clients, it’s time to start upgrading.
Microsoft plans to retire the now-decrepit and very old EAC on September 1, 2022. The old console has hung on too long, perhaps because Microsoft hasn’t progressed the development of its replacement as quickly as they could have since its 2019 debut. Although Microsoft claims that the new EAC reached feature parity with the old some time ago, any examination of the two consoles proves that this is not the case. With that in mind, it seems like Microsoft has some work to do to make everything ready for the big retirement date in 2022.
On June 30, 2022, Azure AD and Microsoft Online Services cmdlets will stop working for license management. The result is that you need to upgrade PowerShell scripts which use these cmdlets. The choice is to use Graph API calls or cmdlets from the Microsoft Graph PowerShell SDK. In this article, we explore the steps necessary to upgrade a script to remove service plans from an Office 365 license (SKU).