Copilot in Excel: Quick Fixes to Try

Key insights

• Personalization
  Set up saved preferences so Copilot remembers formatting and repeated corrections. This cuts down on retyping common instructions and speeds up monthly reports like a sales summary.
• .Rules worksheet
  Place workbook-specific instructions in a visible .Rules worksheet so Copilot can read them. Keep the sheet accessible in the file and update it when you change workflow rules.
• Custom skills
  Convert frequent prompts into reusable custom skills you can call across files. The video shows a plain-language example that groups revenue, calculates shares, and builds a table and chart without code.
• Copilot pane / Edit with Copilot
  Microsoft retired the in-cell COPILOT function and now favors the side Copilot pane and “Edit with Copilot.” Choose “Chat only” to get suggestions or allow edits to have Copilot change the workbook directly. Turn off autosave when testing edits.
• Advanced analysis and traceability
  Copilot supports Python for statistics and visuals inside the workflow and can summarize change history and edit attribution. Always verify results: saved instructions guide Copilot but do not guarantee correct calculations.
• Requirements and limits
  You need a supported Microsoft 365 subscription with Copilot access, appropriate OneDrive placement for custom skills, and correct data permissions. Features and menus can vary by account, Excel version, update channel, and organization settings.

Video overview: what Mynda Treacy demonstrates

In a practical YouTube tutorial, Mynda Treacy (MyOnlineTrainingHub) [MVP] walks viewers through a faster way to use Copilot in Microsoft Excel. She shows how to stop repeating the same formatting fixes by saving preferences, how to add workbook-specific instructions, and how to convert recurring workflows into reusable skills. Consequently, the video uses a monthly sales summary example to illustrate grouping revenue, calculating shares, and producing a table and chart from fresh data.

Furthermore, Treacy emphasizes that the reusable instructions are written in plain language, so users do not need to write code to benefit. She also demonstrates reviewing a plan before applying edits, styling reports, and pulling context from web sources, Microsoft 365 content, Power BI, and other connected data. However, she repeatedly warns that saved instructions guide Copilot but do not guarantee correct calculations.

Setting up reusable instructions and the .Rules worksheet

One of the video’s central tips is to add a visible .Rules worksheet in each workbook to give Copilot direct instructions for that file. Treacy explains that keeping the worksheet visible allows the assistant to read the guidance and behave consistently, while plain-language rules let non-technical users reuse the same process across months. In practice, she shows how a custom skill can be called on new sales data so you do not have to rewrite the whole request each reporting period.

On the other hand, there are tradeoffs when relying on workbook rules. While the approach saves time and reduces repetitive prompts, it creates dependency on the rule text being current and accurate; if underlying data structures change, saved instructions can produce wrong results. Therefore, Treacy advises testing the skill on a sample file and reviewing the proposed edits before committing changes, which helps mitigate risks inherent to automation.

Turning prompts into reusable skills and OneDrive use

Treacy demonstrates how to convert prompts into a shareable custom skill that you can call from different files, and she points out that skills are stored in a OneDrive folder. As a result, teams can distribute the same process across workbooks without rebuilding the logic each time. Moreover, the video explains that this setup works without code, which lowers the barrier to automating repetitive reporting tasks for non-developers.

However, this convenience brings additional challenges related to permissions and access. Because custom skills rely on OneDrive and work data connections, organizations must configure file access and data permissions properly, or the skills will fail for some users. Thus, IT teams must balance ease of reuse with secure access controls and governance policies.

How Microsoft’s Copilot changes affect the workflow

Treacy’s tutorial reflects broader platform changes: Microsoft has removed the standalone COPILOT worksheet function and shifted users toward the Copilot pane and the Edit with Copilot experience. Consequently, workbook-based AI calls are moving into a chat-based side pane that can edit the workbook directly or operate in a chat-only mode. Treacy also covers new features such as Python-powered analysis inside the editing flow and change-history insights that make edits more traceable.

These platform moves have pros and cons. On the positive side, the pane approach reduces formula fragility and allows richer analysis with Python and model upgrades. On the downside, features and menus can vary by subscription, Excel version, update channel, and organizational settings, which means a tutorial that works in one environment may require adaptation in another.

Practical tips, safety checks, and governance

To protect workbooks from unintended edits, Treacy recommends disabling autosave during testing and using the plan-review step before instructing Copilot to apply changes. She also highlights that teams should keep a copy of the original file and check calculations after automation runs, since Copilot can misunderstand intent and produce incorrect formulas. In addition, documenting who can run skills and where rules are stored supports better accountability.

Moreover, administrators should watch for data connections and external context sources that may expose sensitive information. Because Copilot can bring in web and organizational context, permission settings and OneDrive access must be evaluated; failing to do so increases privacy and compliance risks. Therefore, balancing automation benefits with governance and security is essential for reliable deployment.

Conclusions and recommended next steps

Overall, Mynda Treacy’s video offers a pragmatic way to resurrect productivity for users who felt stuck with earlier Copilot behavior. She demonstrates clear steps—use personalization, add a .Rules worksheet, create reusable skills, and validate edits—that streamline recurring reports while preserving a safety review. Consequently, teams can significantly reduce repetitive prompting and speed up monthly reporting with these changes.

Nevertheless, the video also makes clear that automation is not a substitute for review: saved instructions speed work but do not replace human validation. For best results, organizations should pilot the approach on non-critical files, tighten access controls, and train staff on how to test and troubleshoot saved rules and skills before rolling them out more broadly.

Keywords

copilot excel not working, fix copilot in excel, enable copilot excel, improve copilot excel performance, copilot excel troubleshooting, copilot excel settings to change, copilot excel tips and tricks, alternatives to copilot in excel