Introduction Managing the lifecycle of Microsoft 365 Groups is important to prevent accidental deletion of M365 Groups. It is a good practice to set lifecycle expiration policy to control sprawl. However that means that the group will get automatically deleted after they expire. The Teams/M365 groups owners will get email notifications to renew within a certain timeframe , however if the owners missed the renewal notifications for different reasons, it may lead to accidental data loss.

Introduction Have you ever encountered a stubborn Power Automate flow that won’t open in the new designer? For a long time, I stuck with the classic designer due to issues I faced with the new designer. However, I recently decided to make the switch for these reasons: New Power Automate features will only be available in the new designer Microsoft will get rid of classic designer Future proof flows as they might not be editable if classic designer is gone unless Microsoft caters for incompatible action schemas In this blog post, I’ll share my experience and the steps I took to transition from the classic designer to the new designer in Power Automate.

Introduction With the release of SPFx 1.20.0 in September 2024, I decided to upgrade an existing SPFx solution to the latest version following a post by Microsoft 365 & Power Platform Community on Linkedin This process can be challenging, especially when dealing with dependency version conflicts. In this blog post, I’ll walk you through the steps to upgrade your SPFx solution to version 1.20.0, including installing Node.js 18.18.0, using the CLI for Microsoft 365 to generate upgrade instructions, and addressing common issues.