In a previous blog post, I showed a way to retrieve all the Microsoft Services FQDNs, ports, and IP-Addresses. Nice to know those in secure environments where not everything is allowed to go onto the internet, but how can you test if they are accessible? This blog post will show how to test most of these services using PowerShell.
I have been doing a lot of Exchange on-prem to Exchange Online migrations over the last few years, because of that I use mxtoolbox.com a lot for querying MX, SPF, DMARC, and DKIM records. Wouldn't it be convenient to get a simple overview of those records in a PowerShell function? This blog post will show you how 🙂
Things are changing... The Azure AD and MSOL modules will be getting a deprecated status, this was initially set for June 2022 and now that has been postponed until after December 2022. You need to start updating scripts, be prepared for that. In this blog post, I wanted to show you a way to collect all the new cmdlets and show their description, synopsis (A brief summary), and the help URL for more information.
We have all been there, you're working on something (Microsoft Endpoint Manager for example) and things don't work like they are supposed to. Strange errors, you're starting to doubt yourself... And then you see something in your newsfeed (Twitter, LinkedIN, etc.) that there's an issue and that Microsoft is working on it... You lost a few hours troubleshooting your issue, wouldn't it be nice to get notified when starting PowerShell if there's an issue that you should be aware of? This blog post will cover just that 🙂
There are many licenses you can add to your 365 tenant, but it's difficult to get a good overview of all users with their assigned licenses and what each license plan contains. I wrote a PowerShell script for that, it outputs all the users with their assigned SKU (Short for Stock-Keeping-Unit, but in Microsoft terms a license SKU predefines all the properties of a license, including Product/Version/Features) in a CSV file.