Low-code vs pro-code in Microsoft 365: why the conversation has changed

For a long time, Microsoft's pitch was straightforward: not every business problem needed traditional software development. With Power Apps and Power Automate, teams could build forms, workflows and internal tools faster, with less reliance on professional developers and more control in the hands of business users.

That shift made sense. SharePoint Online had moved away from many of the old customisation models that once gave developers broad freedom, and organisations still needed ways to extend Microsoft 365. Power Platform stepped into that gap and became the default answer for a huge range of "build it quickly" scenarios.

But in 2026, the old trade-off looks different.

AI coding agents are reducing the cost and friction of pro-code development. At the same time, many organisations are discovering that low-code does not remove complexity - it relocates it. Governance, environments, licensing, maintainability and long-term solution design still matter. So the real question is no longer whether low-code can replace coding. It is where you want your complexity to live.

Why Power Platform took off

Power Platform rose because it solved a real problem: demand for internal apps and automations was outpacing the supply of engineering time.

For business teams, the appeal was obvious:

  • build forms and approval flows quickly
  • connect Microsoft 365 services without heavy custom development
  • let power users solve local problems directly
  • reduce pressure on IT backlogs

In the cloud-first SharePoint era, this became even more important. As older customisation approaches became less viable or were gradually retired, Power Apps and Power Automate gave organisations a supported path forward inside Microsoft's ecosystem.

For many use cases, that worked well.

Where the low-code promise gets harder

The challenge is that "easy to start" is not the same as "easy to run well at scale".

As low-code solutions become business-critical, organisations start running into familiar engineering issues in a different form:

  • environment management
  • deployment and ALM overhead
  • hidden dependencies between flows, apps and connectors
  • governance and ownership problems
  • licensing surprises
  • difficulty reviewing and maintaining browser-built solutions cleanly over time

So while low-code reduced the need to write code, it did not eliminate architecture or operational discipline. It simply wrapped them in platform rules and admin controls.

What AI changes for pro-code

This is where AI coding tools shift the picture.

One of the biggest reasons organisations favoured low-code was that building custom solutions the traditional way felt too slow or expensive for many small and mid-sized needs. But that assumption is weakening fast.

With modern coding agents, developers can now scaffold a SharePoint Framework web part, build UI components, wire up APIs, generate tests, and prepare clean, reviewable code much faster than before. The coding itself is becoming less of the bottleneck.

That does not mean architecture, review, security and business understanding stop mattering. They still do. But the effort required to get a solid custom solution off the ground is dropping.

Why this matters in SharePoint and Microsoft 365

For Microsoft 365 teams, this reopens an important option.

Instead of defaulting to Power Platform for every app-like requirement, teams can now more seriously consider whether an SPFx solution or other pro-code approach might be better for:

  • richer user experiences
  • cleaner source control and testing
  • stronger reuse and maintainability
  • more predictable lifecycle management
  • better alignment with standard engineering practices

In other words, pro-code is becoming more accessible again - not because the platform changed, but because the economics of development changed.

So is low-code still useful?

Absolutely.

Power Platform still makes strong sense for lightweight forms, approvals, orchestration, quick internal tools and scenarios where speed and platform integration matter more than deep custom engineering.

But it is no longer as convincing to frame low-code as the obvious replacement for code.

AI is strengthening both sides: Microsoft is adding more AI assistance into Power Platform, while coding agents are making traditional development faster and easier. That means the decision is less about ideology and more about fit.

The real decision now

The debate today is not "low-code or pro-code?" in the abstract.

It is:

Do you want your long-term complexity to sit inside a managed low-code platform, or inside versioned, testable, reviewable code?

For some teams, Power Platform will still be the right answer. For others, especially where the solution needs durability, flexibility and cleaner engineering lifecycle management, pro-code deserves a fresh look.

AI has not killed low-code.

It has just made custom development competitive again.

Read the full article here: Low-code versus pro-code in Microsoft 365: how Power Platform rose, and how AI coding agents are reshaping the trade-offs

Comments

Post a Comment

Popular posts from this blog

SharePoint Looping Workflow - How to: Loop through and process all items in a list

Image
Objective To use SharePoint workflows to loop through all items in a list to perform calculations, process and update metadata values, or concatenate the value of a specific column in all list items into a single string. Background The OOB workflow actions provided by SharePoint don't allow a loop to be configured explicitly. Instead, a number of workflows can work together to create a looping affect. Another limitation of Workflows in SharePoint using SharePoint Designer (SPD) is the inability to simply test if the user who initiated the workflow is a member of a SharePoint group, or to test if the value of a field in the item which initiated the workflow is equal to the value of a specific field from any item in a separate list. For example, the OOB Approval Workflow requires that a user who is an Approver of changes to approve their own changes each time a modification is made. In many cases, Approvers are also the users who make many of the changes that require content approval...
Read more

Solved: Can't Group By Choice Column in SharePoint List View

By Default, items in a SharePoint list can't be grouped by a Choice field if it allows multiple selections (checkbox). To be able to group by the value of a Choice field in a SharePoint list or library which allows multiple selections, you need to ensure that the Choice field/column is set as Radio Buttons or a Drop Down Menu. Both of these options only allow a single selection of the available choices, which is required to allow grouping by the column/field using Standard SharePoint List views. To group by a Choice field which allows multiple selections (checkboxes), convert the Web Part to a Data View using SharePoint Designer, then apply grouping doing the following: 1. From the "Common Data View Tasks" menu for the Data View Web Part, select "Sort and Group:" from the options to open the Sort and Group Dialog, add any field into the Sort Order section to activate the "Edit Sort Expression..." button. Click the "Edit Sort Expression..." b...
Read more

InfoPath SharePoint: Submit InfoPath form to SharePoint List or Library using Content Type

Image
The following article demonstrates how to integrate an InfoPath form with a SharePoint form library, using a centralised template stored in a SharePoint document library and linked to a site Content Type. The form is set up to submit to a SharePoint form library Overview: Set up SharePoint libraries Design the form template Publish form template to SharePoint Content Type Configure the form's primary data connection to submit to the SharePoint library Secondary Data Connections to receive or submit data to a SharePoint list Setting up SharePoint to store the Form template and receive Submitted forms: If InfoPath Form services are available on your SharePoint server, you have the option to store the form template using Central Administration's managed templates list. To make the form available using this method it must uploaded to the Managed Templates List, the activated for the required site collection. In this example I publish the form template to a ...
Read more