Summary Build autonomous agents that respond to email queries and generate dynamic Adaptive Cards. Use prompt tools to break down complex instructions into manageable, reusable components. Send personalized, interactive content directly via Outlook email. Learn formatting requirements and best practices for Adaptive Cards in email. Table of Contents Introduction Why Dynamic Adaptive Cards via Email Using Prompt Tools to Manage Instructions Building the Holiday Planning Agent Processing Email Queries Adaptive Card Formatting for Email Demo: Holiday Query in Action Key Takeaways References Introduction Copilot Studio enables makers to create intelligent agents that go beyond the chat interface.

Summary Autonomous agents run in the background without user prompts, so they cannot ask users to sign in during execution. Use maker-provided credentials for tools; user credentials are not appropriate for autonomous scenarios. Apply least privilege and restrict tool actions to reduce data exposure and abuse. Communicate the “runs under author’s identity” warning and govern access like any service account. Table of Contents Why Authentication Matters Autonomous Agents: What Changes Authentication Models Configure Tool Authentication Restrict Tool Actions Publishing, Warnings, and Governance Best Practices Checklist Why Authentication Matters As organizations adopt autonomous agents to perform tasks and make decisions, authentication becomes a core control.

Summary Error AADSTS650057 Invalid resource occurs when https://service.powerapps.com isn’t included in the app registration permissions for PnP.PowerShell. Fix by adding the Power Apps Service API with user delegated permission in Entra ID. Optional: add the permission through the app manifest with requiredResourceAccess. Symptom If https://service.powerapps.com from the entra ID used in PnP PowerShell is missing, you’ll see an error similar to: Get-PnPPowerApp: AADSTS650057: Invalid resource. The client has requested access to a resource which is not listed in the requested permissions in the client’s application registration.

When automating Copilot Studio agents or building custom integrations, you need to grant your Entra ID app registration the proper Power Platform API permissions. However, the Power Platform API often doesn’t appear in the standard API permissions list in the Azure Portal. This guide shows you how to enable the Power Platform API service principal and add the CopilotStudio.Copilot.Invoke permission to your app registration. Table of Contents The Problem Why Power Platform API is Missing Prerequisites Solution Overview Step 1: Verify Power Platform API Status Step 2: Enable Power Platform API Service Principal Step 3: Add API Permissions to Your App Step 4: Grant Admin Consent Alternative: Manual Manifest Configuration Verification Conclusion References The Problem While setting up automated testing for Copilot Studio agents using the Copilot Studio Kit (inspired by Matthew Devaney’s excellent video Copilot Studio Test Automation: STOP Testing Manually!

The Copilot Studio Kit is a powerful tool for managing and testing copilots in Microsoft Power Platform. However, installation requires the Creator Kit as a prerequisite dependency. This guide walks you through the complete installation process, including resolving common dependency issues. Table of Contents Overview Prerequisites Understanding the Dependency Installation Steps Step 1: Install Creator Kit Core Step 2: Install Copilot Studio Kit References Overview The Copilot Studio Kit is a managed solution that provides components and utilities for building, testing, and managing copilots in Power Platform.

Table of Contents Problem Statement Solution Overview Prerequisites Implementation Guide Step 1: Get Site and List IDs Step 2: Test with Graph Explorer Step 3: Initial Search Implementation Step 4: Handle Pagination Complete Code Examples Performance Considerations Conclusion Problem Statement After importing 10,000+ records into SharePoint using Power Automate bulk import techniques, we encountered Power Apps delegation limits that prevented effective searching and filtering of large datasets. There is the option of using Power Automate to get the results, however it adds more artefacts to a simple app designed for search.

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.

Introduction When building agents in Microsoft Copilot Studio, you’re faced with a fundamental choice: Classic Orchestration or Generative AI Orchestration. Understanding the differences between these approaches is crucial for making the right architectural decision for your chatbot project. Enabling Generative AI unlocks dynamic capabilities where responses are intelligently crafted using available tools and knowledge sources as needed. In contrast, Classic Orchestration restricts responses to only the predefined content and behaviors explicitly configured in your agent’s topics.

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 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.

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 In Power Automate/Power Platform, environment variables within solutions are essential for managing and configuring flows across different environments. However, there is no direct way to declare an environment variable as an array. This blog post will cover how to use JSON to store arrays as environment variables, enabling you to manage complex data structures efficiently. Available Environment Variable Types Power Automate offers various types of environment variables you can select and configure:

If it takes too long to deploy the solution, time out issues might occur. In this instance consider checking and updating the MaxAsyncWaitTime. Its value has been increased to 120 which means the deployment process will wait up to 120 seconds (or 2 minutes) for asynchronous operations such as import power platform solution to complete fixing the timing out issue. The fix is to amend the MaxAsyncWaitTime to 120 - task: PowerPlatformImportSolution@2 inputs: authenticationType: PowerPlatformSPN PowerPlatformSPN: 'powerplatform-t-connection' Environment: 'https://contoso-st.

Guide to Preparing setting files for Power Platform managed solution deployment This guide will walk you through the process of creating a settings file for Power Platform managed solution deployment. Refer to the posts for more details to set up Application Lifecycle Management (ALM) for power platform: Power Platform ALM & Pipelines w/ Matt Devaney and Converting to Modern YAML Pipeline: Application Lifecycle Management in Azure DevOps for Power Platform for detailed steps for ALM for power platform solutions.

Overcoming Challenges with Azure DevOps Pipelines using Self-Hosted Build Agents for Power Platform Managed Solutions Application Lifecycle Management (ALM) for Power Platform solutions can be effectively managed using Azure DevOps, providing a robust framework for automating deployments, version control, and continuous integration and delivery, thereby enhancing productivity and reducing manual errors. Refer to the posts for more details: Power Platform ALM & Pipelines w/ Matt Devaney and Converting to Modern YAML Pipeline: Application Lifecycle Management in Azure DevOps for Power Platform

Power Platform Managed Solution Deployment with Connection References - Allow customisations This article explores the challenges and solutions associated with Power Platform managed solution deployment, specifically focusing on connection references and the “Allow Customisations” property. Refer to the posts for more details to set up Application Lifecycle Management (ALM) for power platform: Power Platform ALM & Pipelines w/ Matt Devaney and Converting to Modern YAML Pipeline: Application Lifecycle Management in Azure DevOps for Power Platform

Unable to find Power Platform in Azure DevOps Issue I was Unable to find the powerplatform in Azure devops Solution The solution is to install the Extension: Power Platform Build Tools (2.0.5) to Organisation. This will enable the Power Platform service connection. References Unable to find the powerplatform in Azure devops