Dynamicsgpblogster

For most of 2026, a generative page in a model-driven app was a one-way street. A form script could open one inline or as a dialog and hand it a record ID or a bag of custom data, but nothing ever came back: when the dialog closed, the promise resolved with nothing in it. And the obvious other place to put a page, the side pane next to the form, sat in the documentation ...

Put an unquoted colon in the description of a Copilot Studio skill and nothing will tell you. Copilot Studio skips the skill, loads the rest of the agent, and the agent carries on as though the skill had never been installed. That isn't a bug report, by the way: it is documented behavior, spelled out in a troubleshooting table that lists eight reasons a skill gets skippe...

Copilot Studio agents built on the GitHub Copilot harness can now run one of your workflows before every tool call, and that workflow is allowed to say no. The feature is called hooks, it arrived in preview at the end of September, and it answers the question a governance reviewer eventually asks about any generative agent: "how do I make sure the agent always<...

A generative page is React code that an agent wrote on your behalf. Which means that the first time one fails in front of a user, somebody is going to be debugging code they did not write, from a bug report that says "the page is blank", with no telemetry of any kind to go on. That was the situation until the end of September, when the generative pages documentation pick...

Back on September 4th I wrote about the model app builder, the Power Platform plugin that stands up a model-driven app from a description instead of from four hours of clicking. I said at the time that the interesting thing was not the...