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.

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.

Converting to Modern YAML Pipeline: Application Lifecycle Management in Azure DevOps for Power Platform There are loads of posts explaining Application Lifecycle Management for the Power Platform using Azure DevOps most using the graphical classical pipeline. The latest post I read on this is Application Lifecycle Management for the Power Platform using Azure DevOps by Luise Freese which is brilliant. Please read article covering difference between YAML and Classic UI to explain why you may want the modern YAML pipeline.

Coauthoring with power apps issues Coauthoring in power apps allows multiple power apps developers to work on the same canvas app. Despite being an experimental feature we decided to give a try to speed up the development process. We used the blog post [How To Setup Power Apps Co-Authoring - Azure Dev Ops Version] (https://www.matthewdevaney.com/how-to-setup-power-apps-co-authoring-azure-dev-ops-version/). The tutorial covers step-by-step instructions for enabling co-authoring for canvas apps in Power Apps using Azure DevOps repository.