Following up on my previous post of the retirement of vibe.powerapps.com and Copilot App Builder, Microsoft announced two additional deprecations coming up soon. The first is Dataverse for Teams and the second is the unmanaged developer environments and the Power Apps Developer Plan.
A couple of days ago, Microsoft announced the retirement of the App Builder agent in Microsoft 365 Copilot and the vibe.powerapps.com experience in Power Apps. Both of these are scheduled for retirement on November 30, 2026.
There has been a big hype lately about creating a complete Dataverse solution including tables, relationships, a model-driven app, security roles and web resources. In this post I will go through the steps of doing this. The experience might be slightly different for different users and scenarios, but overall we should be able to achieve the same results.
Starting this month, August 2026, Microsoft will deprecate the use of the wildcard value (*) in the webapi/
Until recently, if you want to invoke Server Logic from within Power Pages, this would have to be done on the client side using http requests and manipulating the data on the client side or by a limited set of predefined set of platform-provided objects. Yesterday, August 11, Microsoft announced the ability to invoke Server Logic directly from within Power Pages.
If you recently logged in to your Canvas App builder, you might have noticed that there are a few new screen templates that you can choose from when creating your app. These new screens, which are built with the Modern controls simplify the process of creating new apps, and the layouts are completely responsive.
In this post, I will demonstrate a new concept called MCP Apps and show how to build an Interactive Widget in Power Apps and use it in Copilot. This is game changing as Copilot will no longer be limited to only text based responses, but can provide you the response as a UI component.
The Power Platform Center of Excellence Started Kit has historically been a comprehensive reference implementation that demonstrates how to build sophisticated governance, monitoring, and adoption capabilities using Power Platform’s native low-code tools. This collection of components and solutions was there to help develop a strategy for adopting and supporting Power Platform while showcasing what’s possible with the platform’s out-of-the-box features.
Using and Interacting with the Dataverse MCP Server in Copilot Studio can be easily done using the step-by-step instructions in this article. This article details how to interact with the Dataverse MCP using Copilot Studio, however other tools such as Github Copilot and Claude can be used to interact with this MCP server as well.
In a recent article I wrote about creating a code app and using a Dataverse table to populate data into the code app. In this post, I will go over adding actions, functions and cloud flows and calling them from your code app.
