From Screen Builder to Solution Engineer in Dynamics 365
The Power Apps Vibe experience and Code apps point to a real change in focus for the D365 and Power Platform developer.
Vibe brings more of the early solution work into AI. Microsoft describes it as an AI-native experience that can build requirements, data, and full apps with generated code from a business prompt. Code Apps moves in another direction at the same time. It gives developers a code-first way to build custom web apps that still use Power Apps capabilities. They can develop locally in tools like Visual Studio Code, use frameworks such as React and Vue, keep full control over the user interface and logic, and run the same app in Power Platform.
That is a meaningful shift. But for D365, it does not mean the model-driven core is fading away.
In D365, model-driven apps are still central. They are still created in the Power Apps maker portal, typically inside solutions. You still use the app designer in make.powerapps.com, where you create the app, add Dataverse tables, design navigation, and save and publish the result. Solutions also remain the mechanism for Application Lifecycle Management across apps and components in Power Apps and the wider Power Platform.
That means familiar model-driven building blocks do not go away. Views do not go away. Forms do not go away. Business Rules do not go away. Business Process Flows do not go away.
So, the right conclusion is not that AI replaces the D365 application pattern. The better conclusion is that AI changes the work around that pattern.
The biggest practical change is that first drafts move earlier into AI. More of the initial requirements shaping, solution framing, data modeling, and app drafting can now happen through Plans and Vibe. That should reduce the time spent manually assembling the first cut of an application. But it also raises the importance of judgment. Someone still has to decide whether the generated tables are right, whether the process makes sense, whether the security model is sound, and whether the app fits the real business need.
Recommended by LinkedIn
At the same time, pro-code becomes more important with Code Apps. Microsoft is not moving only toward AI-generated low-code only as with Vibe. It is also strengthening the code-first path. That means the modern Power Platform developer may need to be more comfortable with TypeScript, React, repository workflows, code review, and custom web experiences than many expected a year ago.
Classic D365 customization also remains important. Solutions still matter. Packaging still matters. ALM still matters. And richer extensions still need serious custom work. So the future is not “AI instead of real development.” It is AI on top of real development, with the model-driven core still carrying much of the business application load in D365.
There is another change as well. Agents and tool-connected experiences are becoming part of normal solution design. In Copilot Studio, tools are treated as building blocks, and generative orchestration can automatically select tools, topics, or knowledge to respond to a user. That pushes more developers to think not only in terms of tables, forms, and workflows, but also in terms of actions, tools, grounding, and orchestration.
In summary, for D365, the role is not moving away from model-driven apps. It is expanding around them. Less time on low-value first drafts. More time on requirements shaping, data modeling, integration thinking, review of generated output, extension design, ALM, security, testing, and architectural judgment.
That is the real shift. The D365 developer is still building on the same core platform. But the focus is becoming broader, more architectural, and more code-literate at the same time.
See:
