Bluebeam Revu and Microsoft 365 storage
SOLUTION GUIDE
Bluebeam Revu is the construction industry's PDF markup standard. Architects, engineers, main contractors, sub-contractors and quantity surveyors live in it for drawing review, takeoffs, RFIs, submittals and punchlists. The workflows Revu supports are unforgiving of unreliable file behaviour: large drawing sets that get marked up and re-shared many times a week, custom tool chests standardised across a project team, revision comparisons between versions of a drawing, and Bluebeam Studio Sessions that pull the whole team into a live collaboration on a single file. Cloud Drive Mapper presents SharePoint as a Windows mapped drive so Revu treats Microsoft 365 storage the way it treats a traditional network file share.
What breaks when Bluebeam Revu runs against OneDrive-synced storage?
Five patterns show up across construction firms that put project drawing folders on OneDrive without a mapped-drive layer.
Large drawing sets create sync churn
A construction drawing set is often a single PDF running to hundreds of pages and hundreds of megabytes. Every markup write updates the file. OneDrive sees the change and tries to sync the whole file back. On a busy site week, sync bandwidth becomes the bottleneck and users start opening old cached versions because the sync has not caught up.
Custom tool chest files fall out of sync
Firms standardise on custom tool chests (Revu's
.btx files) that hold approved stamps, symbols
and markup styles for consistency across the project team.
When those files live in OneDrive-synced folders, sync-timing
issues mean different team members can be running slightly
different tool chest versions on the same day, and stamps
drift.
Revision comparisons fail on unhydrated files
Revu's revision comparison feature opens two PDFs and diffs them page by page. If either file is a Files On-Demand stub that has not been hydrated, the comparison fails or returns partial results. In a drawing review workflow where the whole point is to see the difference between Rev C and Rev D, that failure mode is unacceptable.
Batch operations skip or duplicate
Revu ships with Batch Slip Sheet, Batch Link, Overlay Pages, Batch Export and other bulk operations that iterate through folders of PDFs. Sync-timing artefacts against OneDrive-synced folders cause files to be skipped, processed twice, or written to wrong locations. Users end up re-running batches to be sure they completed cleanly.
Conflict copies of drawing PDFs
When two team members open the same drawing at once and OneDrive cannot reconcile their changes, it produces a "Conflict copy from <username> on <date>" of the drawing PDF. Merging construction markups between two versions of the same drawing is essentially manual, and losing markup information means losing agreed changes. Site teams find themselves with three or four versions of the same drawing and no clear canonical one.
Why Bluebeam Revu needs real file paths
Revu is a Windows desktop application designed against a filesystem model that construction firms have used for decades: network file shares with proper exclusive locks, stable file paths, and no third party moving files around mid-session. Traditional file servers meet those needs. The OneDrive sync client does not, and construction is one of the sectors where the gap shows up most obviously because drawing files are large, change often, and are touched by multiple people every day.
For the broader take on why sync clients struggle with applications that assume they own the filesystem, see Desktop applications and real file paths. Bluebeam Revu sits in the same family as AutoCAD and other construction desktop applications on this axis.
How Cloud Drive Mapper fits with Bluebeam Revu
Drawing sets open from a real Windows drive letter
CDM maps SharePoint document libraries as drive letters
(M:, N:, whatever you configure).
Revu opens PDFs from the mapped drive the same way it would
from a network share. Large drawing sets stream on demand:
opening a drawing downloads only what Revu requests, and
writes stream changed blocks back to SharePoint rather than
re-uploading the whole file.
Custom tool chests stay standardised
Store the firm's standard .btx tool chest
files in a SharePoint document library mapped through CDM.
Every user's Revu loads the shared tool chest from the same
mapped path, so custom stamps, symbols and markup styles
stay consistent across the project team. A tool chest
update saved back to SharePoint propagates the moment the
file is written, without sync-timing drift.
Revision comparison works because paths resolve
Both files in a revision comparison are directly accessible through the mapped drive with no hydration delay. Diff runs complete, side-by-side view opens with both revisions visible, review moves forward.
Batch operations run cleanly
Batch Slip Sheet, Batch Link, Overlay Pages, Batch Export and similar bulk operations execute against the mapped drive with no sync-timing artefacts. A batch run on a folder of drawings completes without files being skipped or duplicated.
Studio Sessions integrate cleanly
Bluebeam Studio Sessions run through Bluebeam's own cloud service, independent of where the source PDF originally lived. Files hosted on a CDM-mapped drive can be added to a Studio Session, collaborated on live by the project team, and pulled back into the SharePoint-hosted file when the session finishes. CDM does not sit in the Studio flow; it makes the source and destination PDF reachable through Windows Explorer.
SharePoint check-out replaces conflict copies
When a team member opens a drawing PDF from a CDM-mapped drive, CDM triggers a SharePoint check-out. A second team member opening the same drawing sees it as checked out and receives a read-only copy. There is no scenario where two concurrent markup sessions produce a conflict copy of the drawing PDF.
Bluebeam-specific setup notes
- Standardise the CDM drive letter across every user in the project team so shared tool chest paths resolve identically.
- Store the firm's standard
.btxtool chest files in a SharePoint document library mapped through CDM, and point every user's Revu at the mapped path. - Update Revu's default open/save location and any batch operation output paths from OneDrive-synced folders to the CDM drive.
- Studio Sessions continue to run through Bluebeam's own service; nothing to configure on the CDM side.
- If moving from a previous OneDrive-synced folder setup, run a Revu Repair (or reopen problematic PDFs) before migrating any drawings that showed corruption or missing markups previously.
CDM supports Bluebeam Revu in the following deployment models:
- Windows desktops (direct)
- Citrix Virtual Apps and Desktops
- Citrix DaaS
- Azure Virtual Desktop (AVD)
- Windows 365 Cloud PC
- Omnissa Horizon (formerly VMware Horizon)
Cloud Drive Mapper is used across construction firms, architects and engineering practices to keep Bluebeam Revu working cleanly against Microsoft 365 storage instead of a local file server.
Frequently asked questions
Does Bluebeam Revu work with Microsoft 365 storage through Cloud Drive Mapper?
Yes. CDM presents SharePoint as a Windows mapped drive
letter. Bluebeam Revu opens PDFs from the mapped drive the
same way it would from a traditional network file share.
Large drawing sets, custom tool chest .btx
files, project-wide markup workflows and revision
comparisons all resolve through stable paths, and Revu
treats the mapped drive as if it were a file server.
Do Bluebeam Studio Sessions still work when files are on a CDM-mapped drive?
Yes. Studio Sessions run through Bluebeam's own cloud service, independent of where the source PDF originally lived. Files hosted on a CDM-mapped drive can be added to a Studio Session, collaborated on live, and pulled back into the SharePoint-hosted file when the session finishes. CDM does not sit in the Studio flow; it makes the source and destination PDF reachable through Windows Explorer.
Can custom tool chests (.btx files) be shared across the team via CDM?
Yes. Store the firm's standard tool chest .btx
files in a SharePoint document library mapped through CDM.
Every user's Revu can load the shared tool chest from the
mapped drive, so custom stamps, symbols and markup styles
stay consistent across the project team. Updates to a
shared tool chest propagate the moment the file is saved
back.
Do large drawing sets (multi-hundred-page PDFs, 100MB+ files) perform well on CDM?
Yes. CDM streams file content on demand from Microsoft 365 rather than syncing a full local mirror. Opening a large drawing set downloads only what Revu requests, and saves stream changed blocks back to SharePoint rather than re-uploading the whole file. Performance is comparable to a network share, which is what construction firms tuned Bluebeam workflows for originally.
Do revision comparisons and Batch operations work with CDM?
Yes. Revu's revision comparison (comparing two versions of a drawing side by side) needs both files to be reachable at real file paths, which CDM provides. Batch Slip Sheet, Batch Link, Overlay Pages and other batch operations that iterate through folders of PDFs run against the mapped drive the same way they would against a network share, without the sync-timing artefacts a OneDrive-synced folder can introduce.
Does IAM Cloud have access to our project drawings?
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. See Zero-access architecture for the design detail.
Related solutions
Try it with your drawing sets
The fastest way to see if CDM fits your Bluebeam workflow is to try it for 30 days, free. Open a real project drawing set from a mapped drive and run a batch operation on it.