Introduction When you share a Power Automate flow with other users, especially flows that include actions like “Send an email”, you unintentionally grant them access to your personal connection. If you share a flow that uses your Outlook connection, the other user can leverage your connection in their own flows. This means they could: Read your user profile Read, update, and delete your emails Send mail as you (the signed-in user) Create, read, update, and delete calendar events Create, read, update, and delete contacts Security Risk Sharing flows without considering connection permissions can expose your account to unintended actions or even compromise your data.

Introduction When managing Microsoft Teams via PowerShell, you may need to assign a user as an owner of a specific channel. However, attempting to add a user directly as an owner can result in an error if the user is not already a member of the channel. Example Error: Add-TeamChannelUser -GroupId $t.GroupId -DisplayName TestPermission -User AdeleV@4g6zf4.onmicrosoft.com -Role Owner Add-TeamChannelUser: Failed to find the user: AdeleV@4g6zf4.onmicrosoft.com on the roster of channel: TestPermission.

Introduction Document Sets in SharePoint are a powerful way to manage groups of related documents as a single entity. They enable you to apply metadata, workflows, and permissions to a collection of documents, making them ideal for project folders, case files, or any scenario where you need to keep related content together. This post shows how to automate the configuration of Document Sets across multiple libraries using PnP PowerShell. Why Use Document Sets?