by DeeDee Walsh, on Jun 2, 2026 1:59:59 AM
Microsoft Build 2026 opens this morning in San Francisco. Here's what the agent-first platform shift means if your core business logic still lives in Visual Basic 6.
Satya Nadella takes the stage in a few hours at Fort Mason Center to make what may be the most consequential platform declaration Microsoft has made in a decade: Windows is no longer a platform built exclusively for human users. Agents (autonomous software that can plan, execute, and coordinate multi-step work) are becoming first-class citizens in the runtime, the tooling, and the distribution model.
The developer world will spend the next 48 hours dissecting what that means for greenfield AI apps, GitHub Copilot's agentic coding modes, and the Microsoft Foundry updates expected from this year's session catalog.
We want to talk about the people who won't be in those sessions. The enterprises whose most critical business logic still runs in Visual Basic 6 (and PowerBuilder, Clarion, MS Access just to name a few).
Your VB6 application can't be an agent, can't be called by an agent, and can't participate in the platform Microsoft is announcing today. It's a structural incompatibility and it's getting more expensive by the quarter.
What Agent-First Requires
It's worth being precise about what the agentic model demands at a technical level, because the gap with legacy code is not obvious from the outside.
Agents, whether they are Windows-native via Microsoft's new agent frameworks, Azure-orchestrated, or built on MCP-compatible toolchains coordinate work by calling things. They call APIs. They read structured interfaces. They fire webhooks. They consume events. They pass context between services. An agent operating across your enterprise does so by discovering capabilities (what this system can do) and invoking them (doing it) programmatically, at runtime, without human mediation.
A well-architected modern application is built for exactly this. REST APIs expose business logic as callable endpoints. .NET and Blazor applications participate natively in Microsoft's authentication and identity layer. Events flow through structured pipelines. Data lives in accessible, queryable stores.
VB6 applications were built for a totally different computing model. One organized around a user sitting at a screen, clicking buttons, triggering COM events, reading from proprietary data stores. The application is the interface. There is no separation between the UI, the business logic, and the data access layer, because that separation was never the point.
You can't wrap a COM-bound VB6 app in an API and call it a day. The logic is not extractable without transformation. The data access patterns aren't abstracted. The authentication model isn't compatible with modern identity providers. And the tooling that would let an agent reason about your application (structured schemas, event contracts, capability declarations) does not exist.
Agents can't see your VB6 application. To every agentic orchestration system Microsoft ships this year, your most important business processes are invisible.
Way Bigger than Technical Debt
Enterprises have been told for years that VB6 modernization is important because the platform is unsupported, because developers who know it are retiring, because the security exposure is real. All of that is true. But those were arguments about cost and risk; gradual pressures that could be deferred, prioritized against other things, managed through heroic maintenance.
The agent-first platform shift is a different kind of problem. It's now about opportunity.
The AI investments your organization is making: the Copilot licenses, the Azure AI spend, the productivity automation initiatives are being built on top of a modern software stack. Those investments compound when your applications can participate in the stack. When an agent can query your inventory system, trigger your approval workflow, surface your customer history, or update your operational records, the AI layer multiplies the value of everything underneath it.
When your applications can't participate because they're COM-bound, UI-dependent, and structurally closed to programmatic access. Those AI investments operate around your core systems, not through them. The agents your competitors are building will have access to their business logic. Yours will have workarounds.
We call this the AI Readiness Tax: the increasing cost, in capability and competitive position, of operating a core application that can't participate in the AI layer your industry is building on. The tax compounds. Every quarter you defer modernization is a quarter your AI-enabled competitors are widening the gap.
What Agent-Ready Looks Like
The good news is that the destination is defined. Microsoft has been consistent about where the modern application stack lands: .NET, Blazor, Azure-native services, and the identity and API patterns that make agent orchestration possible.
An application that lives there can be called by an agent, can call other agents, can participate in Copilot Workspace and the agentic workflows being announced this week. Its business logic becomes a composable capability in a network of systems that can coordinate, automate, and reason.
To be clear, the logic in your VB6 application (the business rules accumulated over decades) is valuable. The problem is that it's trapped in an architecture that makes it inaccessible. The modernization problem is one of extraction and transformation: preserving what matters while rebuilding the structure that lets it participate in the platform you need to operate on.
That is exactly what VELO is built to do. VELO is GAPVelocity AI's automated modernization engine, built on Microsoft Foundry, designed specifically to handle the depth and complexity of VB6 code that general-purpose tools can't touch. It delivers a fully modernized, production-ready application that's a complete, testable, deployable system, at fixed price.
The Question Is Timing
Nadella's keynote this morning will make the direction clear. Agents are here. This is the future. They are the platform Microsoft is shipping now: in Azure, in GitHub Copilot, in Windows, in the developer toolchain every enterprise team is building on.
Every organization still running VB6 is needs to figure out their modernization timeline. The question is how much of the AI-first decade you want to sit out while the work gets done.
If you want to understand what modernization actually takes for your specific application (scope, timeline, cost) we can give you that picture before you commit to anything.
GAPVelocity AI is the AI modernization business unit of Growth Acceleration Partners. VELO automates the modernization of legacy Visual Basic 6, PowerBuilder, Access, and other legacy platforms to production-ready .NET and Blazor applications. Our lineage includes building Microsoft's original Visual Basic Upgrade Wizard.
