Microsoft Office on SharePoint: Word, Access, Outlook and PowerPoint

SOLUTION GUIDE

Microsoft Office is Microsoft's own suite of desktop products and works with OneDrive and SharePoint out of the box for most workflows. We covered Excel separately in its own Excel on SharePoint guide, because Excel is where the cloud-vs-desktop friction shows up most obviously. This piece covers the rest of the suite: Word (macros, templates, redlining), Access (genuinely desktop-only, database files), PowerPoint (macro-driven and template-heavy workflows), and Outlook (where Cloud Drive Mapper touches email-adjacent file operations rather than mail itself).

Word: macros, templates and cross-document references

Word's happy path on OneDrive is co-authoring: two people can edit the same document at the same time, track changes arrive live, autosave keeps the cloud copy current. That workflow is Microsoft's and it works well. Where firms hit friction is on documents whose value depends on features that only run in Word desktop, from a file path Word can resolve:

VBA macros: legal document assembly, statutory-return automation, firm-specific template macros. Word Online does not run VBA.
COM add-ins: redlining tools (Litera Change-Pro), document management integrations (iManage Word add-in, NetDocuments ndOffice), document-automation platforms (HotDocs, Contract Express). All load into Word desktop and expect file paths.
Mail-merge with linked data sources: a Word merge document referencing an external data file (an Excel workbook, an Access database, a CSV) needs the data-source path to resolve. Path shifts between OneDrive-cached and SharePoint-native break merges.
Building-block templates stored at fixed paths: firms with governed template libraries expect templates at a specific path so document creation resolves consistently.

Cloud Drive Mapper presents SharePoint as a mapped drive, Word treats it like a network share, and the whole macro-and-add-in ecosystem carries on working. Add the CDM path to Word's Trusted Locations and VBA runs without prompts, just as it did from a traditional file server.

Access: the one Office app that is genuinely desktop-only

Microsoft Access is the Office application that most clearly needs a real filesystem. It manages .accdb (and legacy .mdb) database files that behave like small local databases: exclusive locks during writes, multi-user access via a shared network path, form and report objects stored inside the same file. Microsoft has not made Access a cloud-native product; there is no Access Online in the way there is Excel Online or Word Online.

That combination makes Access the standout case in the Office suite for a mapped-drive layer. The specific patterns that break under OneDrive sync:

