Transferring an Azure subscription to a new tenant can be a complex process. I recently followed the instructions from How can I move a subscription to a new tenant? to move an Azure subscription to a new test tenant. However, the new test tenant was not appearing in the list of tenants I could move the subscription to. I realized that the account I was using needed to be a global admin in both tenants.

I had to set up a new developer tenant as my previous tenant became unusable due to an expired Visual studio subscription. Fortunately, there is plenty of help and documentation available to guide you through the process. Here’s a step-by-step guide on how to get started with the Power Platform Developer Plan. Steps to Enable the Power Platform Developer Plan Sign Up: Visit the Power Apps Developer Plan website. Click on the “Start free” button.

Sharing is a great feature for collaboration. However, depending on how items, files, or folders are shared, a sharing link might be created or unique permissions on these items are created. It is possible to set an expiration date on sharing links in SharePoint and OneDrive. For more details, please refer to How to set an expiration date on sharing links in SharePoint and OneDrive. Microsoft introduced the capability to set an expiry date for all types of sharing links: “Anyone”, company-wide (aka.

Sharing is a powerful feature for collaboration. However depending on how items, files or folders are shared, a sharing link might be created or unique permissions on these items are created. The sharing link is created when the copy links is clicked from the sharing pop up options when people other those already have existing access are picked. However by default, if sharing options have not been configured, links to “People in ” or “Anyone” (if external sharing is allowed) is selected

Introduction Microsoft Teams offers private and shared channels as specialized collaboration spaces to cater to different organizational needs. While these channels provide enhanced security and collaboration features, they come with specific limitations and management challenges, particularly around the associated SharePoint sites. This post covers some limitations, and management tips for SharePoint sites associated with private and shared channels, including PowerShell hacks and governance practices to overcome these challenges. Managing SharePoint Sites for Private and Shared Channels SharePoint sites associated with private and shared channels are special types of sites with the limitations as identified by Gregory in his blog post Why you should never mess with Private and Shared Channel SharePoint Sites related to the inability to attach to a hub directly, being accessible from the Teams interface mainly, and inability to manage permissions at the site level, and with constrained external sharing.

Introduction It is possible to create M365 Groups and Teams with the same name, and there is currently no built-in way to prevent this. The new Team/Site/M365 Group is created with a random number appended to the Team name for the SharePoint site and m365 Group email address. Having duplicate names can cause confusion and increase risks, including: Wrongly Granting Permissions: Users may accidentally grant permissions to the wrong M365 Group or Team, leading to unauthorized access.

Introduction Renaming the ‘Files’ tab in Microsoft Teams to something more meaningful for your business, such as “All Access,” can enhance user experience. It can help to differentiate other document libraries added as tabs. The Files has been renamed to Shared for chats to show all the files and links that were sent in the chat, making it easier to find them- all in one place. However, it is not possible to rename the Files and Posts tabs from the UI within channels.

Introduction There are situations where you might want to reuse the M365 Group principals to assign permissions to other sites without creating additional Entra ID groups. This can be useful for: Adding M365 group members to a SharePoint site, such as an intranet site for ‘Human Resources’ managed by the ‘Human Resources’ M365 Group/Teams or a hub site managed by a ‘Service Desk’ M365 Group/Teams. Adding M365 group members to custom or out-of-the-box SharePoint groups, such as adding particular M365 group owners or members to custom groups created for additional libraries within a different site.

Introduction Managing Microsoft 365 Group settings is crucial for maintaining a compliant and secure environment.PowerShell and Microsoft Graph can be used to configure various group settings, including naming policies, guest access, and more. As a regular user of PnP PowerShell, I aimed to replicate the functionality of the Microsoft Entra cmdlets for configuring group settings using PnP PowerShell. Example Script to Update naming policy Settings The following PowerShell script updates the naming group settings using the Microsoft Graph API and PnP PowerShell.

Introduction Thanks to Kinga Kazala for her timely article Deploy SPFx app using pipeline’s Workload Identity federation, which showcases how to use Workload Identity Federation to alleviate the need for using Entra app secrets or certificates. This method simplifies the setup process, especially when there’s reliance on a single person who might be unavailable. We initially set up the SPFx pipeline for the Test environment using certificates with CLI for M365.