Introduction The PAT(Personal Access Token) is the Azure DevOps personal access token which can be generated from your account settings and used for authentication when performing Git operations. Cons using PATs Not conducive for teamwork: If the PAT belongs to a team member who leaves the organization, the release manager or another team member will have to generate their own PAT and update the pipeline. Security risks: Similar to a password, a PAT poses risks if leaked.

In the Power Platform Admin Center, you may have added app users that you no longer need. To view the list of app users added to an environment, navigate to the following URL https://admin.powerplatform.microsoft.com/manage/environments/c1725b9e-0000-0000-0000-000d3ad0000/appusers, replacing c1725b9e-0000-0000-0000-000d3ad0000 with your environment ID: To delete an app user, click on the ellipsis (…) next to the app user and select the Delete button. However, you may encounter a misleading error message: ✖ Failed to delete app user: User with SystemUserId= is not disabled.

Introduction When setting up your Azure DevOps pipeline for deploying a Power Platform solution, you may encounter an error message if your solution relies on connection references. The reason given was : An unexpected error occurred. This generic message does not provide much help and can occur for multiple reasons. In my scenario, it was related to the connection references in the target environment not being shared with the service principal.

Introduction Microsoft Teams provides a unified platform for end users to collaborate on files stored within SharePoint. However, there are notable differences between the two platforms that can influence your decision on when to use SharePoint and when to use Teams. Search Functionality Contextual Search Contextual search on libraries does not exist within Teams, while SharePoint offers richer contextual search at library, site, organization, and hub levels. Issue with Results from Shared Channels There is an issue searching contents within shared channels where the shared channel name is shown as Mock Team Name which is not helpful identitying the source of the search results without opening the file.

Client secrets have traditionally been the go-to method for deploying Power Platform solutions from Azure DevOps, utilizing app registrations from the Azure platform. However, my personal experience has shown that this approach can be problematic, especially when you are not an application admin. It often involves wasting time figuring out why deployments have failed due to expired or missing client secrets. Even when reaching out to someone with application admin rights, they might generate a new client secret but forget to update the service connections for each service connection within Azure Dev Ops or the application admin does not have access requiring to reach out to someone else who have access, causing further disruptions.

My Visual Studio subscription was deactivated, resulting in the loss of my Azure subscription and licenses to access Microsoft Teams within my M365 developer tenant. This post covers my attempts to recover access in vain. Access to Microsoft Teams I thought I could extend my access to Microsoft Teams by opting for a free trial for Microsoft 365 E5 (no Teams) and Teams Premium - Microsoft Teams Premium. However, this did not restore access to Microsoft Teams despite waiting multiple hours after I added the above licenses.

When you create an Agent within Copilot Studio, a corresponding App registration is automatically generated. These app registrations are named after the Agent, suffixed with “(Microsoft Copilot Studio)”. You can view these app registrations in the Azure Portal under App registrations > All applications. Agent Certificates and Federated Identity Each app registration associated with a Copilot Studio Agent includes three certificates and two federated credentials as of January 2025. These components enable secure communication between agents and your data sources and services.

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.

Introduction Taxonomy feature is not activated by default in SharePoint sites linked to a private or shared Teams Channels. When attempting to add content types with managed metadata columns, you may encounter an error message stating “Taxonomy disabled”. To resolve this issue, you can enable the taxonomy feature with the ID 73ef14b1-13a9-416b-a9b5-ececa2b0604c using the PowerShell cmdlet Enable-PnPFeature before adding the content types to the sites with the template TEAMCHANNEL#1. Script to check whether feature taxonomy is enabled Get-PnPFeature -Scope Site | Where-Object { $_.