Well my organization current moto is to create hundred of different sharepoint sites that can contain multiple document libraries to compartmentalize (I persona

Well my organization current moto is to create hundred of different sharepoint sites that can contain multiple document libraries to compartmentalize (I personally think it's a really bad idea but i have to comply). So when you happen to work with 10+ Sharepoint sites there is two way to operate if you must sync. 1. Click sync on the document library. Then each sync while need a configuration entry in One Drive and each sync will create it's own background worker. Prioritization between sync/mounts point must happen somehow but if you open 10+ I experienced lot's of sync error/delay. Sync parameters to each sharepoint have to be defined manually and independently on all your devices. 2.You can add a "shortcut" pointing to the sharepoint into your organization (personal) OneDrive. The configuration is then stored on your OneDrive profile, it's synchronized across all you device and the OneDrive webapp. You can move the shortcut around (inside your OneDrive) and rename the folder as you which. It only require one background worker that don't compete for system ressources with others. I was initially configured using solution 1 and experienced many conflict/lag/bug. Since I implemented aolution 2 everything is (almost) flawless. So the question remain why do they offer two concuring implementations one of which can lead to madness... legacy support I guess.