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 DevOps or the application admin does not have access requiring to reach out to someone else who have access, causing further disruptions.