SOLVED
Home

Shared files via OneDrive not updating

%3CLINGO-SUB%20id%3D%22lingo-sub-37089%22%20slang%3D%22en-US%22%3EShared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37089%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%20%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWell%20we%20are%20giving%20MS%20teams%20a%20go%20and%20trying%20a%20few%20things%20that%20we%20would%20like%20to%20use.%3C%2FP%3E%3CP%3EOne%20feature%20we%20like%20is%20the%20File%20sharing%20in%20the%20teams.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20i%20noticed%20is%20that%20when%20i%20share%20a%20file%20from%20our%20OneDrive%20%2C%20once%20i%20make%20some%20changes%20to%20it%20no%20one%20in%20the%20team%20Chat%20sees%20the%20changes.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20normal%20or%20am%20i%20missing%20something%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-37089%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-558708%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-558708%22%20slang%3D%22en-US%22%3E%3CP%3EThis%26nbsp%3Bstill%26nbsp%3Bhas%26nbsp%3Bnot%26nbsp%3Bbeen%26nbsp%3Bfixed...How%26nbsp%3Bdoes%20this%20not%20drive%20people%20crazy%3F%20Does%20anyone%20know%20of%20a%20way%20to%20contact%20Microsoft%20with%20this%20issue%3F%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F35025%22%20target%3D%22_blank%22%3E%40Costas%20Koulermou%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-123068%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123068%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20checking%20to%20see%20if%20their%20is%20any%20change%20in%20this%20issue%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-88410%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-88410%22%20slang%3D%22en-US%22%3EYes%20please%20MS.%20By%20Teams%20duplicating%20the%20files%20into%20sharepoint%20from%20ODFB%20we%20will%20run%20the%20risk%20of%20people%20using%20the%20wrong%20version%20of%20the%20file%20and%20needing%20to%20know%20which%20file%20is%20the%20latest.%3CBR%20%2F%3EI%20really%20like%20Teams%20so%20far%2C%20but%20this%20file%20duplication%20(and%20not%20syncing)%20really%20worries%20me.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37258%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37258%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20i%20was%20hoping%20it%20would%20work%20like%20that.%3C%2FP%3E%3CP%3ESince%20i%20am%20sharing%20somehting%20from%20our%20common%20ODFB%20in%20a%20group%20of%20our%20company%20it%20would%20be%20amazing%20to%20be%20able%20to%20update%20the%20already%20shared%20file.%20No%20need%20to%20reshare%20if%20changes%20made.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20MS%20will%20see%20this%20and%20give%20us%20an%20option%20in%20the%20near%20future!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37222%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37222%22%20slang%3D%22en-US%22%3E%3CP%3EI%20went%20and%20double%20checked%20this%20myself%2C%20and%20am%20now%20curious%20why%20this%20is%20working%20this%20way.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20share%20a%20file%20from%20my%20OneDrive%20for%20Business%20within%20Teams%2C%20what%20is%20happening%20is%20the%20file%20is%20being%20copied%20to%20the%20Teams%20file%20storage%20(which%20is%20technically%20the%20Office%20365%20Group's%20file%20storage%2C%20in%20SharePoint).%20This%20results%20in%20two%20copies%20of%20the%20file%20now%20existing%20that%20are%20not%20linked%20or%20syncing%20in%20any%20way.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20what%20I%20would%20have%20expected%20to%20happen%20is%20that%20when%20I%20shared%20the%20file%20from%20my%20OneDrive%20for%20Business%20within%20Teams%2C%20it%20would%20have%20simply%20granted%20permissions%20on%20the%20file%20to%20the%20underlying%20Office%20365%20Group%20(and%20prompted%20me%20whether%20I%20wanted%20to%20grant%20view%20or%20edit%20permissions).%20This%20way%20if%20I%20make%20updates%20on%20the%20file%20in%20my%20OneDrive%20for%20Business%2C%20or%20if%20others%20make%20updates%20to%20the%20file%20in%20Teams%2C%20everyone%20is%20still%20on%20the%20same%20version%20and%20I'm%20still%20potentially%20syncing%20down%20that%20latest%20version%20via%20the%20OneDrive%20for%20Business%20sync%20client%20to%20my%20local%20machine%20for%20offline%20usage.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20guessing%20the%20reasoning%20this%20works%20the%20way%20it%20does%20currently%20is%20to%20try%20to%20move%20%22ownership%22%20of%20the%20file%20from%20an%20individual%20to%20the%20team%2C%20but%20not%20prompting%20for%20and%20resulting%20in%20a%20'Move'%20action%20is%20going%20to%20generate%20confusion%20for%20users%20and%20potential%20version%20conflicts%20down%20the%20road.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37186%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37186%22%20slang%3D%22en-US%22%3E%3CP%3EAh%20i%20see!%20So%20once%20a%20file%20is%20shared%20via%20Teams%20Ui%20that%20is%20a%20copy%20of%20the%20original.%20It%20will%20not%20get%20any%20updates.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20is%20what%20i%20needed%20to%20know.%20Thank%20you%20very%20much%20Juan!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37185%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37185%22%20slang%3D%22en-US%22%3EQuite%20simple%3A%3CBR%20%2F%3E-%20If%20you%20are%20sharing%20files%20from%20ODFB%20and%20you%20update%20those%20files%2C%20the%20user%20you%20are%20sharing%20with%20will%20se%20the%20file%20is%20updated%20by%20means%20of%20the%20Shared%20view%20in%20ODFB.%3CBR%20%2F%3E-%20If%20you%20are%20sharing%20files%20from%20Teams%2C%20there%20is%20no%20way%20to%20see%20if%20the%20files%20have%20been%20updates%20from%20the%20team%20UI%2C%20you%20have%20to%20go%20to%20the%20underlying%20Group%20and%20the%20SPO%20site%20to%20see%20this%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37162%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37162%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20our%20OneDrive%20Bussines.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20difference%20if%20i%20may%20ask%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-37096%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-37096%22%20slang%3D%22en-US%22%3EWhere%20are%20you%20storing%20the%20file%20you%20have%20shared%3A%20in%20OneDrive%20or%20in%20Teams%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-558809%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-558809%22%20slang%3D%22en-US%22%3E%3CP%3EA%20message%20from%20Microsoft%20actually%20went%20out%20this%20morning%20that%20says%20they%20are%20rolling%20out%20new%20sharing%20features%20in%20Microsoft%20Teams%20starting%20in%20late%20May%20and%20completing%20by%20the%20end%20of%20June.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBasically%2C%20it%20sounds%20like%20they%20are%20going%20to%20setup%20sharing%20in%20Teams%20to%20match%20the%20sharing%20functionality%20already%20in%20SharePoint%20and%20OneDrive.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20a%20link%20to%20the%20feature%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bfilters%3D%26amp%3Bsearchterms%3D51230%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bfilters%3D%26amp%3Bsearchterms%3D51230%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-559151%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-559151%22%20slang%3D%22en-US%22%3E%3CP%3EI%26nbsp%3Bhope%26nbsp%3Bthis%26nbsp%3Bactually%26nbsp%3Bfixes%20the%20issues%20of%20file%20updating%20from%20OneDrive%2C%20not%20just%20an%20easier%20way%20to%20navigate%20the%20waters%20of%20file%20sharing%20to%20Teams.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62361%22%20target%3D%22_blank%22%3E%40Kevin%20McKeown%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-830759%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-830759%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F340107%22%20target%3D%22_blank%22%3E%40tad-anderson_0956%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStill%20looking%20for%20a%20solution%20to%20this.%20I%20have%20the%20original%20files%20that%20I%20own%20and%20use%20all%20the%20time%20in%20ODFB%2C%20share%20these%20in%20Teams%20but%20always%20update%20the%20original%20files%20in%20ODFB.%20Since%20the%20point%20of%20sharing%20files%20in%20Teams%20is%20to%20eliminate%20multiple%20files%2C%20reduce%20space%20and%20give%20easy%20access%20-%20this%20seems%20counterintuitive%20to%20me.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-831059%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-831059%22%20slang%3D%22en-US%22%3E%3CP%3EOneDrive%20stemmed%20from%20what%20used%20to%20be%20called%20My%20Sites%20in%20SharePoint%2C%20and%20technically%20your%20OneDrive%20is%20your%20own%20personal%20SharePoint%20site.%20With%20this%20in%20mind%2C%20my%20opinion%20of%20OneDrive%20is%20that%20you%20should%20do%20very%20little%20sharing%20from%20OneDrive.%20It%20should%20be%20used%20as%20your%20personal%20storage%2C%20for%20files%20that%20only%20you%20need%20access%20to%2C%20or%20first%20draft%20versions%20of%20documents%20that%20aren't%20ready%20to%20be%20shared.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%2C%20any%20files%20that%20do%20need%20shared%20and%20collaborated%20on%20should%20be%20uploaded%20to%20Teams%20or%20a%20SharePoint%20site.%20The%20file%20in%20Teams%2FSharePoint%20then%20becomes%20the%20working%20document%20and%20any%20modifications%20to%20that%20document%20should%20be%20made%20within%20Teams%2FSharePoint.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20rarely%20a%20good%20situation%20to%20have%20the%20actual%20source%20of%20a%20shared%20document%20be%20your%20own%20OneDrive.%20If%20you%20ever%20leave%20the%20company%2C%20your%20OneDrive%20goes%20away.%20Shared%20documents%20should%20be%20placed%20into%20relevant%20Teams%2FSharePoint%20libraries%20in%20most%20situations.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-831310%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-831310%22%20slang%3D%22en-US%22%3EI%20own%20the%20files%2C%20and%20don%E2%80%99t%20want%20them%20on%20SharePoint%20where%20the%20are%20available%20for%20everyone.%20They%20are%20my%20personal%20consulting%20files%2C%20and%20I%20share%20for%20the%20projects%20with%20which%20I%20am%20involved.%20Don%E2%80%99t%20want%20the%20original%20files%20in%20Teams%20as%20Teams%20are%20project%20groups%20which%20only%20last%20for%20a%20short%20time.%20Then%20I%20have%20to%20constantly%20move%20them%20from%20Team%20to%20Team%20or%20to%20cloud%20storage.%20I%20suppose%20I%20could%20create%20my%20own%20private%20team%20in%20Teams%20and%20share%20from%20there%20and%20see%20if%20they%20create%20copies%20of%20of%20the%20file%20or%20shares%20the%20original%20file.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-831346%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-831346%22%20slang%3D%22en-US%22%3EThat%20is%20exactly%20my%20issue%20though.%20The%20whole%20point%20of%20TEAMS%20is%20to%20improve%20communication.%20I%20want%20my%20team%20to%20have%20access%20to%20files%20that%20they%20both%20can%20edit%20AND%20view%20only.%20OneDrive%20allows%20that%2C%20why%20not%20just%20create%20that%20workflow%20access%20in%20TEAMS%20so%20that%20your%20team%20members%20have%20a%20one%20stop%20shop%20for%20direct%20communication%2C%20team%20communication%20and%20any%20files%20that%20can%20be%20both%20edited%20or%20just%20viewed%20depending%20on%20how%20the%20owner%20sets%20the%20privileges.%20This%20seems%20like%20a%20very%20simple%20concept%20and%20if%20you%20have%20a%20platform%20to%20share%20files%20(and%20determine%20privileges)%20why%20not%20take%20advantage%20of%20that%20workflow%20so%20you%20can%20run%20a%20more%20efficient%20team%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-831725%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20files%20via%20OneDrive%20not%20updating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-831725%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F127680%22%20target%3D%22_blank%22%3E%40Ted%3C%2FA%3E-anderson_0956%3CBR%20%2F%3E%3CBR%20%2F%3EGlad%20someone%20understands%20what%20I%20am%20trying%20to%20accomplish%20and%20the%20challenge%20with%20the%20way%20things%20currently%20are.%3C%2FLINGO-BODY%3E
Highlighted
Costas Koulermou
Occasional Contributor

Hello all ,

 

Well we are giving MS teams a go and trying a few things that we would like to use.

One feature we like is the File sharing in the teams.

 

What i noticed is that when i share a file from our OneDrive , once i make some changes to it no one in the team Chat sees the changes. 

 

Is this normal or am i missing something?

 

Thank you

16 Replies
Where are you storing the file you have shared: in OneDrive or in Teams?

On our OneDrive Bussines.

 

What is the difference if i may ask? 

Solution
Quite simple:
- If you are sharing files from ODFB and you update those files, the user you are sharing with will se the file is updated by means of the Shared view in ODFB.
- If you are sharing files from Teams, there is no way to see if the files have been updates from the team UI, you have to go to the underlying Group and the SPO site to see this

Ah i see! So once a file is shared via Teams Ui that is a copy of the original. It will not get any updates.

 

That is what i needed to know. Thank you very much Juan!

I went and double checked this myself, and am now curious why this is working this way.

 

When I share a file from my OneDrive for Business within Teams, what is happening is the file is being copied to the Teams file storage (which is technically the Office 365 Group's file storage, in SharePoint). This results in two copies of the file now existing that are not linked or syncing in any way.

 

I think what I would have expected to happen is that when I shared the file from my OneDrive for Business within Teams, it would have simply granted permissions on the file to the underlying Office 365 Group (and prompted me whether I wanted to grant view or edit permissions). This way if I make updates on the file in my OneDrive for Business, or if others make updates to the file in Teams, everyone is still on the same version and I'm still potentially syncing down that latest version via the OneDrive for Business sync client to my local machine for offline usage.

 

I'm guessing the reasoning this works the way it does currently is to try to move "ownership" of the file from an individual to the team, but not prompting for and resulting in a 'Move' action is going to generate confusion for users and potential version conflicts down the road.

Yes i was hoping it would work like that.

Since i am sharing somehting from our common ODFB in a group of our company it would be amazing to be able to update the already shared file. No need to reshare if changes made.

 

I hope MS will see this and give us an option in the near future! 

 

 

Yes please MS. By Teams duplicating the files into sharepoint from ODFB we will run the risk of people using the wrong version of the file and needing to know which file is the latest.
I really like Teams so far, but this file duplication (and not syncing) really worries me.

Hello,

 

Just checking to see if their is any change in this issue :)

This still has not been fixed...How does this not drive people crazy? Does anyone know of a way to contact Microsoft with this issue? @Costas Koulermou 

A message from Microsoft actually went out this morning that says they are rolling out new sharing features in Microsoft Teams starting in late May and completing by the end of June. 

 

Basically, it sounds like they are going to setup sharing in Teams to match the sharing functionality already in SharePoint and OneDrive.

 

Here is a link to the feature: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&filters=&searchterms=51230

I hope this actually fixes the issues of file updating from OneDrive, not just an easier way to navigate the waters of file sharing to Teams. @Kevin McKeown 

@tad-anderson_0956 

 

Still looking for a solution to this. I have the original files that I own and use all the time in ODFB, share these in Teams but always update the original files in ODFB. Since the point of sharing files in Teams is to eliminate multiple files, reduce space and give easy access - this seems counterintuitive to me. 

OneDrive stemmed from what used to be called My Sites in SharePoint, and technically your OneDrive is your own personal SharePoint site. With this in mind, my opinion of OneDrive is that you should do very little sharing from OneDrive. It should be used as your personal storage, for files that only you need access to, or first draft versions of documents that aren't ready to be shared. 

 

Then, any files that do need shared and collaborated on should be uploaded to Teams or a SharePoint site. The file in Teams/SharePoint then becomes the working document and any modifications to that document should be made within Teams/SharePoint. 

 

It is rarely a good situation to have the actual source of a shared document be your own OneDrive. If you ever leave the company, your OneDrive goes away. Shared documents should be placed into relevant Teams/SharePoint libraries in most situations. 

I own the files, and don’t want them on SharePoint where the are available for everyone. They are my personal consulting files, and I share for the projects with which I am involved. Don’t want the original files in Teams as Teams are project groups which only last for a short time. Then I have to constantly move them from Team to Team or to cloud storage. I suppose I could create my own private team in Teams and share from there and see if they create copies of of the file or shares the original file.
That is exactly my issue though. The whole point of TEAMS is to improve communication. I want my team to have access to files that they both can edit AND view only. OneDrive allows that, why not just create that workflow access in TEAMS so that your team members have a one stop shop for direct communication, team communication and any files that can be both edited or just viewed depending on how the owner sets the privileges. This seems like a very simple concept and if you have a platform to share files (and determine privileges) why not take advantage of that workflow so you can run a more efficient team?
@Ted-anderson_0956

Glad someone understands what I am trying to accomplish and the challenge with the way things currently are.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies