Knowing what agents are configured to do is one thing, but organizations also need to know how to monitor agents at runtime. Knowing what users are actually saying to those agents, what data they are Read more
Sharing and deploying agents in Copilot Studio is one of the most frequently misunderstood topics in the platform. The official documentation covers the essential, but it leaves several important behaviors unexplained, particularly around permissions & Read more
“Chat Sessions”, “Messages” and then “Copilot Credits”, Copilot Studio licensing has gone through a few iterations already. Let’s summarize the different options available, when each makes sense and how to report and monitor consumption. This Read more
Copilot Studio is evolving fast, but governance and visibility capabilities haven’t kept up. The Copilot Studio Monitor fills critical visibility gaps by surfacing the configuration of every agent in a structured data model extended from the CoE Read more
Configuring the Power Platform tenant settings properly is one of the simplest (and most overlooked) ways to strengthen governance and security. Yet, many organizations still end up with configuration drift or outdated defaults that expose Read more
I shared my thoughts on the CoE Starter Kit a while ago. Long story short: it’s a great foundation, a toolkit to build on and adapt to your organization’s needs. Microsoft recommends upgrading the kit Read more
What’s with the Endpoint Manager? I recently shared the Endpoint Collector, an extension of the CoE Kit which allows CoEs and Admins to report on the Endpoints configured with the HTTP connector in Cloud Flows. Read more
Monitoring Endpoints configured in the HTTP connectors in Cloud Flows is key to safely govern the Power Platform and prevent data leaks. I share a reusable solution for it!
This is probably one of the most recurring topics in the Power Platform: Licensing. Instead of discussing the various plans available, or whether making Managed Environments more accessible could actually bring more benefits to both Read more
One of the key requirements for any platform governance is visibility. For an organization to be able to govern the usage of any technology, they will need visibility over it. For this, they will need Read more
I previously shared this Copilot Studio Governance article where I explain that I did not find any suitable and out-of-the-box-solution to programmatically delete Copilot Studio Bots as Admin. For us, responsible for the Power Platform Read more
It is sometimes necessary to use the Dataverse API to perform operations on an environment. It can be necessary when integrating with other third party applications, or even from within the Power Platform itself when Read more
As the Power Platform adoption continues to grow, many organizations start to adopt governance and operational models involving other teams. Indeed, it becomes increasingly hard for CoEs to manage everything themselves in large organizations. And Read more
I share a reusable solution which Admins can use to change Canvas App and solution-aware Flow Owners programmatically. Not complicated, but pretty handy for Power Platform CoEs and Admins! Why Changing App and Flow Owners Read more
This is the complete Copilot Studio governance reference for Power Platform admins and CoE teams. It covers monitoring, restrictions, maker management, and common governance scenarios, with direct links to the controls that matter and the Read more
This topic is close to my heart, as it is key when working in a Power Platform CoE. How can we centrally manage reusable components, such as Component Libraries, Custom Connectors, or Child Flows, and Read more
In this post I am sharing some comprehensive self-pace labs to learn about Dataverse in a learn-by-doing approach. If you have been reading the other posts on this blog, you might be thinking that this Read more
I feel quite passionate about this topic, partly because the absolute “Best Operational Model to Govern the Power Platform” does not exist. It is likely to exist for each organization, but not likely to be Read more
If you are responsible for the Power Platform Governance in the organization then you need to be able to monitor the platform usage and consumption. Some of this reporting is easily accessible from the Power Read more
Following the positive feedback I received from the DLP Policy Toolbox, I decided to share another app with the community: the Ownership Toolbox. It is often that admins have to manage apps and flows ownership. Read more
The Power Platform Governance functionalities are slowly but surely ramping up to something satisfying for Admins, CoEs and Governance teams. One of the key components from that range of functionalities is the DLP Policies. Even Read more
Have you ever seen the Power Apps consent popup below when you open a Canvas App for the first time? Yes, I am sure you did. And who else did? Everyone who ever used a Read more
People sometimes ask some general advice for organizations wanting to leverage the Power Platform and establish a robust governance. I am writing this article to sum up what I usually say! Define Responsibilities with Dedicated Read more
Setting up some key tenant restrictions is a good starting point to establish a robust Power Platform governance in a secure way, as suggested in this other post. Carefully assign the Power Platform Tenant Administrator Read more
“I wish our Makers would clean up what they do not use!”…. Have you ever heard that from an Admin? I have… I have also seen the suffering caused by having too many Flows and Read more
The Center of Excellence (CoE) Starter Kit is a kit provided by Microsoft. It consists in a set of solutions to support admins and CoEs to govern the platform in their organization. The kit is Read more
AI Builder is a fantastic capability and is getting more and more traction with the fast development of Large Language Models and the recent addition of the AI Builder OpenAI model. However, the way to Read more
Microsoft introduced the so called “Power Platform request limits”, previously referred to as “API calls”. This concept can provoke headaches to both admins and makers trying to understand the potential impact for them. In this Read more