Excel on SharePoint: macros, add-ins and co-authoring in one setup

SOLUTION GUIDE

Excel and SharePoint work together out of the box. For simple workbooks the default experience is good: open through SharePoint or Teams, co-author with colleagues in real time, autosave to the cloud, restore prior versions if needed. Where accounting practices, finance teams and other Excel-heavy operations hit the limits of that default is on the advanced end: VBA macros, COM add-ins (Sage, IRIS, CCH and tax-software integrations), cross-workbook references, and statutory templates with locked formulas that rely on desktop Excel and a resolvable file path. Cloud Drive Mapper adds a mapped-drive layer on top of SharePoint so those workflows keep working from Excel desktop, without asking practices to give up co-authoring on the workbooks that suit it. One file, two access paths, one source of truth in SharePoint.

Why the default Excel + SharePoint experience is good

Excel is Microsoft's own product and SharePoint / OneDrive are Microsoft's own storage. Nobody needs a third-party tool to make them talk to each other. For a huge share of workbooks, the default path is genuinely the right answer:

Real-time co-authoring across multiple users
Autosave to SharePoint on every change
Version history managed by SharePoint natively
Share by link, control access through Microsoft 365 permissions
Excel Online in the browser when someone needs quick access without opening desktop Excel

A firm's regular reporting spreadsheets, budget trackers, client-facing data summaries, project sheets and general collaborative workbooks all live comfortably in the default Excel + SharePoint model. Nothing in this page is arguing to change that.

Where accounting workflows outgrow the default

The friction shows up on the workbooks accounting practices, finance functions and analyst teams live in the most. Four patterns account for almost every case we see.

VBA macros

Excel Online does not run VBA. Any workbook whose value depends on macros (a reconciliation routine, a journal-entry posting macro, a firm-standard reporting workflow, a statutory-return automation) is a desktop-Excel workbook by definition. Opening it via SharePoint browser strips the macro layer; opening it via the OneDrive sync client works but ties the file to whichever laptop last synced it. Neither is what practices want for a workbook that a whole team runs quarterly.

COM add-ins (Sage, IRIS, CCH, tax and audit tools)

Practice-management, accounting and tax software regularly ships Excel COM add-ins that hook into Excel desktop: populate templates from the practice database, post journal entries back, pull tax figures into working papers. These add-ins load into Excel at startup and expect files to resolve at a real Windows file path. Excel Online does not support them. Opening a workbook through the SharePoint browser bypasses the add-in surface entirely.

Cross-workbook references and INDIRECT() formulas

Many practice models are multi-workbook. A consolidated reporting workbook pulls from a set of underlying data workbooks. A tax-return workbook references figures held in a working-papers workbook. These references are stored as file paths. If the path structure is unstable (files moving between local, OneDrive-synced and SharePoint-native locations), the links break, INDIRECT() formulas return #REF, and the model has to be rebuilt or re-linked by hand every time.

Statutory templates with locked formulas and password-protected structures

Statutory account templates, industry-body reporting templates and audit workbooks often ship with locked structures and password-protected VBA. They are designed to run on desktop Excel from a resolvable file path. They tend to break in unpredictable ways under sync-client behaviour that touches temp files, locks or metadata during open/save operations.

The trade-off firms face without a mapped-drive layer

Firms with heavy Excel workflows tend to end up with an unhappy compromise:

Keep the macro-heavy and add-in-dependent workbooks on a local file server. Macros work, add-ins work, links resolve. No co-authoring, no version history, no easy sharing, and the file server keeps needing to exist.
Move everything to SharePoint / OneDrive. Co-authoring works, version history works, sharing works. Macros are limited, COM add-ins are hit-or-miss, cross-workbook links start breaking, statutory templates behave oddly.
Two copies of each workbook: one "live" copy in SharePoint for sharing, one "working" copy on the file server for macro operations. Predictable outcome: the two drift apart, staff work on the wrong version, and reconciliation of the reconciliation workbook becomes a Monday-morning ritual.

None of these is a good place for a practice to end up.

How Cloud Drive Mapper gives you both

CDM does not replace SharePoint co-authoring. It presents SharePoint document libraries as Windows mapped drive letters, so the same workbook stored in SharePoint is reachable via two paths on the same endpoint:

Through the SharePoint browser, the Teams client, or the standard OneDrive path: the co-authoring surface Microsoft designed.
Through the CDM-mapped drive letter (typically M:, N:, P:): a normal Windows file path that Excel desktop and its add-ins can operate against.

One workbook, one source of truth in SharePoint, two access paths that suit different workflows. Practices can choose per-workbook (or per-team) which access pattern fits.

Macros run from the mapped drive

Excel opens a workbook from the CDM drive as if from a network share. Add the mapped drive to Excel's Trusted Locations and VBA runs without prompts, exactly as it would from a file server. The macro estate a practice has built up over years continues to function without rewriting.

COM add-ins work

Sage Excel plugins, IRIS practice suite plugins, CCH tax integrations, Thomson Reuters practice tools, custom firm-built add-ins: all load into Excel at startup and operate on whatever workbook is open. They do not care where the file physically lives, only that Excel can resolve it as a file path. CDM provides exactly that.

