Map Network Drive / WebDav with SharePoint Online O365

WebDav with SharePoint Online O365

Issue: While Mapping a Drive to SharePoint Online it fails with below error.

Error: The Mapped Network Drive could not be created because the following error has occurred.
'Access Denied'. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site and select the option to login Automatically.




  1. Open IE -> Go to ‘Internet Options’
  2. Select ‘Security’ tab -> Select ‘Internet’ Zone.
  3. UnCheck the box for ‘Enable Protected Mode


Issue: You are using SharePoint workspace and when you try to save the file opened from Workspace. The Save location changes to local machines Temp folder instead of SharePoint Online Library from where the file was accessed. While Saving or ‘Save As’ , the location should default to the SharePoint Online library itself and not the local machines temp folder.

Check / Troubleshoot:

  1. Make sure the ‘Web Client’ service is started on the client machine.

  2. Open the SPO site -> go to the Document Library

  3. Select ‘Open with Explorer’ [ Make sure this is working fine ]

  4. Delete IE Cache.

  5. In IE ‘Trusted Sites’ zone add





Note: This is basically working on the WebDav functionality to work which is related to “Open in Explorer” mode from a SharePoint Document library. If you notice that the library does not open in Explorer Window from the site directly, your Save As option will redirect you to temp folder instead of the Site URL.


Note: Some users may complain that after certain period of time the mapped drive disconnects or they are asked to enter the credentials again for O365. This will happen if the time period has extended over 8 hours. This is default behavior by Design. They will need to refresh the credentials. This may also occur if users have not selected “Keep me signed in” checkbox while they sign in through Microsoft Online sign-in assistant.


Users can't sign out of Office 365 web services


Note: this is known issue with Office 2013 64 Bit version. it will not work