I used the Send-MailMessage cmdlet a lot in the past for testing Receive Connectors in Exchange or for emailing reports in scheduled PowerShell scripts. When you try to use the Send-MailMessage cmdlet, it has been showing you this message for quite a while now: WARNING: The command 'Send-MailMessage' is obsolete. This cmdlet does not guarantee secure connections to SMTP servers. While there is no immediate replacement available in PowerShell, we recommend you do not use Send-MailMessage at this time. See https://aka.ms/SendMailMessage for more information. In this blog post, I will show you the new way of sending emails using Send-MgUserMail. Note: This works for Exchange Online, not for local Exchange installations or any other service running SMTP.
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 🙂
One of our customers is switching from Mobile Iron to Endpoint Manager for their mobile devices, a good choice :). After retiring the device, Mobile Iron removes the managed Authenticator app from the device. Endpoint manager pushes it back to the device again but... The iCloud backup options were not set/managed and users have to add their account back which requires MFA. Which they can't do because only the Authenticator app was registered (Mobile app code) and no recovery email or mobile phone number. But the mobile phone numbers were set on most users in Active Directory in the past and were synced to Azure AD, this blog post describes how you can add those numbers to the affected users so that they can use the recovery option and won't have to contact the ServiceDesk 🙂