01
Get the expected resource
Ask what folder or department the user needs, how a working peer reaches it, and whether the resource normally appears as a drive letter, UNC path, SharePoint library, or OneDrive shortcut.
Everyday IT · Mapped Drives & File Access
Find the real resource before you map anything.
A user saying “my drive is missing” does not tell you whether the resource is an SMB share, a mapped drive, a SharePoint library, or a OneDrive-synced folder.Identify the source first. Then test path, connectivity, identity, and permissions.
The quick path
Do not create a new mapping until you know what the user is supposed to reach.
02
Test the source path
For an SMB resource, use the known UNC path directly. If the server or share cannot be reached, solve connectivity, VPN, DNS, or server availability before permissions.
03
Verify role-based access
Compare the user's approved group membership with a working peer. Avoid adding broad access just because the drive letter is missing.
04
Map only after access works
A drive mapping is a convenience layer. Prove the underlying path works first, then recreate the mapping if needed.
Drive letter, UNC path, SharePoint, or OneDrive?
File Explorer can make very different systems look similar.
Mapped drive
A drive letter points somewhere else
A mapped drive typically points to a network share such as a server and folder. The drive letter itself is not the data source.
UNC path
The direct network location
A UNC path is the cleaner test because it removes the drive-letter mapping from the equation.
SharePoint
A cloud document library
SharePoint access is controlled in Microsoft 365 and may appear in File Explorer only through sync or shortcuts.
OneDrive
A sync client and user storage layer
A OneDrive entry in File Explorer may represent the user's own files, a synced SharePoint library, or a shortcut to shared content. Verify which one before changing anything.
If access is denied
Separate reachability from authorization.
Reachability
Can the server and share be reached?
If not, permissions are not the first problem. Check network connection, VPN, DNS, server state, and the exact path.
Identity
Which account is actually being used?
Saved credentials, alternate domain accounts, stale sessions, or a local account can make the right path fail with the wrong identity.
Groups
Does the user have the intended role?
Use approved security groups and compare with a known-good peer. Newly added group memberships may require a sign-out or token refresh.
ACLs
Check effective access before redesigning permissions
If the correct group is present but access still fails, inspect share and NTFS permissions, inheritance, explicit entries, and nested groups before changing the folder design.
What not to do
Missing drives are easy to turn into permission sprawl.
Avoid
Mapping a guess
Do not map a path because its name sounds right. Confirm the approved resource and working path first.
Avoid
Giving direct Full Control
A broad direct permission can hide the real group or path problem and make future audits harder.
Avoid
Confusing OneDrive with a file server
Do not treat every File Explorer location as an SMB share. Cloud sync and network shares behave differently.
Escalate
When the access model is unclear
Pause if ownership is unclear, nested groups are complicated, child folders have unique permissions, or a line-of-business application depends on the path.
First prove the resource. Then prove the path. Then prove the access.