11th MVP Award Rewarded

on
I am actually on vacation, but as I sit here under the summer sun, toes in the pool and a cold drink within reach, I have been waiting for that email confirming that I’ve been awarded my 11th Microsoft MVP Award! As last year, I am being awarded in both the Teams and Copilot category. To say I’m humbled would be an understatement. Being part of the global Microsoft MVP community for over a decade now has been an incredible journey, filled with learning, sharing, speaking, and connecting with passionate technologists from every corner of the world. What is the Microsoft MVP Award? The Microsoft Most Valuable Professional (MVP) award is given to technology experts who share their knowledge and real-world expertise with communities. With fewer than 4,000 MVPs worldwide, it’s an honor to be part of such a vibrant and dedicated group. MVPs contribute through speaking engagements, writing, open-source contributions, and helping others online and offline. You can learn more about the progra...

New Microsoft Loop workspace policy coming: Require Existing Microsoft 365 Group for New Loop workspaces

on

Microsoft is improving the security of Loop workspaces by giving admins the capability to connect new workspaces into existing Microsoft 365 Groups. This change will allow end-users to choose existing groups for managing new workspaces, providing a structured environment for collaboration. While this integration supports governance, it may challenge scenarios like automatic aggregation of Teams meeting content into a Loop workspace or creating short-term project workspaces. I recommend reading the following post on how aggregating teams meeting into loop workspaces works.

If organizations have separate workflows for creating and govern Microsoft 365 groups, now would be the time to look into them and see if they need to be updated to include Loop Workspaces (or allowing to add workspaces)

This update is currently planned to be complete by the end of April 2025 but keep an eye on Microsoft 365 Roadmap ID 422725 for changes.