After figuring out how to convert a script from using Azure AD licensing cmdlets (due to stop working in June 2022), we move on to create a licensing report for a tenant using cmdlets from the Microsoft Graph SDK for PowerShell. The code is pretty straightforward, but you need to do some up-front work to extract and prepare some input files containing product and service plan codes. Given that Microsoft is increasing its license fees, it’s a good time to report this information…
An interesting and worthwhile interview (available on YouTube) with security researcher Amit Serper reveals a lot more detail about the Autodiscover credential leak reported by Guardicore last month. The interview (with three Office 365 MVPs) goes through the collection of leaked credentials, how Serper tried to reproduce the problem, and his interaction with Microsoft. It’s a real pity Serper didn’t include the information in his original report as it would have taken a lot of heat out of the situation.
Microsoft plans to remove the management of Exchange transport-rule based policies from the classic EAC in mid-2022. Given that Microsoft 365 DLP policies offer the same if not better functionality for Exchange Online and can process other workloads as well, it’s a good time to consider transitioning away from the older technology. Microsoft is obviously not putting any engineering effort into Exchange-based DLP, so there’s no good reason not to move over and use the technology they are investing in, The transition will take time and effort, but it will be worth it.
Along with the general availability of a new Graph Export API for Teams, Microsoft is introducing new licensing and charging models. Understanding the charging incurred for different uses will take some time to sort out and could pose real challenges for ISVs working in the migration space. Developers need to understand terms like model A and model B, seeded capacity, and consumption units and how these apply to their apps. The question now is if this is a test bed for Microsoft to apply similar charges to other APIs.
On November 1, Microsoft will limit auto-expanding archives to 1.5 TB and bring the era of “bottomless archiving” to an end. The new limit might not affect many Exchange Online tenants, but it’s a wake-up call for administrators to check how archiving is used in their tenants. To help the process, we’ve written a PowerShell script to report the current set of user and shared mailboxes with archives.