
Map SharePoint document libraries as network drives using OneDrive sync, WebDAV, or Azure Files — with GPO deployment, Intune configuration, troubleshooting, and enterprise security guidance.
How do you map SharePoint as a network drive? The recommended method is OneDrive Sync Client: open the SharePoint document library in your browser, click the Sync button, and the library appears in Windows File Explorer with full offline access and Files On-Demand. For legacy drive letter requirements, use WebDAV mapping (Map Network Drive with the SharePoint library URL) or Azure Files with SMB mounting. OneDrive sync is superior for 90%+ of enterprise scenarios because it supports offline access, handles files up to 250GB, manages 300,000+ items per library, and is centrally managed via GPO or Intune. EPC Group deploys SharePoint file access strategies as part of our enterprise SharePoint consulting engagements.
Users have been accessing files through network drives for 30 years. When organizations migrate file servers to SharePoint Online, the most common user request is: "Can I still see my files in File Explorer with a drive letter?" The answer is yes — but the method you choose has massive implications for performance, reliability, security, and supportability.
The traditional approach — mapping SharePoint as a WebDAV network drive with a letter like Z: — technically works but creates a fragile, slow connection that disconnects after idle periods, fails with large files, and bypasses modern security controls. It is the approach that generates the most helpdesk tickets in any SharePoint migration. The modern approach — OneDrive sync — provides a far superior experience but requires users to abandon the drive letter mental model and navigate to their organization folder in File Explorer instead.
This guide covers all three methods for accessing SharePoint files from File Explorer — OneDrive sync, WebDAV mapped drives, and Azure Files — with honest assessments of when each is appropriate, how to deploy at enterprise scale via GPO and Intune, how to troubleshoot the most common errors, and the performance and security implications of each approach.
EPC Group has migrated over 500 organizations from traditional file servers to SharePoint Online, and the file access strategy is consistently the factor that determines whether users love or hate the migration. Get this right and the migration succeeds. Get it wrong and users revolt, create shadow IT workarounds, and the migration is perceived as a failure regardless of how well the data was moved. For complete SharePoint document management guidance, see our SharePoint document management enterprise guide.
Three methods for accessing SharePoint files from File Explorer. Each serves a different use case — but OneDrive sync is the right choice for the vast majority of enterprise users.
Modern, cloud-native synchronization with offline support and Files On-Demand.
Legacy drive letter mapping with significant limitations for SharePoint Online.
Enterprise-grade SMB file shares synced with SharePoint for legacy compatibility.
Group Policy is the standard deployment method for Active Directory-joined Windows devices. The following GPO settings configure OneDrive to automatically sync SharePoint libraries without any user interaction — users log into their PC and their SharePoint files appear in File Explorer immediately.
Deploy the per-machine OneDrive installer (OneDriveSetup.exe /allusers) via SCCM software deployment or GPO software installation. The per-machine install ensures OneDrive is available for all user profiles on shared workstations and conference room PCs. Verify installation by checking for OneDrive.exe in C:\Program Files\Microsoft OneDrive.
GPO Path: Computer Configuration > Policies > Administrative Templates > OneDrive. Enable "Silently sign in users to the OneDrive sync app with their Windows credentials". This uses the Windows login credentials to automatically configure OneDrive — no user interaction, no sign-in prompt, no confusion. Requires Azure AD Connect with password hash sync or pass-through authentication.
Enable "Silently move Windows known folders to OneDrive" with your tenant ID. This redirects Desktop, Documents, and Pictures from the local C: drive to OneDrive, protecting user data from hardware failure and enabling access from any device. Set the prompt option to prevent users from redirecting folders back to local storage.
Configure "Configure team site libraries to sync automatically" with the library ID of each SharePoint library you want to auto-sync. Find the library ID in the SharePoint admin center or via PowerShell (Get-SPOSite). This ensures users get the correct departmental SharePoint libraries without clicking Sync manually.
Set "Use OneDrive Files On-Demand" to Enabled. This is critical for large libraries — without Files On-Demand, syncing a 100GB library downloads all 100GB to every user device. With Files On-Demand, files appear in Explorer but only download when opened, reducing initial sync to metadata only (seconds instead of hours).
For Azure AD-joined devices managed by Microsoft Intune (no on-premises Active Directory), use Settings Catalog configuration profiles to deploy the same OneDrive sync settings without Group Policy. Intune is the recommended approach for organizations that have adopted cloud-only device management.
These are the five most common SharePoint drive mapping errors that generate helpdesk tickets. Most of them are inherent WebDAV limitations that disappear when migrating to OneDrive sync.
WebClient service is not running or the SharePoint URL format is incorrect.
WebDAV has a default 50MB upload limit configured in the Windows registry.
WebDAV session cookies expire after 30-60 minutes of inactivity.
Modern authentication failure, cached credential conflicts, or conditional access blocking.
Conditional access policy blocking WebDAV traffic or insufficient SharePoint permissions.
Files On-Demand, delta sync, handles 300K+ files, up to 250GB per file. Initial sync is metadata-only (seconds).
Every operation requires network round-trip. 5,000+ files per folder causes timeouts. 50MB default upload limit. Synchronous file saves freeze applications.
SMB 3.0 performance with 1-5ms metadata latency. Throughput scales with selected tier. Best for legacy application compatibility.
Azure AD auth with MFA, conditional access, BitLocker on endpoint, Files On-Demand prevents bulk exfiltration, selective wipe on departure.
No conditional access enforcement, session cookies in memory, all files physically on disk, no compliance checking, credentials may be cached insecurely.
Azure AD Kerberos auth, encryption at rest, private endpoints, RBAC permissions, but requires proper network configuration to avoid exposure.
The correct file access method depends on three factors: whether the user needs offline access, whether a legacy application requires a drive letter path, and whether the organization prioritizes security or backward compatibility. Here is the decision framework EPC Group uses for every SharePoint migration.
For any user who accesses SharePoint files through Office apps, File Explorer, or web browser. Provides the best combination of performance, offline access, security, and manageability. Deploy automatically via GPO or Intune — zero user action required. This is the answer for knowledge workers, executives, managers, and anyone who primarily uses Microsoft 365 apps.
Only for legacy applications that require a drive letter path (e.g., engineering software that reads CAD files from H:\Projects\). Document each mapped drive as technical debt with a modernization plan. Set a review date (6-12 months) to evaluate whether the legacy application can be updated to use UNC paths or cloud storage APIs. Never deploy WebDAV mapped drives as the default access method.
For organizations with on-premises servers that need shared access to the same files as cloud users, or legacy applications requiring true SMB 3.0 protocol (not WebDAV emulation). Azure Files provides enterprise-grade SMB file shares with Azure AD authentication, private endpoints, and configurable performance tiers. Higher infrastructure cost but eliminates WebDAV limitations entirely.
Enterprise SharePoint consulting — migration, governance, architecture, and optimization.
Read moreComplete guide to enterprise document management on SharePoint Online.
Read moreTop SharePoint migration service providers for enterprise file server and legacy migrations.
Read moreThere are 3 methods to map SharePoint as a network drive: 1) OneDrive Sync Client (Recommended) — the modern approach. Open the SharePoint document library in a browser, click "Sync", and OneDrive sync client maps the library to Windows File Explorer as a local folder under your OneDrive organization. Files sync automatically, work offline, and support co-authoring. No drive letter required. 2) WebDAV Mapped Drive — the legacy approach. In Windows File Explorer, click "Map network drive", enter the SharePoint library URL (https://tenant.sharepoint.com/sites/sitename/Shared%20Documents), and authenticate. This creates a traditional drive letter (e.g., Z:) but requires persistent internet connectivity, has poor performance with large files, and session cookies expire causing frequent re-authentication. 3) Azure Files with Private Endpoint — the enterprise approach for hybrid scenarios. Create an Azure Files share, sync SharePoint content via Logic Apps or Power Automate, and mount the Azure Files share as a traditional SMB network drive. This provides the best of both worlds but adds infrastructure complexity. For most enterprise scenarios, EPC Group recommends OneDrive sync as the primary method with Azure Files for legacy application compatibility.
OneDrive sync and mapped drives serve the same user need (access SharePoint files from File Explorer) but work fundamentally differently: OneDrive Sync — files appear in File Explorer under the organization name, supports Files On-Demand (files download only when opened, saving disk space), works offline with automatic sync when connectivity returns, supports co-authoring (multiple users editing simultaneously), handles large files efficiently (up to 250GB per file), and is managed centrally via Group Policy or Intune. Mapped Drive (WebDAV) — creates a traditional drive letter (Z:, S:, etc.), requires continuous internet connectivity (no offline access), session cookies expire after 30-60 minutes of inactivity causing disconnection, has a file size upload limit of approximately 50MB via WebDAV, performance degrades significantly with folders containing 5,000+ files, and is not supported by Microsoft for SharePoint Online (legacy method). The key difference: OneDrive sync is a robust, offline-capable, cloud-native synchronization engine. WebDAV mapped drives are a compatibility layer that makes SharePoint pretend to be a file server — and it pretends poorly. For enterprise environments, OneDrive sync is the correct choice in 95% of scenarios.
GPO deployment of OneDrive sync for SharePoint requires 5 configuration steps: 1) Install OneDrive sync client — deploy the per-machine installer (OneDriveSetup.exe /allusers) via SCCM or GPO software installation. The per-machine install ensures all users on shared workstations get OneDrive. 2) Configure silent account sign-in — enable the GPO "Silently sign in users to the OneDrive sync app with their Windows credentials" to auto-configure OneDrive using the user Azure AD credentials. No user action required. 3) Configure Known Folder Move — enable "Silently move Windows known folders to OneDrive" to redirect Desktop, Documents, and Pictures to OneDrive. This protects user data from local disk failure. 4) Configure SharePoint library sync — use the "Configure team site libraries to sync automatically" GPO with the SharePoint library ID to auto-sync specific document libraries for target users. 5) Enable Files On-Demand — set "Use OneDrive Files On-Demand" GPO to prevent full synchronization of large libraries. Files appear in Explorer but download only when accessed, saving disk space. All GPO templates are available in the OneDrive admin ADMX files from Microsoft.
Intune deployment of SharePoint access uses OneDrive sync configuration profiles: 1) Create a Settings Catalog profile in Intune (Devices > Configuration profiles > Create > Settings Catalog). 2) Add OneDrive settings: "Silently sign in users" (enabled), "Files On-Demand" (enabled), "Known Folder Move" (enabled with tenant ID), and "Configure team site libraries to sync automatically" (with library IDs). 3) For legacy mapped drive requirements, deploy a PowerShell script via Intune that creates drive mappings: the script authenticates via WAM (Web Account Manager), obtains a SharePoint access cookie, and creates the mapped drive using net use. 4) Assign the configuration profile to device groups or user groups. 5) Monitor deployment status in Intune reports. Important: Microsoft officially recommends OneDrive sync over mapped drives for Intune-managed devices. If legacy applications require a drive letter, use the Intune PowerShell script approach but document it as technical debt to be addressed when the legacy application is modernized.
The 5 most common SharePoint drive mapping errors: 1) "The network path was not found" — cause: WebClient service not running or SharePoint URL format incorrect. Fix: start the WebClient service (net start WebClient), verify URL uses HTTPS and includes the document library path, not just the site URL. 2) "The file size exceeds the limit allowed" — cause: WebDAV has a default 50MB upload limit. Fix: increase the FileSizeLimitInBytes registry value at HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters (set to 4294967295 for 4GB max). 3) "The mapped drive disconnects after idle time" — cause: WebDAV session cookies expire after 30-60 minutes. Fix: increase the ServerNotFoundCacheLifeTimeInSec registry value, or better yet migrate to OneDrive sync which does not have this limitation. 4) "Access denied" or repeated authentication prompts — cause: modern authentication failure or Windows credential manager conflicts. Fix: clear cached credentials in Windows Credential Manager, ensure the SharePoint URL is in the Trusted Sites zone, and verify multi-factor authentication is completed. 5) "The remote server returned an error: 403 Forbidden" — cause: conditional access policy blocking the connection. Fix: verify that the device meets compliance requirements and that WebDAV traffic is not blocked by conditional access policies.
Performance varies dramatically by method: OneDrive Sync performance — excellent. Files On-Demand means only accessed files consume bandwidth and disk space. Initial sync of a 50GB library takes 2-8 hours depending on connection speed, but subsequent syncs are incremental (only changed files). Co-authoring uses delta sync, transferring only changed portions of files. Libraries with 300,000+ files sync reliably. WebDAV Mapped Drive performance — poor to unusable at scale. Every File Explorer operation (browsing, sorting, searching) requires a network round-trip. Opening a folder with 1,000 files takes 5-15 seconds. Opening a folder with 10,000 files may timeout entirely. File save operations are synchronous — the application freezes until the upload completes. Large file operations (50MB+) frequently fail. WebDAV connections consume persistent HTTP sessions on the SharePoint server, which can hit throttling limits with many concurrent users. Azure Files performance — good. Provides SMB 3.0 performance characteristics with Azure infrastructure. Typical latency of 1-5ms for metadata operations. Throughput scales with the selected tier (Transaction Optimized, Hot, Cool). Best for legacy applications that require true SMB/CIFS protocol compatibility.
Security considerations by method: OneDrive Sync — most secure option. Authentication uses Azure AD with full MFA support. Data in transit encrypted via TLS 1.2+. Data at rest on the endpoint is protected by BitLocker (if enabled via Intune). Conditional access policies apply (device compliance, location, risk level). Files On-Demand prevents bulk data exfiltration — files are not physically on disk until accessed. Information Rights Management (IRM) labels persist on synced files. Selective wipe removes synced files when an employee departs. WebDAV Mapped Drive — weakest security. Basic authentication sends credentials in base64 encoding (not encrypted) unless HTTPS is enforced. No conditional access policy enforcement. No compliance checking of the device. Session cookies stored in memory can be intercepted. All files are physically accessible on the device once mapped — no Files On-Demand protection. Disconnected sessions may leave cached credentials accessible. Azure Files — strong security with proper configuration. Supports Azure AD Kerberos authentication. Data encrypted at rest with Azure Storage encryption. Private endpoints eliminate public internet exposure. Conditional access can be enforced at the Azure AD level. RBAC controls file-level permissions.
Decision matrix for SharePoint file access method: Use OneDrive Sync when: users need offline access, you want Files On-Demand for disk space optimization, co-authoring is required, the organization is cloud-first with modern Windows 10/11 devices, and IT wants centralized management via GPO or Intune. This is the correct choice for 90% of enterprise scenarios. Use WebDAV Mapped Drive when: a legacy application requires a drive letter path (e.g., C:\Program Files\LegacyApp that reads from Z:\), the application cannot be modified to use UNC paths or OneDrive paths, and the files are small (<50MB) and the library is small (<5,000 files). Document this as technical debt. Use Azure Files when: legacy applications require true SMB protocol (not WebDAV), high-performance file access is needed from Azure-hosted applications, you need hybrid scenarios where on-premises servers and cloud services both access the same files, or regulatory requirements mandate data residency in a specific Azure region. EPC Group recommends OneDrive sync as the default, with Azure Files for specific legacy compatibility requirements.
Migration from mapped drives to OneDrive sync follows 5 steps: 1) Inventory current mapped drives — identify all GPO-deployed and manually configured mapped drives using a PowerShell script that scans HKCU\Network registry keys across all managed devices. Document which SharePoint sites and libraries each drive maps to. 2) Pilot OneDrive sync — deploy OneDrive sync to 50-100 users who currently use mapped drives. Configure auto-sync for the same SharePoint libraries they previously accessed via mapped drives. Collect feedback on usability and performance for 2-4 weeks. 3) Configure equivalent OneDrive sync — for each mapped drive, identify the corresponding SharePoint library and configure either auto-sync via GPO/Intune or provide users with a one-click sync button in the SharePoint browser interface. 4) Parallel run — run both mapped drives and OneDrive sync simultaneously for 2-4 weeks so users can transition at their own pace and verify that all files and workflows function correctly. 5) Remove mapped drives — disable the GPO or Intune configuration that deploys mapped drives. Send communication explaining the change with instructions for accessing files via OneDrive sync in File Explorer. Keep mapped drive GPO disabled (not deleted) for 30 days in case rollback is needed.
SharePoint drive mapping on macOS has important differences from Windows: OneDrive Sync on macOS — fully supported. The OneDrive sync client for macOS provides the same functionality as Windows: Files On-Demand, SharePoint library sync, Known Folder Move (for Desktop and Documents), and Finder integration. Deploy via Intune MDM, Jamf, or manual installation. This is the recommended approach for macOS. WebDAV on macOS — partially functional but problematic. macOS Finder supports "Connect to Server" (Cmd+K) with SharePoint URLs, but: authentication frequently fails with modern auth and MFA, Finder WebDAV implementation has file size limits and timeout issues, macOS does not support the WebClient service registry tweaks available on Windows, and Apple has not updated the WebDAV client to handle SharePoint Online authentication changes. Azure Files on macOS — supported via SMB 3.0. Mount Azure Files shares using Finder Connect to Server with the smb:// protocol. Requires port 445 outbound (often blocked by corporate firewalls). For enterprise macOS environments, EPC Group exclusively recommends OneDrive sync client. Do not attempt WebDAV mapped drives on macOS — the compatibility issues create persistent helpdesk tickets that are not worth the engineering effort to resolve.
Schedule a free SharePoint file access assessment. We will audit your current drive mapping configuration, identify reliability and security gaps, and deploy OneDrive sync with enterprise governance that eliminates helpdesk tickets and keeps data secure.