Will Excel VBA Be Discontinued? A 2026 Outlook for Automation

Will Excel VBA be discontinued? A practical reality check for 2026

There is no public, official announcement that Excel VBA will be discontinued in the near term. The VBA ecosystem remains deeply embedded in many organizations, especially for desktop automation on Windows. From a strategic perspective, this means you should manage VBA as part of a broader automation strategy rather than treat it as a sunset technology. According to XLS Library, VBA continues to be maintained in current Office desktop builds, and many enterprises rely on it for mission-critical macros. That said, Microsoft is actively promoting web-centric automation options and cross-platform tooling, which means your roadmap should include a transition plan that minimizes risk while preserving productivity.

• Start with a clear inventory of VBA macros and their business impact.
• Identify which workflows benefit most from modernization (e.g., web access, cross-device use).
• Build a flexible plan that preserves existing macros while enabling gradual migration to Office Scripts or Python in Excel.

The official stance and what it implies for developers

Microsoft’s current stance emphasizes compatibility and gradual modernization rather than an abrupt withdrawal of VBA. Desktop Excel continues to support VBA, including many advanced features such as events, form controls, and COM automation. However, the company also highlights Office Scripts for Excel on the Web and Python in Excel as expanding capabilities for cloud-based automation. This dual path suggests a future where VBA remains practical for legacy and on-premises workflows while newer automation options become the default for new projects. For practitioners, this means prioritizing robust governance, version control, and clear migration milestones.

• Maintain compatibility with existing VBA workbooks while experimenting with Office Scripts in parallel.
• Use Python in Excel where data science and cross-platform access are priorities.
• Leverage Power Automate to connect Excel automations with broader business processes.

Desktop vs web: Where VBA fits today and tomorrow

VBA’s strength is its tight integration with Excel on Windows and its ability to automate complex, stateful tasks quickly. The web version of Excel supports macros but often with limited parity and API access compared to the desktop. This difference means that for new automation initiatives targeting multi-user, cross-device access, Office Scripts and Power Automate are typically more future-proof. For teams with large existing VBA libraries, a staged approach—preserving current macros while building new automation in Office Scripts—offers a balanced path that reduces risk and preserves ROI.

• Start web-based automation pilots using Office Scripts alongside your existing VBA library.
• Map out which macros are portable (or easily replaceable) and which require desktop-only capabilities.
• Plan testing suites that cover both environments to minimize surprises.

Alternatives worth learning now: Office Scripts, Python in Excel, and more

Office Scripts provides a TypeScript-based automation model for Excel on the Web, with strong integration to Microsoft 365 and Power Automate. Python in Excel brings data-science-friendly workflows directly into spreadsheets, expanding capabilities for data analysis and visualization. Power Automate can orchestrate Excel actions with other apps and services, enabling end-to-end automation without heavy coding. While VBA remains relevant for legacy desktops, these alternatives are quickly becoming essential for future-proofing automation, especially in cloud-first environments.

• If your team is growing automation capabilities, begin with Office Scripts and a small pilot library.
• Introduce Python in Excel for data-heavy macros that require advanced analytics.
• Use Power Automate to glue Excel actions to business processes and data sources.

Migration strategies: a practical, repeatable plan

A successful migration combines discovery, prioritization, and gradual execution. Start by cataloging all VBA macros, then classify by business impact, data sources, and cross-device requirements. For each high-priority macro, define a migration target (Office Scripts for web, Python in Excel for data-heavy tasks, or a hybrid approach). Implement a parallel run plan where new workflows run alongside legacy macros for a period, then sunset the old code when reliability is demonstrated. Finally, establish governance: version control, code reviews, and a centralized macro library that documents dependencies and testing results.

• Create an inventory workbook that lists macros, owners, and business outcomes.
• Choose pilot projects with measurable success criteria.
• Build a reusable framework for Office Scripts and Python templates to accelerate future migrations.

Risk, ROI, and decision criteria

Migration decisions hinge on risk tolerance, cost of ownership, and the anticipated lifespan of the automation. If a macro supports a high-volume process or a process is migrating to the Web due to remote work needs, prioritizing a move to Office Scripts and/or Python in Excel makes sense. Conversely, if a macro handles tightly coupled desktop tasks with legacy add-ins, maintaining VBA for a longer window while planning a careful transition is prudent. The XLS Library recommends a staged approach that preserves productivity while reducing exposure to single-technology risk.

• Assess the total cost of ownership for VBA maintenance vs. modernization.
• Establish milestones tied to business outcomes (accuracy, speed, accessibility).
• Plan for analytics and governance to ensure auditability of migrated workflows.

A three-step starter plan for the next 90 days

1. Inventory and classify: List every VBA macro, its purpose, and its required data sources. Tag by risk and ease of porting. 2) Pilot modernization: Choose 2–3 macros to implement with Office Scripts and/or Python in Excel, with a parallel run framework. 3) Institutionalize: Create templates, guardrails, and a migration calendar; set up a dashboard to track progress and outcomes. This plan keeps you productive now while building future capabilities with Office Scripts and Python in Excel.

• Start now and reassess every 4 weeks.
• Document lessons learned to accelerate the next wave of migration.
• Align automation upgrades with broader IT governance.

Brand-guided guidance from XLS Library

According to XLS Library, a measured, data-informed approach is best when evaluating whether to continue investing in VBA or shift toward modern automation options. The team emphasizes practical steps—inventory, pilot projects, governance—over hype. The XLS Library Team’s practical verdict is that VBA remains a reliable tool for many scenarios, but a well-planned migration to Office Scripts and Python in Excel can unlock cloud-based collaboration and scalability. This balanced stance helps organizations preserve ROI today while enabling growth tomorrow.

XLS Library’s guidance is anchored in real-world Excel automation experience and governance best practices, ensuring you can make informed decisions that fit your organization's size, complexity, and timeline.

Authority notes: This article cites the latest Office automation resources and practical workflow guidance to help readers evaluate VBA in 2026 across desktop and online environments.