Cross-workbook references resolve

Because the CDM drive letter is consistent across users (M: always maps to the same SharePoint site for every practice member), workbooks that reference other workbooks by path continue to work. INDIRECT() formulas that build paths dynamically continue to resolve. Multi-workbook models keep working across the practice, without re-linking after every migration.

Statutory templates behave the way they were designed to

Templates that expect to run on desktop Excel from a resolvable file path get exactly that through CDM. The locked structures and protected VBA behave as they would against a traditional network share, without the odd sync-client interference that shows up when the same template is opened via OneDrive-synced folders.

Co-authoring is still available where it fits

This is the important part. Nothing about CDM prevents the same workbook being opened for co-authoring via the SharePoint browser or the standard OneDrive path. Practices typically split by workflow rather than by workbook: a shared quarterly-reporting model is opened via the CDM path when the reporting accountant is running its macros; the same file is opened via the SharePoint browser when the partner and senior are jointly reviewing the summary sheet. One source of truth in SharePoint; two access paths chosen by workflow.

Setting it up

A few practical notes for a clean deployment:

Add the CDM drive letter (or a specific folder inside it) to Excel's Trusted Locations so VBA runs without security prompts. This can be pushed centrally through Group Policy or Intune.
Standardise which drive letter maps to which SharePoint site across the practice, so cross-workbook references resolve identically for every user.
Test practice-critical add-ins (Sage, IRIS, CCH, tax tools) against a workbook opened from the mapped drive as part of the initial rollout. In practice these tend to just work, but a five-minute smoke test is worth doing before wider deployment.
Document a simple internal guide for staff: which workflows use the SharePoint / Teams path (co-authoring, quick edits, shared review) and which use the CDM path (macros, add-in-heavy templates, cross-workbook models). Nothing complex; a one-page "when to use which" reference is enough.
For information governance sign-off, walk stakeholders through the zero-access architecture underpinning CDM: no local cache, delegated permissions to your tenant, no IAM Cloud staff access to customer content by design.

Cloud Drive Mapper is used across accounting practices, finance teams and other Excel-heavy operations to keep macro and add-in workflows alive on SharePoint, without giving up co-authoring where it fits.

Start a 30-day free trial How Cloud Drive Mapper works →

Frequently asked questions

Do VBA macros run when Excel opens a workbook from a Cloud Drive Mapper drive?

Yes. Excel treats a CDM-mapped drive the same way it treats any Windows network drive. Macros run under the same trust rules they would from a traditional file share: add the mapped drive to Excel's Trusted Locations (or use signed-macro trust) and VBA runs as it always has. This is why practices with heavy macro-based tooling can move to SharePoint without giving up their macro estate.

Do COM add-ins (Sage, IRIS, CCH, tax software integrations) work with Excel opened from a CDM drive?

Yes. COM add-ins are loaded by Excel itself at startup and operate on whatever workbook Excel has open. They do not care where the file physically lives, only that Excel can resolve it as a file path, which CDM provides. Sage Excel plugins, IRIS practice suite plugins, CCH tax integrations, Thomson Reuters practice tools and equivalents behave the same way against a CDM-mapped drive as they would against a network share.

Can I still co-author an Excel workbook that lives on a CDM-mapped drive?

Yes. The workbook physically lives in SharePoint, and CDM is just presenting it via a mapped drive letter. The same file is reachable through the SharePoint browser or the standard OneDrive path, and Excel's co-authoring works when the file is opened via those routes. Firms typically split by workflow: simple, collaboratively-edited workbooks get opened via SharePoint or Teams; macro-heavy or add-in-dependent workbooks get opened via the CDM path where Excel desktop's full feature set applies.

Do cross-workbook references and INDIRECT() formulas work with CDM?

Yes. Cross-workbook references and INDIRECT() formulas need consistent file paths to resolve. CDM presents SharePoint content at consistent drive letters (M:, N:, whatever you configure), and the folder tree beneath is stable across sessions and users. Workbooks that reference other workbooks by path continue to resolve correctly, provided every user has the same drive letter mapped to the same SharePoint site.

What about very large or complex accounting workbooks?

CDM streams file content on demand rather than syncing a full local mirror. Opening a large workbook downloads only what Excel requests; saves stream changed blocks back to SharePoint rather than re-uploading the whole file. Performance on the CDM path is comparable to a network share, which is what those workbooks were tuned for originally. Very large models with heavy calculation loads still spend most of their time in Excel's calculation engine rather than in file I/O, so the storage layer is not usually the bottleneck.

Does IAM Cloud have access to our workbooks?

No. Cloud Drive Mapper operates purely with delegated permissions inside your Microsoft 365 tenant. IAM Cloud holds no credentials that would authenticate to your tenant. Only your firm's signed-in users can access content through CDM, and only within their existing M365 permissions. Full technical detail is in the Zero-access architecture solution.

See it work with your Excel estate

The fastest way to see if CDM works for your macro and add-in workflows is to try it for 30 days, free. Point Excel at a mapped drive, open a workbook that depends on your add-in stack, and see how it feels.

Start a free trial Request a demo