Azure

Commands to force password change for users in Microsoft 365 by using Microsoft Graph Powershell

Introduction And the time has arrived. Many months after having read Flavio Copes’ amazing post about the value of a boring stack I’ve finally moved my blog from Wordpress to Hugo

Introduction This is a request coming from Discord: how to send an email through Graph API if the local disk is full? Preparing requirements Create the application and apply the Mail.

One interesting challenge that a recent request via Discord brought was how to handle secrets for automated/unattended processes on onpremise machines. My initial interest in the Powershell Secret Management module slowly waned as I realized that it’s not really meant for that purpose (though it can be made with a command) so I started wondering if it would be possible to actually have that working through Azure Keyvault in an easy manner.

Disclaimer: This review was written following 7 weeks with a review sample of the book provided by the publisher. The publisher had no early preview, copy approval or editorial inputs of any kind and it provided no compensation in exchange for the review.

Since Microsoft is set to deprecate the Azure AD Powershell cmdlets soon™ I’m taking the opportunity to upgrade some scripts I’m using from AzureAD to Graph API, and the one showcased today is the script to add Graph API permissions to an Azure AD Application.

During the labbing in preparation for the AZ-140 exam next week I hit one particular issue which required the updating of the FsLogix clients on the AVD hosts, but as usual I’m way too lazy to do that manually in 10 minutes, so instead I spent a few hours building a script to do it automatically!

So, the initial idea of this project was to do what Lansweeper hasn’t done in years and try to modernize the Lansweeper solution by running parts of it in PAAS/SAAS environments.