Map a network drive to sharepoint onedrive for business

The best practice in SharePoint is to create many sites and many libraries as you split content by function and security. As your library grows in size, you will see degraded performance If you have a very deep folder hierarchy, you will encounter it one day. Sooner or later you will encounter SharePoint technical limitations. Below I would like to present few reasons why, in my opinion, you should not create any mapped drives with SharePoint.ДonвЂ™t have time to read the post? You can listen to the Podcast episode on the same topic below.

ThatвЂ™s not what SharePoint was designed for. If this is your wish, so be it, but I would argue against using SharePoint for this purpose.

вЂњWe want to collaborate the same way we did for the last 20 yearsвЂќ When you map a SharePoint document library, you essentially say: I have written a post previously where I cautioned against using SharePoint as a file share. What usually follows is a dismal user experience from a performance standpoint and badmouthing of SharePoint and anyone who made a decision to migrate to Office 365. Companies purchase Office 365 subscription, create a single site in SharePoint with a single document library, migrate their whole file share into that single library, map it as a network drive and call the project complete. I see this happening over and over again.

Map a network drive to sharepoint onedrive for business