Database corruption from partial syncs: the same pattern as QuickBooks .QBW files. Access writes continuously to the .accdb; if OneDrive uploads a mid-write state, the cloud copy can be corrupt.
Multi-user access breaks: traditional Access multi-user access relies on all users hitting the .accdb via a shared network path with exclusive-lock semantics. OneDrive-synced folders do not honour that model.
Split-database Access apps: many production Access deployments split the app into a front-end (.accde, on each user's desktop) and a back-end (.accdb, on shared storage). The front-end has hard-coded paths to the back-end. Path instability breaks linking.
Compact and Repair operations fail: Access's routine maintenance operation opens the file exclusively, rewrites it, replaces the original. Sync-timing during that operation can corrupt the resulting file.

Cloud Drive Mapper presents SharePoint as a Windows mapped drive, and Access treats it like a network share. Split-database front-end / back-end apps continue to link through stable paths. Compact and Repair operations complete cleanly because there is no sync client racing them. Multi-user access still requires the general Access-on-network-share considerations that Microsoft has documented for years, but CDM removes the OneDrive-specific corruption risk.

For finance teams, government departments, education administration and older firms that built their reporting infrastructure around Access years ago, this is often the single Office-side workflow that most needs CDM.

PowerPoint: templates, macros, presentation automation

PowerPoint macros are less common than Word or Excel macros, but they exist in specific contexts: management-reporting slide packs generated from data, sales deck automation, template-driven presentation assembly, training-material generators. PowerPoint template libraries referenced from a fixed path (firm-standard branding assets, approved slide banks) also depend on stable paths.

The pattern with CDM is the same as Word: PowerPoint treats the mapped drive as a network share, macros run from Trusted Locations, template libraries resolve consistently across every user's endpoint. PowerPoint Online co-authoring still works for the ordinary decks that suit it; CDM adds the desktop-Excel-equivalent surface for the more automated workflows.

Outlook: the parts that touch the filesystem

Outlook itself is not a file-based application; email lives in Exchange or Microsoft 365, not on a Windows filesystem. CDM does not sit in the mail flow. Where CDM matters for Outlook is on the file-based edges:

PST archive files: legacy or compliance-driven PSTs stored on file shares. Firms often keep large historical PSTs on network storage for regulatory reasons. CDM presents that storage as a mapped drive; Outlook opens the PST from there.
Email-filing add-ins: iManage Communications Manager, NetDocuments ndMail, DocsCorp cleanDocs and equivalents file emails from Outlook into a matter workspace. These add-ins use temp files at configured paths.
Signature templates and stationery: firm-standard signature and stationery files stored at a fixed path so every user's Outlook picks up the same version.
Attachments filed to SharePoint folders: dragging an email attachment into a SharePoint folder via a mapped drive is the same UX users had with a network share.

For firms whose email workflow includes any of the above, CDM's mapped-drive layer makes the Outlook-adjacent file operations work the way they always did.

How Cloud Drive Mapper fits with the Office suite

The pattern is consistent across every Office application: CDM does not replace SharePoint or OneDrive; it adds a mapped-drive view of SharePoint alongside them. Office treats the mapped drive as a network share, so macros run, add-ins work, cross-file references resolve, and Access databases stay uncorrupted. Co-authoring is still available on the workbooks and documents that suit it, through the SharePoint browser or the standard OneDrive path.

One workbook or document, two access paths, one source of truth in SharePoint.

Setting it up

Add the CDM drive letter to Trusted Locations in each Office application whose macros you rely on (Word, Excel, PowerPoint, Access). Push centrally via Group Policy or Intune.
Standardise the mapped-drive letter across the whole organisation so cross-document references and Access split-database front-ends resolve identically.
For Access split-database apps, update the linked-table paths in each front-end to point at the CDM drive; this is a one-time job per app.
For Outlook signature files and template locations, update Outlook's configured paths from OneDrive-synced folders to the CDM drive.
See the Excel on SharePoint page for the Excel-specific configuration detail.

Cloud Drive Mapper is used across accounting practices, government departments, finance teams and professional services firms to keep the file-based Office workflows (Access databases, Word macros, PowerPoint template libraries, Outlook filing) working on Microsoft 365 storage.

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

Frequently asked questions

Does the standard Microsoft Office suite work with OneDrive?

Yes, for most workflows. Word, Excel, PowerPoint and Outlook are Microsoft's own products and integrate cleanly with OneDrive and SharePoint for standard use. This page focuses on the specific patterns where the default integration hits limits: macros, add-ins, cross-document references, Access databases, and Outlook PST archives.

Does Microsoft Access work with SharePoint?

Access is a genuinely desktop-only Office application that lives on .accdb (and legacy .mdb) database files. It expects a real Windows file path, exclusive locks, and (for multi-user access) all users to reach the same file over the same network share. OneDrive sync does not meet these requirements well and can produce database corruption. CDM presents SharePoint as a mapped drive so Access treats the .accdb file like it did on a network share. This is the most desktop-anchored of the standard Office apps and the one where CDM adds the most value on the Office side.

Do Word macros and add-ins work through CDM?

Yes. Word treats a CDM-mapped drive the same way it treats any Windows network drive. VBA macros run under Word's Trusted Locations rules: add the mapped drive to Trusted Locations and macros run without security prompts. COM add-ins (industry-specific templates, redlining tools, document-automation platforms) load into Word at startup and operate on whatever document is open, so they do not care where the file lives as long as the path resolves.

Where does Outlook fit in?

Outlook is not primarily a file-based application (email lives in Exchange or Microsoft 365, not on a filesystem), so CDM does not sit in the mail flow itself. Where CDM matters for Outlook is around the file-based edges: PST archive files (legacy or compliance), signature templates stored at configured paths, attachments filed from Outlook into SharePoint folders (Outlook needs the folder to be reachable), and email-filing add-ins that assume a Windows file path.

What about PowerPoint templates and macros?

PowerPoint macros are less common than Word or Excel macros but exist in firms with template-driven or presentation-automation workflows (regular management reporting, industry-standard slide decks, custom sales-deck generation). Same pattern as Word: macros run from a CDM-mapped drive under PowerPoint's Trusted Locations. PowerPoint template libraries stored in SharePoint are accessible through the mapped drive with stable paths.

Does IAM Cloud have access to our Office documents?

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 organisation's signed-in users can access content through CDM, and only within their existing M365 permissions.

Try it with your Office estate

The fastest way to see if CDM fits your Office workflows is to try it for 30 days, free. Point Word, Access, PowerPoint or Outlook at a mapped drive and see how it behaves against a real workflow.

Start a free trial Request a demo