Migrating files from Sharepoint Online document libraries to Azure Storage Accounts

%3CLINGO-SUB%20id%3D%22lingo-sub-192509%22%20slang%3D%22en-US%22%3EMigrating%20files%20from%20Sharepoint%20Online%20document%20libraries%20to%20Azure%20Storage%20Accounts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-192509%22%20slang%3D%22en-US%22%3EIs%20this%20possible%20to%20do%20that%20exclusively%20in%20365-Azure%3F%20Trying%20to%20bypass%20the%20%22download%20the%20files%20from%20sharepoint%20to%20a%20local%20computer%22%20part...This%20would%20be%20like%20using%20the%20Migration%20Tool%20(local%20computer%20to%20Azure%20blob%20to%20SharePoint%20Doc%20Lib)%20in%20reverse.%20Perhaps%20a%20Powershell%2FCSOM%20way%3F%20You%20might%20ask%20why%20this%20is%20a%20need%3F%20Its%20the%20File%20Explorer%20davwwwroot%20not%20working%20issue%20that%20drives%20the%20%22save-as%22%20to%20SharePoint%20Libraries%20pain%20point.%20The%20loss%20of%20productivity%20isn't%20good...and%20we%20can't%20authorize%20using%20the%20OD%20Sync%20client%20as%20a%20File%20Explorer%20solution%20because%20there%20isn't%20an%20option%20yet%20to%20just%20'view'%20the%20files%20but%20not%20sync%20them%20using%20the%20sync%20client%20to%20SharePoint%20Online%20Libraries%20yet.%20The%20OneDrive%20option%20itself%20though%20is%20amazingly%20helpful..wish%20that%20could%20be%20applied%20to%20SharePoint.%20So%20much%20'office%20pain'%20could%20be%20avoided...%20and%20now%20we%20have%20to%20return%20to%20local%20storage%20but%20using%20the%20Azure%20File%20Sync%20setup%20makes%20the%20local%20storage%20far%20cheaper%20because%20of%20the%20hot%2Fcold%20file%20Tiering%20(you%20can%20hold%20a%20fraction%20of%20the%20total%20data%20on%20prem%20thus%20reducing%20the%20need%20for%20large%20expensive%20SAN%20arrays).%20Thanks%20in%20advance%20for%20any%20advice%20on%20this%20one!%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-192509%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPowerShell%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-192735%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20files%20from%20Sharepoint%20Online%20document%20libraries%20to%20Azure%20Storage%20Accounts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-192735%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20reply...still%20not%20sure%20if%20you%20can%20directly%20copy%20from%20SPO%20to%20an%20Az%20storage%20account.%20Am%20trying%20to%20avoid%20having%20the%20file%20stream%20reach%20our%20premises.%20You%20asked%20why%20go%20from%20SPO%20to%20Azure%20Storage%3F%20Its%20the%20pain%20of%20working%20with%20non-Office%20files%20(pdf's%20really)%20in%20sharepoint.%20Our%20users%20just%20can't%20let%20go%20of%20the%20File%20Explorer%2C%20and%20wwwdavroot%20has%20become%20quite%20problematic%20(non-working)%20for%20many%20of%20our%20Admin%20users%20enough%20so%20to%20force%20an%20alternate%20solution%20like%20Az%20File%20Sync%20to%20reduce%20the%20loss%20of%20productivity.%20Using%20the%20OneDrive%20sync%20client%20would%20be%20ideal%20in%20its%20current%20iteration%20for%20this%20case%20as%20a%20File%20Explorer%20replacement...but%20the%20data%20being%20accessed%20is%20not%20allowed%20to%20be%20sync'd.%20(you%20wouldn't%20want%20dept.%20shared%20data%20sync'd%20to%20yon%20random%20staff's%20home%20machine)...and%20there%20is%20no%20granular%20control%20available%20yet%20that%20could%20block%20sync%20but%20still%20let%20the%20files%20be%20browsed%20at%20the%20Doc%20Library%20level%20thus%20turning%20the%20OneDrive%20Sync%20client%20into%20a%20true%20SharePoint%20file%20explorer...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-192592%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20files%20from%20Sharepoint%20Online%20document%20libraries%20to%20Azure%20Storage%20Accounts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-192592%22%20slang%3D%22en-US%22%3EMight%20I%20ask%20why%20do%20you%20need%20to%20migrate%20files%20from%20SPO%20to%20Azure%20Storage%3F%20By%20the%20way%2C%20if%20you%20are%20looking%20for%20an%20automated%20way%20to%20do%20this%2C%20definitively%20CSOM%20API%20is%20the%20answer%20on%20the%20SPO%20side%20and%20I%20think%20you%20can%20get%20the%20same%20on%20the%20Azure%20part.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor
Is this possible to do that exclusively in 365-Azure? Trying to bypass the "download the files from sharepoint to a local computer" part...This would be like using the Migration Tool (local computer to Azure blob to SharePoint Doc Lib) in reverse. Perhaps a Powershell/CSOM way? You might ask why this is a need? Its the File Explorer davwwwroot not working issue that drives the "save-as" to SharePoint Libraries pain point. The loss of productivity isn't good...and we can't authorize using the OD Sync client as a File Explorer solution because there isn't an option yet to just 'view' the files but not sync them using the sync client to SharePoint Online Libraries yet. The OneDrive option itself though is amazingly helpful..wish that could be applied to SharePoint. So much 'office pain' could be avoided... and now we have to return to local storage but using the Azure File Sync setup makes the local storage far cheaper because of the hot/cold file Tiering (you can hold a fraction of the total data on prem thus reducing the need for large expensive SAN arrays). Thanks in advance for any advice on this one!
2 Replies
Highlighted
Might I ask why do you need to migrate files from SPO to Azure Storage? By the way, if you are looking for an automated way to do this, definitively CSOM API is the answer on the SPO side and I think you can get the same on the Azure part.
Highlighted
Thanks for the reply...still not sure if you can directly copy from SPO to an Az storage account. Am trying to avoid having the file stream reach our premises. You asked why go from SPO to Azure Storage? Its the pain of working with non-Office files (pdf's really) in sharepoint. Our users just can't let go of the File Explorer, and wwwdavroot has become quite problematic (non-working) for many of our Admin users enough so to force an alternate solution like Az File Sync to reduce the loss of productivity. Using the OneDrive sync client would be ideal in its current iteration for this case as a File Explorer replacement...but the data being accessed is not allowed to be sync'd. (you wouldn't want dept. shared data sync'd to yon random staff's home machine)...and there is no granular control available yet that could block sync but still let the files be browsed at the Doc Library level thus turning the OneDrive Sync client into a true SharePoint file explorer...