Excel App Builder: Should Excel Support Turning Workbooks into Standalone Low-Code Applications?
Excel has been much more than a spreadsheet application for a long time. In many organizations, Excel is already used as an informal low-code development platform. Advanced workbooks often contain not only data and formulas, but complete domain-specific logic: calculation models, planning tools, dashboards, input forms, reports, simulations, administrative workflows, and sometimes even small internal business applications. This is one of Excel’s greatest strengths. It allows domain experts, power users, analysts, engineers, teachers, consultants, and small businesses to build working tools without becoming full-time software developers. However, there is a structural limitation: the final product usually remains an Excel workbook. That creates several problems: the user needs a compatible Excel installation, macro security and Trust Center settings can block functionality, formulas and business logic are difficult to protect properly, distribution and updates are not as clean as with real applications, workbook-based tools often look less professional than standalone software, user interface, data, and logic are often mixed together in the same file. I believe Microsoft could turn this existing reality into a major strategic opportunity. Core proposal: Excel App Builder / Excel Runtime My suggestion is an official Excel App Builder or Excel Runtime. The idea would be to allow selected Excel workbooks to be packaged as protected standalone applications. Excel would continue to serve as the calculation, data, and automation engine in the background. The end user would not necessarily see the workbook itself. Instead, they would interact with a clean application interface: input forms, buttons, dashboards, charts, reports, controlled tables, and export options. Possible output formats could include: Windows apps, web apps, Teams apps, SharePoint apps, mobile-friendly internal tools, protected specialist applications. This would not replace Power Apps. In my view, it could complement Power Apps very well. Excel could remain the place where fast domain logic, calculations, prototypes, and models are created. Power Apps, Dataverse, Azure, and the wider Microsoft ecosystem could then support larger, scalable, enterprise-level workflows. In other words: Excel could become the natural entry point into Microsoft’s low-code ecosystem. Why this could matter strategically Excel already has an enormous “hidden developer base”: people who are not traditional programmers, but who build useful tools with formulas, tables, Power Query, Power Pivot, VBA, Office Scripts, and now AI assistance. This is a unique market position. Many of these users would not start with C#, JavaScript, Python, or a full application framework. But they already start with Excel. They already build the logic there. The missing step is a professional way to package, protect, distribute, and update those solutions. An official App Builder could: strengthen Excel’s long-term relevance, differentiate Excel from simpler spreadsheet competitors, create a stronger bridge between Excel and Power Platform, give power users a professional deployment path, create new commercial licensing opportunities, reduce the need for fragile VBA/UI workarounds, make Excel-based tools more secure and maintainable. Example use cases A small engineering office creates a technical calculation workbook and exports it as a protected customer tool. A school or university builds a grading, diagnostic, or planning tool with Excel logic but provides staff with a clean app interface. A small business turns an Excel-based quotation calculator into an internal sales app. A finance department packages a planning model as a controlled scenario tool for managers. A consultant builds specialized calculation tools and distributes them professionally without exposing the workbook structure. These are not exotic scenarios. Many people already build this kind of logic in Excel today. The difference would be that Microsoft could provide an official, safe, and professional deployment path. Supporting features that would make this stronger 1. Modern UI layer for Excel-based apps Excel-based applications would need a modern interface layer: forms, dialogs, navigation pages, buttons, card layouts, dashboards, responsive views, mobile-friendly layouts, role-based views, binding to cells, tables, named ranges, and data models. This would create a clearer separation between data, logic, and user interface. 2. Protected workbook logic A professional app export would require strong protection options: hidden formulas, protected named ranges, protected scripts or macro logic, defined input areas, digital signing, controlled editing, update mechanisms, possible licensing controls for commercial distribution. 3. Formula cells with controlled manual override One frequent Excel problem is that users overwrite formulas. A useful new cell mode could be: default formula + optional manual override The cell would keep the original formula internally but allow a controlled manual exception value. Excel could show whether the formula is active or manually overridden. This would remove many helper-column and VBA workarounds in planning, pricing, grading, budgeting, and technical models. 4. Native database layer inside Excel Excel is widely used as a database, even when that becomes fragile. A native database layer could support: primary keys, relationships between tables, required fields, validation rules, change history, duplicate detection, form views, simple queries, optional cloud synchronization. This should feel like a natural extension of Excel tables, not like a separate database product. 5. Multidimensional workbook models Many workbooks use separate sheets for months, locations, versions, departments, or scenarios. This often creates duplication and maintenance problems. Excel could support native dimensions for tables and models, for example: time period, location, scenario, version, department. Formulas, charts, dashboards, and PivotTables could become dimension-aware. This would be especially useful for financial planning, controlling, simulations, scientific models, and project planning. Why now? AI is changing how people build with Excel. Copilot and other AI tools make it easier for non-programmers to generate formulas, scripts, models, and structured workflows. That means more users will be able to build complex Excel-based solutions. But if AI helps users create more advanced workbooks, the next logical question is: How can these workbooks be safely packaged, shared, protected, and used as real tools? An Excel App Builder could be the answer. Possible first step This does not need to start as a massive platform. A realistic first version could be experimental: selected workbook ranges, simple input forms, protected formulas, dashboard view, Windows or web runtime, export as an internal app, optional Teams or SharePoint integration. It could even begin as an Excel Labs / Microsoft Garage style experiment to test demand and gather feedback from power users, developers, and organizations. Core question for the community Excel is already used as a hidden development platform. Should Microsoft make this official? Would an Excel App Builder / Excel Runtime be useful for your organization, clients, or internal tools? Which feature would matter most in a first version? protected workbook runtime, modern UI layer, formula override cells, native database layer, multidimensional models, Power Platform integration, commercial app distribution? I would be very interested to hear how other Excel users, developers, MVPs, and Microsoft product people see this idea. In short: Excel already allows millions of people to build domain-specific logic. Microsoft could turn that strength into an official, secure, and economically attractive low-code application platform.In Case You Missed It: Frontier Transformation and Wave 3 of Microsoft 365 Copilot Announcements
March brought a major set of Frontier Transformation and wave 3 of Microsoft 365 Copilot announcements across Microsoft 365 Copilot, Copilot Chat, and agents—all focused on helping people move faster from intent to action and helping organizations scale AI responsibly. If you missed any of the updates, here’s a quick recap of what’s new and why it matters. Copilot Transforms Knowledge Work These updates deepen how Copilot shows up inside the flow of work—grounded in your content, context, and tools. Word, Excel, and PowerPoint Agents From Copilot Chat, users can ask Word, Excel, or PowerPoint agents to create content, take next steps, or execute tasks, helping them move from intent to action without copying and pasting or switching contexts. 👉 Learn more Edit with Copilot in Word, Excel, and PowerPoint Copilot now creates, edits, and refines content directly inside Word, Excel, and PowerPoint, grounded in the context of a user’s work through Work IQ, so people can iterate and improve content without leaving the app they’re working in. 👉 Learn more Sequences shortened for demonstration purposes. Copilot Chat in Outlook Copilot Chat in Outlook enables users to draft and refine emails, manage calendars and RSVPs, and use the Outlook email widget to take action directly from chat, streamlining everyday communication and scheduling tasks. 👉 Learn more Outlook customer calendar instructions & proactive RSVPs Copilot finds available meeting times, sends invites, and keeps calendars up to date based on custom instructions, notifying users of changes directly in chat to reduce manual coordination. 👉 Learn more Copilot Cowork Built with Anthropic, Copilot Cowork brings a multimodel approach to Microsoft 365 Copilot—so your work isn’t tied to a single model. Cowork moves Copilot beyond prompts into long‑running, multi‑step work. With full awareness of your work context through Work IQ, it lets you delegate meaningful work and stay informed as it progresses. 👉 Learn more Claude Sonnet available in Copilot Chat Users can select Claude models directly in Copilot Chat, alongside next‑generation OpenAI models, bringing leading models from multiple providers into a single Copilot experience. 👉 Learn more Dataverse in Work IQ Work IQ connects signals from Microsoft 365—including documents, meetings, email, and chat—and will soon access operational data in Dataverse through Copilot in Dynamics 365 and Power Apps, bringing work context and business data closer together. 👉 Learn more Work IQ Memory (Chat History) Work IQ Memory enables more relevant, personalized Copilot responses shaped by a user’s work and Copilot chat history over time. 👉 Learn more Extensibility: Work IQ API / MCP Work IQ APIs provide access to production‑ready AI capabilities that work directly with enterprise work context, enabling extensibility through APIs and MCP. 👉 Learn more Launch Demo Copilot in Dynamics 365 & Power Apps Microsoft 365 Copilot is accessible directly within Dynamics 365 Sales, Customer Service, and Power Apps, extending Copilot experiences into business applications where operational work happens. 👉 Learn more Agents That Help Run the Business These announcements focus on building, deploying, and scaling agents across the enterprise. Apps SDK The Apps SDK provides tools to build ChatGPT apps based on the MCP Apps standard, with additional ChatGPT functionality to support agent and Copilot experiences. 👉 Learn more Model Context Protocol (MCP) Apps MCP Apps turn Copilot from a text interface into a governed, interactive execution layer by surfacing interactive app experiences directly in Copilot Chat. 👉 Learn more Apps in Agents: Outlook, Dynamics 365, and Power Apps Agents can bring Outlook, Dynamics 365, and Power Apps directly into chat, allowing users to review information and take action without leaving the conversation. 👉 Learn more Agent Recommendations in Microsoft 365 Copilot When users prompt Microsoft 365 Copilot, the system analyzes intent and recommends an installed, IT‑approved agent directly in the flow of work, making agents easier to discover and use at scale. 👉 Learn more Evaluate agents in Copilot Studio Copilot Studio provides structured, repeatable testing to help catch issues early, reduce the risk of bad answers, and maintain agent quality as agents evolve. 👉 Learn more Visibility, Governance, and Control at Scale As agent usage grows, these updates help organizations move from experimentation to enterprise readiness. Agent 365 Agent 365 serves as the control plane for agents, helping organizations move from experimentation to enterprise‑scale operations by enabling them to observe, govern, and secure agents. 👉 Learn more Microsoft 365 E7: The Frontier Suite Microsoft 365 E7 unifies Microsoft 365 E5, Microsoft 365 Copilot and Agent 365 into a single solution powered by Work IQ and integrated with the productivity apps and security stack customers already rely on. It includes Microsoft Entra Suite and advanced Defender, Intune and Purview security capabilities, delivering comprehensive protection across agents and employees. 👉 Learn more To explore what’s available now—and what’s coming next—visit the Microsoft 365 roadmap and related announcement blogs. 👉 Explore the roadmap
Allow removal of "Copilot Suggestions" from right-click menu
I have been using Excel for decades and CONSTANTLY use the right-click menu for quick access to basic functions (e.g., "Insert"). Ever since "Copilot Suggestions" was added to the drop-down list, it always throws me off due to its placement. I have Microsoft 365 on Windows 11 Pro. I have searched for ways to remove this from appearing there and the result said "go to File > Options > Copilot and uncheck the 'Enable Copilot' box". However, when I attempt to do that, there is NO "Copilot" option available! PLEASE allow removal of "Copilot Suggestions" from the right-click menu OR at least the option to move it to the bottom (so it isn't in the way of things used ALL the time). I realize that Copilot is a great resource for many users, but I am confident in my Excel skills and in my ability to research/learn new skills the "old school" way, so I have little use for this feature now and would prefer to hide it.
Proposal for a Unified Copilot Architecture and Tiered AI Assistant Model
Submitted by: Craig D. Evans Detroit, Michigan Executive Summary This proposal outlines a strategic redesign of Microsoft Copilot that transforms it from a collection of isolated chat instances into a unified, persistent, account based artificial intelligence assistant. The proposed architecture positions Copilot as the central intelligence that operates all Microsoft Office applications, maintains long term memory, and follows the user across all devices. This model introduces a tiered pricing structure that creates a scalable revenue engine while strengthening Microsoft’s long term dominance in productivity software. The proposal also introduces the concept of a dual AI verification system, in which Copilot performs tasks and a secondary model provides independent review. This structure increases reliability, reduces errors, and enhances user trust. Problem Statement The current Copilot experience is fragmented. Each application instance behaves as a separate assistant with limited continuity, limited memory, and limited cross application intelligence. Users must repeatedly re explain context, re establish preferences, and manually coordinate tasks across Word, Excel, PowerPoint, Outlook, and other Microsoft 365 applications. This fragmentation reduces efficiency, increases cognitive load, and prevents Copilot from functioning as a true personal assistant. It also limits Microsoft’s ability to monetize Copilot at scale, because the product does not yet offer a unified, persistent experience that users would be willing to subscribe to at higher tiers. Vision The vision is a single, persistent Copilot identity that the user logs into, similar to any modern online service. This identity follows the user across all devices and applications, retaining memory, preferences, formatting rules, workflows, and ongoing projects. In this model, Copilot becomes the central intelligence that operates the Microsoft Office ecosystem. Office applications become the tools, and Copilot becomes the operator. This transformation elevates Copilot from a chatbot to a long term digital assistant that remains with the user for decades. Functional Overview 1. Persistent Copilot Identity A single Copilot account that retains: Long term memory User preferences Formatting rules Writing style Project context Cross application workflows Templates and document structures This identity behaves like any other modern login system, such as Amazon, Walmart, or email services. 2. Copilot as the Central Intelligence of Office Copilot should be capable of: Opening and managing Word documents Applying templates and formatting Building PowerPoint presentations Managing Excel formulas and data structures Organizing files and directories Coordinating tasks across applications Executing workflows on behalf of the user Office becomes the body. Copilot becomes the brain. 3. Cross Device Continuity The user logs into Copilot once, and the assistant follows the user across: Desktop Laptop Mobile Web Cloud environments This creates a seamless, continuous experience. Tiered Pricing Model A tiered structure creates a scalable revenue engine and aligns with Microsoft’s existing subscription model. Tier 1: Free Copilot Basic chat No memory No continuity Limited functionality This tier serves as the entry point that encourages users to upgrade. Tier 2: Copilot with Memory and Formatting Persistent memory Document formatting intelligence Writing style retention Basic cross application awareness This tier provides immediate value and will attract a large user base. Tier 3: Cross Device Copilot Identity Full continuity across devices Unified assistant experience Project level intelligence Long term context retention This tier becomes the premium personal assistant model. Tier 4: Copilot as Full Office Manager Complete control of Word, Excel, PowerPoint, Outlook Workflow automation File management Multi application coordination Enterprise grade productivity This tier becomes the flagship offering for professionals and businesses. Optional Tier: Dual AI Verification (Copilot + Reviewer Model) Copilot performs tasks. A secondary model independently reviews output for: Accuracy Formatting Logic Consistency This reduces errors and increases trust. It becomes a high value premium tier. Competitive Advantage This architecture provides Microsoft with several strategic advantages: A unified assistant that no competitor currently offers A multi tier revenue structure that scales with user needs A long term relationship between user and assistant Increased adoption of Microsoft 365 subscriptions Strong differentiation from competing AI products Reduced user churn due to persistent memory and continuity This model positions Microsoft as the leader in personal and professional AI assistance. Long Term Strategic Value A persistent Copilot identity ensures that users remain within the Microsoft ecosystem for decades. As the assistant accumulates memory, preferences, and workflows, the cost of switching to another platform becomes extremely high. This creates: Long term subscription stability Increased enterprise adoption Stronger user loyalty A durable competitive moat Copilot becomes not only a feature, but a lifelong digital partner. Closing Statement I respectfully submit this proposal as a long time user who believes that Microsoft has the opportunity to define the future of personal and professional artificial intelligence. A unified Copilot identity, combined with a tiered pricing model and a dual AI verification system, will create a powerful, scalable, and enduring platform that strengthens Microsoft’s leadership in productivity software. Submitted by: Craig D. Evans Detroit, Michigan
Limitations of Microsoft 365 Copilot for Excel workflows?
I've been exploring Microsoft 365 Copilot for Excel workflows recently. It works well for simple queries, but I still find it limited when dealing with: - messy data cleaning - converting images/PDFs into structured tables - more complex data transformations Curious how others are using Copilot for these scenarios? Are you relying purely on Copilot, or combining it with other tools/workflows?
