Home

SharePoint Document Library Integration

%3CLINGO-SUB%20id%3D%22lingo-sub-27046%22%20slang%3D%22en-US%22%3ESharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27046%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%2C%20I%20want%20to%20say%20Amazing%20Job%20on%20the%20release%20of%20Microsoft%20Teams!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20just%20had%20our%20go-live%20for%20O365%20this%20week%20after%20migrating%20from%20Google%20Apps.%26nbsp%3B%20I%20have%20been%20frantically%20looking%20for%20something%20to%20fill%20a%20gap%20that%20we%20have%20stumbled%20across%20that%20we%20were%20using%20on%20GApps%20that%20doesn't%20exist%20in%20O365.%26nbsp%3B%20Then%20along%20comes%20Teams%20and%20has%20promise%20to%20give%20us%20much%20more%20than%20plugging%20the%20gap%20that%20I%20have%20that%20is%20frustrating%20our%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Chat%20Bot%20told%20me%20that%20SharePoint%20Document%20Libraries%20(although%20you%20can%20add%20it%20as%20a%20tab%20in%20Teams)%20isn't%20quite%20ready.%26nbsp%3B%20(BTW%2C%20I%20love%20it%20when%20a%20Chat%20Bot%20actually%20answers%20the%20question%20that%20I%20ask%20it!!!!)%26nbsp%3B%20Having%20the%20abiltiy%20to%20link%20a%20document%20library%20from%20SharePoint%20into%20Teams%20will%20plug%20the%20missing%20feature%20that%20we%20relied%20on%20in%20Google%20Apps.%26nbsp%3B%20Do%20you%20have%20an%20ETA%20when%20this%20integration%20will%20be%20ready%3F%26nbsp%3B%20I%20would%20be%20very%20much%20willing%20to%20test%20this%20out%20with%20my%20user%20base.%26nbsp%3B%20This%20would%2C%20IMO%2C%20be%20a%20game%20changer%20on%20user%20acceptance%20of%20our%20O365%20rollout.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-27046%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280494%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280494%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20believe%20I%20have%20a%20similar%20issue%20and%20would%20greatly%20appreciate%20your%20assistance.%20This%20is%20with%20a%20team%20that%20was%20created%20from%20an%20existing%20office%20365%20group.%20When%20I%20go%20to%20the%20files%20tab%20in%20the%20team%20channel%20I%20get%20the%20%22These%20files%20are%20no%20longer%20available%2C%20Check%20to%20see%20if%20the%20site%20is%20available%20and%20try%20again%22%20with%20a%20show%20details%20link.%20The%20site%20does%20exist%20and%20I%20can%20add%20it%20as%20a%20tab%20but%20the%20binding%20for%20the%20channels%20and%20files%20just%20doesn't%20work.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-271098%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-271098%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBumping%20over%20here%20because%20I'm%20also%20facing%20this%20issue.%20Teams%20V.%26nbsp%3B%3CSPAN%3E1.1.00.25457%20(64%20bits)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%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-131390%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-131390%22%20slang%3D%22en-US%22%3EMy%20version%20is%3A%20%3CBR%20%2F%3EYou%20have%20Microsoft%20Teams%20Version%201.0.00.30452%20(64-bit).%20It%20was%20last%20updated%20on%2011%2F10%2F17.%20%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-131389%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-131389%22%20slang%3D%22en-US%22%3EWe%20have%20Office%20365%20deploy%20for%20company%2C%20%3CBR%20%2F%3EI%20have%20a%20group%2Fchannel%20chatting%20in%20Teams.%20%3CBR%20%2F%3EXXX_YYY%20with%20channel%20General%20%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20a%20Sharepoint%20site%20auto-created%20by%20Teams%20in%20Sharepoint.%20%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fmycompany.com%2Fsites%2FXXX_YYY%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmycompany.com%2Fsites%2FXXX_YYY%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20when%20I%20link%20Sharepoint%20site%20to%20Teams%20tab%2C%20Teams%20say%20%22We%20couldn't%20find%20any%20SharePoint%20site%20or%20a%20folder.%20Check%20the%20link%20and%20try%20again%22%3CBR%20%2F%3EWhat%20did%20I%20do%20wrong%3F%20How%20can%20I%20fix%20it%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-106291%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-106291%22%20slang%3D%22en-US%22%3E%3CP%3EI%20also%20have%20the%20same%20issue%20in%20my%20organization.%20We%20have%20an%20existing%20SharePoint%20library%20which%20was%20really%20hard%20and%20painful%20process%20to%20establish%20to%20be%20used%20as%20storage%20and%20to%20be%20organized.%20Now%20I%20am%20thinking%20of%20proposing%20teams%20as%20working%20and%20collaboration%20tool%20but%20this%20means%20either%20migration%20to%20the%20new%20concept%20of%20document%20storage%2C%20which%20will%20be%20confusing%20for%20the%20users%20and%20really%20painful%20or%20not%20using%20is%20at%20all%20and%20keep%20the%20link%20to%20the%20old%20library%20but%20it%20will%20be%20a%20mess%2C%20as%20users%20will%20soon%20start%20to%20exchange%20files%20and%20they%20will%20be%20stored%20in%20the%20new%20one%20and%20they%20will%20get%20lost.%3C%2FP%3E%3CP%3ESo%20really%20as%20it%20is%20now%20I%20don't%20see%20a%20way%26nbsp%3Buse%20it%20in%20our%20organization.%20%3A(%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-79042%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-79042%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20there%20any%20remaining%20known%20issues%20with%26nbsp%3Blinkage%20to%20SharePoint%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20in%20a%20hybrid%20situation%20-%20most%20of%20our%20SharePoint%20is%20at%20O365.%20%26nbsp%3BWe%20do%20have%20a%20few%20sites%20on-prem.%20%26nbsp%3BI%20am%20unable%20to%20link%20to%20these%20on-prem%20sites.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CSPAN%3EWe%20couldn't%20find%20any%20SharePoint%20site%20or%20a%20folder.%20Check%20the%20link%20and%20try%20again.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIs%20this%20supported%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-78475%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-78475%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20update%20on%20the%20issue%20with%20using%20doc%20libraries%20from%20the%20root%3F%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-78004%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-78004%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20Team%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20happy%20that%20all%20the%20features%20are%20intigrated%20at%20one%20place...!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EReg%3A%20Sharepoint%20document%20library%20in%20Microsoft%20Teams%20-%20Will%20the%20customiused%20view%20of%20documents%20library%20can%20be%20dispayed%20as%20it%20is%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77815%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77815%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Kyle!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewhen%20adding%20sharepoint%20tab%20to%20teams%20channel%2C%20Is%20there%20any%20way%20to%20select%20specific%20path%20from%20documents%20instead%20of%20the%20whole%20document%20tree%3F%20That%20would%20be%20great!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20proposal%20is%20to%20keep%20every%20project%20document%20in%20the%20sharepoint%20site%20instead%20of%20the%20teams%20file%20tab%20in%20order%20to%20keep%20it%20all%20together.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance!%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-74413%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-74413%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20having%20the%20same%20issue%20when%20using%20Teams.%20I%20create%20a%20Team%2C%20then%20click%20the%20Files%20tab%20and%20encounter%20the%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20been%20told%20%22wait%2024%20hours%22%20on%20a%20similar%20issue%20-%20with%20the%20idea%20being%20that%20%22behind%20the%20scenes%2C%20Microsoft%20is%20provisioning%20the%20storage%22%20and%20it%20can%20take%20up%20to%2024%20hours%20for%20that%20process%20to%20run.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%231%3A%20the%20error%20message%20should%20be%20more%20descriptive%3C%2FP%3E%3CP%3E%232%3A%20this%20error%20never%20should%20happen%20in%20the%20first%20place%20-%20come%20up%20with%20another%20way%20to%20provision%20file%20space%20if%20this%20is%20really%20what's%20happening.%20Nothing%20like%20having%20work%20interrupted.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61645%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61645%22%20slang%3D%22en-US%22%3EHello%20all%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20just%20spoke%20to%20a%20SharePoint%20technician.%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20seems%20that%20this%20message%20%22We%20can't%20get%20your%20files.%20We're%20working%20on%20getting%20them%20back.%22%20appears%20when%20adding%20a%20document%20library%20from%20the%20root%20SharePoint-site%3A%3CBR%20%2F%3E(%3CA%20href%3D%22https%3A%2F%2Fcontoso.sharepoint.com%2Fdocumentlibrary%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcontoso.sharepoint.com%2Fdocumentlibrary%3C%2FA%3E).%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20adding%20a%20document%20library%20from%20a%20different%20site%20collection%20it%20actually%20works!%3CBR%20%2F%3E(i.e.%20%3CA%20href%3D%22https%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2Fitdepartment%2Fdocumentlibrary%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2Fitdepartment%2Fdocumentlibrary%3C%2FA%3E)%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20case%20is%20now%20being%20sorted%20by%20the%20Skype%20for%20Business%20Team.%20I%20will%20keep%20you%20posted.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-60753%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-60753%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F44333%22%20target%3D%22_blank%22%3E%40Greg%20Matthews%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20have%20the%20same%20error%3A%3C%2FP%3E%3CDIV%20class%3D%22drag-cta%22%3EThese%20files%20are%20no%20longer%20available%3C%2FDIV%3E%3CDIV%20class%3D%22drag-cta-subtext%22%3ECheck%20to%20see%20if%20site%20is%20available%20and%20try%20again%3C%2FDIV%3E%3CDIV%20class%3D%22error-details%22%3E%3CDIV%3EFile%20Not%20Found.%20Scenario%20ID%3A%2004CA7FA4B01340B0A2C2D6FE43325E5C%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3ELast%20week%20I%20created%20our%20first%20Team%2C%20and%20have%20a%20General%20and%203%20other%20channels.%20%26nbsp%3BIn%20one%20of%20the%20channels%20we%20uploaded%20some%20files%2C%20it%20was%20working%20fine%20for%20several%20days%2C%20but%20now%20when%20clicking%20on%20the%20Files%20tab%20in%20this%20particular%20channel%2C%20get%20the%20message%20above.%20%26nbsp%3BThe%20files%20are%20still%20available%20on%20the%20Sharepoint%20site%2C%20and%20in%20Team%20under%20Files%20-%20Microsoft%20Teams.%20%26nbsp%3BIt%20seems%20like%20the%20link%20is%20broken.%20%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EThe%20only%20change%20I%20can%20think%20that%20we%20did%20after%20uploading%20the%20files%20was%20to%20add%20the%20Sharepoint%20site%20to%20the%20General%20tabs%2C%20and%20added%20a%20Plan%20page%20to%20the%20failing%20channel.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EI%20posted%20this%20onto%20the%20feedback%20button%2C%20but%20no%20response.%20%26nbsp%3BI%20am%20hoping%20this%20is%20where%20to%20request%20assistance%20for%20this%20software.%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54042%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54042%22%20slang%3D%22en-US%22%3EI%20actually%20think%20I%20might%20know%20what%20it%20is.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20it%20'breaks'%20if%20you%20rename%20the%20'General'%20folder%20to%20something%20else.%3CBR%20%2F%3E%3CBR%20%2F%3EI've%20just%20renamed%20the%20top%20level%20folder%20via%20the%20SharePoint%20link%20back%20to%20'General'%20and%20now%20my%20Files%20tab%20works%20again.%3CBR%20%2F%3E%3CBR%20%2F%3EEveryone%20owes%20me%201%20beer.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54039%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54039%22%20slang%3D%22en-US%22%3EI've%20got%20this%20issue%20too%20if%20we%20can%20be%20of%20assistance%20to%20provide%20further%20clues.%3CBR%20%2F%3E%3CBR%20%2F%3EAm%20getting%20the%20message%20These%20files%20are%20no%20longer%20available%22%20when%20I%20click%20on%20the%20Files%20tab%20in%20a%20channel.%3CBR%20%2F%3E%3CBR%20%2F%3E%22File%20Not%20Found.%20Scenario%20ID%3A%2021CE93E2137C4E0D9ED6E2964B0949A7%22%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20only%20happens%20for%201%20of%20the%202%20channels%20I%20have%20--%20both%20have%20SharePoint%20integration%20added%20as%20a%20tab%20along%20the%20top.%3CBR%20%2F%3EFor%20the%20'broken'%20channel%2C%20I%20can%20still%20access%20files%20via%20the%20SharePoint%20tab%3CBR%20%2F%3EMS%20Teams%20version%201.0.00.6903%20(64-bit).%20It%20was%20last%20updated%20on%203%2F13%2F17.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53916%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53916%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20providing%20logs%20and%20assisting%20us%20with%20this%20issue.%20With%20your%20help%20we've%20narrowed%20down%20the%20possibilities%2C%20but%20need%20to%20make%20changes%20to%20our%20telemetry%20to%20find%20the%20root%20cause.%20The%20changes%20are%20already%20on%20the%20way%20-%20I'll%20provide%20another%20update%20based%20on%20the%20results.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20your%20patience!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKyle%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53577%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53577%22%20slang%3D%22en-US%22%3E%3CP%3Esame%20issue%20here.%20Can%20seem%20to%20add%20SP%20document%20library%20on%20MS%20Teams%20app.%20I'm%20on%20a%20mac%20by%20the%20way%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51917%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51917%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20already%20reached%20out%20to%20those%20of%20you%20with%20an%20exisiting%20issue%20via%26nbsp%3Bprivate%20message%20(here%20on%20tech%20community).%26nbsp%3B%20Please%20gather%20the%20requested%20infromation%20and%20send%20that%20info%20to%20me%20so%20we%20can%20investigate%20your%20issue(s).%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51870%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51870%22%20slang%3D%22en-US%22%3ETry%20to%20ask%20Rebecca%20Valdivia%20maybe%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51868%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51868%22%20slang%3D%22en-US%22%3Etry%20to%20ask%20Rebecca%20Valdivia%2C%20she%20was%20very%20helpful%20last%20time.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51866%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51866%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20in%20that%20case%20please%20try%20to%20ask%20somebody%20from%20MS%20Teams's%20support%20Team.%20I%20had%20before%20same%20issue%20but%20not%20anymore.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51855%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51855%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20in%20the%20US.%20We%20use%20Office%20365%20and%20have%20a%20main%20site%20for%20our%20company%20with%20many%20document%20libraries%20on%20that%20site.%20Here%20are%20some%20screen%20shots%20that%20I%20just%20took%20trying%20this%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51814%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51814%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20pretty%20strange%20because%20I%20have%20a%20same%20version%20and%20by%20me%20it's%20working%20now.%20It%20was%20not%20working%20but%20I%20tried%20it%20few%20weeks%20back%20and%20I%20was%20succesfull.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20which%20region%20you%20are%3F%20The%20reason%20of%20question%20is%20that%20I%20saw%20somewhere%20(maybe%20in%20this%20discussion)%20that%20some%20feature%20of%20MS%20Teams%20are%20released%20in%20some%20sequence%20by%20countries%2C%20regions%20or%20something%20like%20that.%20But%20now%20I'm%20not%20able%20to%20find%20this%20source%20of%20information.%20So%20I'm%20not%20100%20sure%20I'm%20right.%20Maybe%20you%20just%20need%20to%20wait%20little%20bit.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20460px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11671iD0A158E56E71C60E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22sharepoint.png%22%20title%3D%22sharepoint.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51354%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51354%22%20slang%3D%22en-US%22%3E%3CP%3EHallo%2C%20we%20have%26nbsp%3B%3CSPAN%3EMicrosoft%20Teams%20Version%201.0.00.6501%20(64-bit).%20The%20issue%20with%20the%20sharepoint%20tab%20described%20above%20is%20still%20present%2C%20no%20files%20are%20shown%20in%20that%20tab%2C%20with%20the%20message%20%22We%20can't%20get%20your%20files.%20We%20are%20working%20on%20getting%20them%20back%22.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIt%20would%20be%20nice%20if%20this%20would%20work.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50188%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50188%22%20slang%3D%22en-US%22%3E%3CP%3EGreg%2C%20you%20should%20be%20able%20to%20add%20libraries%20from%20sites%20with%20multiple.%20Sounds%20like%20this%20may%20be%20a%20bug.%20We%20just%20had%20a%20new%20update%20release%20this%20week%2C%20so%20please%20update%20your%20client%20or%20session%20first%20and%20try%20again.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'll%20have%20a%20support%20member%20from%20my%20team%20pre-emptively%20reach%20out%20in%20the%20case%20that%20doesn't%20work%20and%20we%20need%20to%20debug%20the%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50150%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50150%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20started%20using%20teams%20after%20having%20used%20Office365%20for%20a%20couple%20of%20years.%20In%20that%20implementation%20we%20have%20several%20sharepoint%20sites%20and%20existing%20document%20libraries%20that%20I'm%20tring%20to%20make%20visibile%20in%20Teams.%20In%20one%20instance%20I%20was%20able%20to%20use%20the%20'%2B'%20to%20add%20a%20sharepoint%20site%20by%20providing%20a%20sharepoint%20link%20to%20the%20existing%20library.%20That%20worked%20for%20one%20instance%20where%20there%20is%20only%20one%20document%20library%20on%20that%20site.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20to%20do%20the%20exact%20same%20thing%20to%20a%20site%20that%20has%20several%20document%20libraries%20on%20it.%20In%20that%20process%20I%20was%20prompted%20to%20select%20the%20specific%20document%20library%20I%20wanted%20to%20include%20on%20my%20Teams%20general%20channel%20and%20I%20received%20the%20message%20'We%20Can't%20get%20your%20files.%20We're%20working%20on%20getting%20them%20back.'%20Huh%3F%20What%20am%20I%20suppose%20to%20do%3F%20I%20don't%20really%20want%20to%20link%2Fsync%20the%20same%20documents%20into%20two%20document%20libraries.%20that%20seems%20pointless.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20thoughts%3F%20is%20this%20a%20known%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-48785%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-48785%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20sharing%20that%20Vincent.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20question%26nbsp%3Bremains%20though%20is%20(for%20the%20MS%20folks)%20-%20we%20have%20many%20teams%20which%20rely%20on%20existing%20processes%20which%20provision%20an%20internal%20SharePoint%20site%20-%20which%20is%20different%20than%20the%20%22internal%22%20SharePoint%20instance%20for%20the%20team%20created%20by%20Teams.%20The%20SharePoint%20connector%20should%20be%20able%20to%20surface%20the%20files%20from%20the%20existing%20SharePoint%20deployment%20as%20well.%20Is%20this%20something%20currently%20being%20looked%20into%2C%20and%20is%20there%20anything%20we%20can%20provide%20(logs%2C%20etc.)%20to%20help%20in%20that%20investigation%3F%20I%20can%20repro%20the%20problem%20with%20our%20instance%20as%20well%20(SharePoint%20on-prem%20document%20library).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45534%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45534%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%20create%20a%20support%20ticket%20and%20wanted%20to%20post%20the%20results%20here%20too.%20Apparently%2C%20you%20cannot%20just%20add%20a%20sharepoint%20site.%20Even%20though%20you%20select%20the%20actual%20document%20library%20you%20want%20to%20sync%20with%20the%20team%2C%20it%20will%20just%20not%20show%20up.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20did%20work%20was%20uploading%20a%20file%20into%20'Files'%20in%20Teams%20which%20would%20pop%20up%20in%20the%20sharepoint%20teamsite%20that%20was%20generated%20when%20creating%20the%20Team.%20From%20then%20on%2C%20all%20files%20that%20were%20added%20to%20that%20folder%20(called%20General)%20were%20being%20synced%20back%20and%20forth%20between%20SP%20and%20Teams.%20Not%20great%2C%20but%20at%20least%20it%20is%20something...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45516%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45516%22%20slang%3D%22en-US%22%3E%3CP%3EVincent%20sounds%20like%20a%20bug.%20I'll%20reach%20out%20directly%20for%20more%20details.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45307%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45307%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20is%20Sharepoint%20Integration%20not%20working%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20default%20sharepoint%20site%20for%20the%20Teams%20group%20I%20created%20inside%20MS%20Teams%20won't%20find%20documents%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22drag-cta%22%3E%3CEM%3EThese%20files%20are%20no%20longer%20available%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%20class%3D%22drag-cta-subtext%22%3E%3CEM%3ECheck%20to%20see%20if%20site%20is%20available%20and%20try%20again%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%20class%3D%22error-details%22%3E%3CDIV%3E%3CEM%3EList%20'Documents'%20does%20not%20exist%20at%20site%20with%20URL%20'%3CA%20href%3D%22https%3A%2F%2Fxxx.sharepoint.com%2Fsites%2FCore%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fxxx.sharepoint.com%2Fsites%2FCore%3C%2FA%3E'.%20Scenario%20ID%3A%20B5A0D121F24644A4BABF390C25E3F0D0%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EI%20can%20also%20add%20our%20regular%20SP%20site%2C%20but%20again%2C%20files%20are%20not%20coming%20in.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CDIV%20class%3D%22drag-cta%22%3E%3CEM%3EWe%20can't%20get%20your%20files%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%20class%3D%22drag-cta-subtext%22%3E%3CEM%3EWe're%20working%20on%20getting%20them%20back.%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%20class%3D%22drag-cta-subtext%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22drag-cta-subtext%22%3ETotally%20useless%20for%20us%20at%20this%20point%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-34005%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-34005%22%20slang%3D%22en-US%22%3E%3CP%3EIvan%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20have%20the%20current%20build%20(I%20revised%20my%20post%20as%20I%20referenced%20the%20Mac%20version).%26nbsp%3B%20I%20will%20reach%20out%20to%20you%20directly%20on%20your%20issue.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-33882%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-33882%22%20slang%3D%22en-US%22%3ELooks%20like%20my%20Teams%20app%20updated%20again%2C%20but%20I'm%20still%20a%20build%20number%20behind%20the%20one%20you've%20mentioned%2C%20so%20I'll%20have%20to%20wait%20to%20confirm%20this.%3CBR%20%2F%3EBuild%20%22You%20have%20Microsoft%20Teams%20Version%200.6.00.32301%20(64-bit).%20It%20was%20last%20updated%20on%2011%2F30%2F16.%22%20still%20has%20the%20same%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-33831%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-33831%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20sync%20documents%20from%20any%20SharePoint%20library%20(on-prem%20or%20Online)%20with%20Teams%20documents%2C%20also%20from%26nbsp%3Blocal%20file%20server%20department%20shares%20or%20user%20home%20drives%20via%203rd%20party%20tools%20like%20the%20Layer2%20Cloud%20Connector%20one-way%20or%20two-way%20with%20flexible%20options.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-33251%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-33251%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20update%20is%20pushed%20out%20over%20different%20rings%20-%20so%20may%20not%20have%20made%20it%20to%20your%20tenant%20yet.%26nbsp%3B%20Version%20%3CSPAN%3E0.6.00.31001%20is%20the%20prior%20version%20even%20though%20it%20says%20you%20were%20updated%20(a%20fix%20for%20displaying%20that%20you%20were%20updated%20when%20you%20havent%20been%20should%20be%20in%20the%20next%20update).%26nbsp%3B%20Some%20of%20the%20SP%20file%20issues%20in%20this%20thread%20have%20been%20resolved%20in%20builds%20after%200.6.00.32301%20(0.6.00.32302%20on%20Mac).%26nbsp%3B%20You%20may%20want%20to%20manually%20check%20for%20an%20update%20again%20periodically.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32680%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32680%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Rebecca%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20I%20can%20confirm%20a%20version%26nbsp%3B%3CSPAN%3E0.6.00.31001%20(64-bit).%20It%20was%20last%20updated%20on%2011%2F29%2F16.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAnother%20point%26nbsp%3BI%20really%20don't%20like%20is%20how%20the%20version%20is%20displayed.%20(UX)%20I%20was%20really%20expecting%2C%20that%20some%20kind%20of%20dialog%20will%20be%20displayed%2C%20when%20I%20click%20on%20%22About%20%22%20and%20after%20few%20try%20I%20founded%2C%20that%20the%20version%20is%20displayed%20on%20the%20top%20of%20window.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EOn%20the%20other%20hand%2C%20I%20really%20like%20MS%20Teams%20and%20idea%20behind%20it.%20It%20will%20need%20some%20improvement%20and%20bug%20fixing%20but%20it%20looks%20really%20promissing.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32662%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32662%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27864%22%20target%3D%22_blank%22%3E%40Rebecca%20Valdivia%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3ECan%20you%20confirm%20that%20you%20have%20the%20current%20client%20version%2C%200.6.00.32301%3F%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3ESame%20as%20the%20other%20replies%20above.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EYou%20have%20Microsoft%20Teams%20Version%200.6.00.31001%20(64-bit).%20It%20was%20last%20updated%20on%2029%2F11%2F2016.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20would%20have%20assumed%20to%20get%20the%20latest%20version%2C%20since%20I%20only%20started%20using%20the%20product%20yesterday%20and%20downloaded%20the%20setup%20fresh%20from%20teams.microsoft.com.%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EI've%20also%20manually%20checked%20for%20updates%20it%20says%20I'm%20on%20the%20latest%20build.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32656%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32656%22%20slang%3D%22en-US%22%3EMy%20guess%20is%20that%20users%20wil%20have%20to%20navigate%20to%20the%20actual%20SharePoint%20library%20and%20if%20you%20need%20to%20have%20this%20kind%20of%20customizations%20inside%20Teams%2C%20you%20will%20have%20to%20build%20it%20yourself%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32653%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32653%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20of%20all%2C%20Kyle%20-%20thanks%20for%20bringing%20in%20the%20SharePoint%20document%20library%20integration%20already%20in%20the%20beginning%20of%20the%20preview.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20someone%20who%20is%20accustomed%20to%20finetuning%20the%20inner%20workings%20of%20a%20SharePoint%20library%2C%20I've%20got%20one%20question%20though%3A%20Is%20the%20support%20for%20different%20views%20within%20SharePoint%20Document%20Libraries%20and%20%2F%20or%20document%20metadata%20on%20the%20roadmap%20to%20be%20added%20to%20the%20SharePoint%20tab%3F%20Or%20do%20the%20users%20have%20to%20navigate%20to%20the%20actual%20SharePoint%20library%20view%20even%20in%20the%20future%20to%20achieve%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32651%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32651%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here.%3C%2FP%3E%3CP%3ESettings%20%7C%20About%20shows%20%22%3CSPAN%3EYou%20have%20Microsoft%20Teams%20Version%200.6.00.31001%20(64-bit).%20It%20was%20last%20updated%20on%2011%2F30%2F16.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32645%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32645%22%20slang%3D%22en-US%22%3E%3CP%3EWhere%20is%20the%20build%20you%20mentioned%3F%3C%2FP%3E%3CP%3EI%20have%20run%20updates%20and%20reinstalled%20only%20to%20be%20at%20Microsoft%20Teams%20Version%200.6.00.31001%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32556%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32556%22%20slang%3D%22en-US%22%3E%3CP%3EAlan%2C%20this%20issue%20(adding%20non%20default%20library)%26nbsp%3Bhas%20been%20fixed%20in%20the%20current%20build%200.6.00.32301.%20If%20you%20are%20still%20experiencing%20after%20updating%20to%20this%20build%20this%20please%20let%20us%20know.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32555%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32555%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20confirm%20that%20you%20have%20the%20current%20client%20version%2C%200.6.00.32301%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32450%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32450%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20issue%20with%26nbsp%3B...%2Fworkgroups%2FXYZ%2FShared%2520Documents%2F...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32435%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32435%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I've%20started%20using%20Teams%20and%20wanted%20to%26nbsp%3Badd%20my%20default%20root%20document%20library%2C%20but%20I%20get%20the%20message%20%22These%20files%20are%20no%20longer%20available.%26nbsp%3BCheck%20to%20see%20if%20site%20is%20available%20and%20try%20again%22.%3C%2FP%3E%3CP%3EI've%20went%20through%20the%20add%20tab%20wizard%20%26gt%3B%20sharepoint%20%26gt%3B%20it%20even%20suggested%20my%20connected%20Office%20365%20Groups%20site%20%26gt%3B%20I%20select%20the%20Library%20%26gt%3B%20give%20it%20name%20%26gt%3B%20click%20save%20and%20done.%20Except%2C%20no%20files%20but%20the%20message%20above.%3C%2FP%3E%3CP%3EThe%20Group%20uses%20the%20%22German%22%20locale%2C%20so%20the%20URL%20is%20something%20like%20%3CA%20href%3D%22https%3A%2F%2Ftenantname.sharepoint.com%2Fsites%2Fo365groupname%2FFreigegebene%2520Dokumente%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftenantname.sharepoint.com%2Fsites%2Fo365groupname%2FFreigegebene%2520Dokumente%2F%3C%2FA%3E%20(I%20still%20don't%20get%20why%20Microsoft%20insists%20on%20changing%20default%20library%20names%20to%20german%2C%20instead%20of%20leaving%20them%20in%20english...)%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29504%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29504%22%20slang%3D%22en-US%22%3E%3CP%3EAbsolutely.%20I%20would%20like%20to%20be%20able%20to%20have%20a%20custom%20document%20library%20available%20in%20a%20channel%20in%20the%20event%20the%20collaboration%20is%20specific%20to%20content%20of%20a%20particular%20existing%20library.%20Seems%20it%20list%20the%20custom%20documetn%20library%20and%20adds%20without%20error%20but%20then%20its%20actually%20adding%20the%20default%20shared%20documents%20library.%20A%20true%20but%20that%20I'd%20like%20to%20see%20corrected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-28534%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-28534%22%20slang%3D%22en-US%22%3E%3CP%3EFWIW%2C%20I%20too%20am%20having%20problems%20with%20SharePoint%20in%20Teams.%20The%20error%20I%20receive%20is%2C%20%22The%20Files%20are%20no%20longer%20available%22.%20I've%20seen%20elsewhere%20this%20may%20be%20related%20to%20a%20bug%20with%20libraries%20that%20have%20spaces%20in%20the%20path%20name.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20test%20almost%20every%20day%20so%20am%20intersted%20in%20knowing%20when%20this%20gets%20fixed%20so%20i%20can%20roll%20out%20Teams%20to%20my%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-27914%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27914%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Kyle%2C%20If%20this%20bug%20is%20fixed%20and%20the%20option%20to%20choose%20the%20columns%20to%20display%20in%20the%20integration%20is%20added%2C%20I%20can%20see%20this%20being%20huge.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-27887%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27887%22%20slang%3D%22en-US%22%3E%3CP%3EBased%20on%20the%20descriptions%20a%20few%20of%20you%20have%20provided%20it%20sounds%20like%20there%20are%20likely%20several%26nbsp%3Bbugs%20involved.%20I'll%20have%20a%20support%20engineer%20from%20our%20team%20reach%20out%20to%20you%20individually%20to%20collect%20logs%20and%20other%20information%20to%20assist%20in%20our%20debugging.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20again%20for%20reporting%20the%20issues%2C%20and%20we%20greatly%20appreciate%20the%20assistance%20in%20identifying%20the%20root%20cause.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-27886%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27886%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlan%2C%20yes%2C%20not%20being%20able%20to%20add%20a%20non-default%20document%20library%20is%20one%20of%20the%20known%20issues.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-27743%22%20slang%3D%22en-US%22%3ERE%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27743%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27881%22%20target%3D%22_blank%22%3E%40Kyle%20Blevens%3C%2FA%3E%20Has%20anyone%20found%20a%20workaround%20or%20a%20reason%20why%20some%20SP%20libraries%20work%20with%20Teams%20and%20others%20don't%3F%20I%20have%20fired%20up%20Fiddler%20and%20looked%20at%20the%20calls%20to%20libraries%20that%20fail%20and%20libraries%20that%20work.%20The%20only%20thing%20that%20I%20can%20see%20is%20that%20on%20the%20ones%20that%20are%20failing%20there%20is%20no%20JSON%20returned%20from%20the%20API%20call%20to%20list%20the%20items%20in%20the%20library.%20The%20press%20on%20Teams%20has%20been%20crazy%20and%20I%20have%20about%2020%2B%20people%20asking%20daily%20when%20I%20am%20going%20to%20start%20rolling%20this%20out.%20If%20I%20cannot%20find%20a%20solution%2Fworkaround%20on%20this%20document%20library%20issue%20then%20I%20don't%20feel%20comfortable%20rolling%20this%20out%20to%20people.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-27666%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27666%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Kyle%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20one%20of%20those%20bugs%20the%20situation%20where%20you%20try%20to%20add%20a%20Documents%20library%20that%20isn't%20the%20default%20'Documents'%20one%20and%20it%20says%20that%20it%20works%20but%20it%20adds%20a%20bugged%20copy%20of%20the%20'Documents'%20library%20instead%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3CBR%20%2F%3EAlan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-27653%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27653%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Kyle%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20to%20add%20(pressing%20%22%2B%22%20in%20tab)%20Sharpoint%20site%20to%20channel%20both%20in%20Teams%20web%20and%20desktop%20apps.%20Both%20give%20me%20the%20same%20problem.%20If%20I%20select%20one%20from%20%22Relevant%20sites%22%20and%20click%20%22Next%22%2C%20there's%20no%20further%20response.%20If%20I%20enter%20the%20URL%20from%20%22Use%20a%20Sharepoint%20link%22%2C%20I%20get%20an%20error%20message%20saying%20%22We%20couldn't%20find%20any%20Sharepoint%20site%20or%20a%20folder.%20Check%20the%20link%20and%20try%20again.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETeams%20desktop%20version%3A%26nbsp%3B%3CSPAN%3E0.6.00.30201%20(64-bit)%3B%20last%20updated%20on%2011%2F3%2F16.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-27294%22%20slang%3D%22en-US%22%3ERE%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27294%22%20slang%3D%22en-US%22%3EHello%20Kyle.%20Thank%20you%20for%20getting%20back%20to%20me.%20I%20do%20believe%20that%20I%20am%20encountering%20a%20bug.%20I%20did%20additional%20testing%20today%20and%20here%20is%20what%20I%20have%20found.%20Some%20sites%20do%20indeed%20work%20and%20if%20I%20add%20a%20tab%20to%20a%20SharePoint%20library%20it%20does%20display%20properly.%20Most%20subsites%20however%20come%20up%20with%20a%20%22View%20your%20SharePoint%20files%20here%22%20message%20instead.%20I%20did%20test%20the%20Upload%20button%20and%20it%20is%20properly%20linking%20to%20the%20SharePoint%20library%20because%20the%20file%20does%20get%20uploaded%20properly%20it's%20just%20not%20creating%20the%20proper%20view%20into%20the%20library.%20It%20doesn't%20seem%20to%20be%20related%20to%20the%20type%20of%20site%20either.%20I%20have%20Wiki%2C%20Team%2C%20and%20Publishing%20subsites%20and%20there%20is%20no%20pattern%20that%20I%20can%20see%20on%20which%20libraries%20work%20and%20which%20don't.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-27264%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27264%22%20slang%3D%22en-US%22%3EHello%20Mike%20-%20I'm%20the%20Program%20Manager%20for%20files%20in%20Microsoft%20Teams.%20Good%20news%20-%20the%20ability%20to%20view%20files%20from%20an%20external%20SharePoint%20document%20library%20is%20available!%20Go%20to%20any%20channel%20in%20your%20team%2C%20press%20the%20%2B%20to%20the%20right%20of%20the%20tabs%2C%20and%20select%20the%20%22SharePoint%22%20option.%20%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20had%20some%20bugs%20with%20the%20feature%20reported%20that%20we're%20investigating.%20Please%20let%20me%20know%20if%20you%20encounter%20any%20or%20have%20feedback.%20Also%2C%20I'll%20ensure%20T-Bot%20is%20updated%20with%20the%20correct%20response.%20Thank%20you%20for%20trying%20Microsoft%20Teams!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-27055%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Document%20Library%20Integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-27055%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%26nbsp%3Bhaving%20the%20ability%20to%20link%26nbsp%3BSharepoint%20document%20libraries%20to%20Microsoft%20Teams%20is%20exactly%20what%20I'm%20looking%20for%20and%20what%20is%20missing%20for%20my%20organisation%20in%20Slack.%20This%20would%20be%20very%20helpful!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Mike Valentine
New Contributor

First, I want to say Amazing Job on the release of Microsoft Teams!

 

We just had our go-live for O365 this week after migrating from Google Apps.  I have been frantically looking for something to fill a gap that we have stumbled across that we were using on GApps that doesn't exist in O365.  Then along comes Teams and has promise to give us much more than plugging the gap that I have that is frustrating our users.

 

The Chat Bot told me that SharePoint Document Libraries (although you can add it as a tab in Teams) isn't quite ready.  (BTW, I love it when a Chat Bot actually answers the question that I ask it!!!!)  Having the abiltiy to link a document library from SharePoint into Teams will plug the missing feature that we relied on in Google Apps.  Do you have an ETA when this integration will be ready?  I would be very much willing to test this out with my user base.  This would, IMO, be a game changer on user acceptance of our O365 rollout.

 

Thanks!

54 Replies

Yes, having the ability to link Sharepoint document libraries to Microsoft Teams is exactly what I'm looking for and what is missing for my organisation in Slack. This would be very helpful! 

Hello Mike - I'm the Program Manager for files in Microsoft Teams. Good news - the ability to view files from an external SharePoint document library is available! Go to any channel in your team, press the + to the right of the tabs, and select the "SharePoint" option.

We've had some bugs with the feature reported that we're investigating. Please let me know if you encounter any or have feedback. Also, I'll ensure T-Bot is updated with the correct response. Thank you for trying Microsoft Teams!
Hello Kyle. Thank you for getting back to me. I do believe that I am encountering a bug. I did additional testing today and here is what I have found. Some sites do indeed work and if I add a tab to a SharePoint library it does display properly. Most subsites however come up with a "View your SharePoint files here" message instead. I did test the Upload button and it is properly linking to the SharePoint library because the file does get uploaded properly it's just not creating the proper view into the library. It doesn't seem to be related to the type of site either. I have Wiki, Team, and Publishing subsites and there is no pattern that I can see on which libraries work and which don't.

Hi Kyle,

 

I tried to add (pressing "+" in tab) Sharpoint site to channel both in Teams web and desktop apps. Both give me the same problem. If I select one from "Relevant sites" and click "Next", there's no further response. If I enter the URL from "Use a Sharepoint link", I get an error message saying "We couldn't find any Sharepoint site or a folder. Check the link and try again."

 

Teams desktop version: 0.6.00.30201 (64-bit); last updated on 11/3/16.

Hi Kyle,

 

Is one of those bugs the situation where you try to add a Documents library that isn't the default 'Documents' one and it says that it works but it adds a bugged copy of the 'Documents' library instead?

 

Thanks,
Alan

@Kyle Blevens Has anyone found a workaround or a reason why some SP libraries work with Teams and others don't? I have fired up Fiddler and looked at the calls to libraries that fail and libraries that work. The only thing that I can see is that on the ones that are failing there is no JSON returned from the API call to list the items in the library. The press on Teams has been crazy and I have about 20+ people asking daily when I am going to start rolling this out. If I cannot find a solution/workaround on this document library issue then I don't feel comfortable rolling this out to people.

 

Alan, yes, not being able to add a non-default document library is one of the known issues.

Based on the descriptions a few of you have provided it sounds like there are likely several bugs involved. I'll have a support engineer from our team reach out to you individually to collect logs and other information to assist in our debugging.

 

Thank you again for reporting the issues, and we greatly appreciate the assistance in identifying the root cause.

Thanks Kyle, If this bug is fixed and the option to choose the columns to display in the integration is added, I can see this being huge.

FWIW, I too am having problems with SharePoint in Teams. The error I receive is, "The Files are no longer available". I've seen elsewhere this may be related to a bug with libraries that have spaces in the path name.

 

I test almost every day so am intersted in knowing when this gets fixed so i can roll out Teams to my users.

 

Thanks

Absolutely. I would like to be able to have a custom document library available in a channel in the event the collaboration is specific to content of a particular existing library. Seems it list the custom documetn library and adds without error but then its actually adding the default shared documents library. A true but that I'd like to see corrected.

 

Hi, I've started using Teams and wanted to add my default root document library, but I get the message "These files are no longer available. Check to see if site is available and try again".

I've went through the add tab wizard > sharepoint > it even suggested my connected Office 365 Groups site > I select the Library > give it name > click save and done. Except, no files but the message above.

The Group uses the "German" locale, so the URL is something like https://tenantname.sharepoint.com/sites/o365groupname/Freigegebene%20Dokumente/ (I still don't get why Microsoft insists on changing default library names to german, instead of leaving them in english...) 

 

Any ideas?

 

I have the same issue with .../workgroups/XYZ/Shared%20Documents/...

 

Can you confirm that you have the current client version, 0.6.00.32301?

Alan, this issue (adding non default library) has been fixed in the current build 0.6.00.32301. If you are still experiencing after updating to this build this please let us know.

Where is the build you mentioned?

I have run updates and reinstalled only to be at Microsoft Teams Version 0.6.00.31001

Same here.

Settings | About shows "You have Microsoft Teams Version 0.6.00.31001 (64-bit). It was last updated on 11/30/16."

First of all, Kyle - thanks for bringing in the SharePoint document library integration already in the beginning of the preview.

 

As someone who is accustomed to finetuning the inner workings of a SharePoint library, I've got one question though: Is the support for different views within SharePoint Document Libraries and / or document metadata on the roadmap to be added to the SharePoint tab? Or do the users have to navigate to the actual SharePoint library view even in the future to achieve this?

My guess is that users wil have to navigate to the actual SharePoint library and if you need to have this kind of customizations inside Teams, you will have to build it yourself

@Rebecca Valdivia wrote:

Can you confirm that you have the current client version, 0.6.00.32301?


Same as the other replies above. 

You have Microsoft Teams Version 0.6.00.31001 (64-bit). It was last updated on 29/11/2016.

 

I would have assumed to get the latest version, since I only started using the product yesterday and downloaded the setup fresh from teams.microsoft.com. I've also manually checked for updates it says I'm on the latest build.

Hi Rebecca

 

Yes, I can confirm a version 0.6.00.31001 (64-bit). It was last updated on 11/29/16.

 

Another point I really don't like is how the version is displayed. (UX) I was really expecting, that some kind of dialog will be displayed, when I click on "About " and after few try I founded, that the version is displayed on the top of window.

 

On the other hand, I really like MS Teams and idea behind it. It will need some improvement and bug fixing but it looks really promissing. 

The update is pushed out over different rings - so may not have made it to your tenant yet.  Version 0.6.00.31001 is the prior version even though it says you were updated (a fix for displaying that you were updated when you havent been should be in the next update).  Some of the SP file issues in this thread have been resolved in builds after 0.6.00.32301 (0.6.00.32302 on Mac).  You may want to manually check for an update again periodically.

You can sync documents from any SharePoint library (on-prem or Online) with Teams documents, also from local file server department shares or user home drives via 3rd party tools like the Layer2 Cloud Connector one-way or two-way with flexible options. 

Looks like my Teams app updated again, but I'm still a build number behind the one you've mentioned, so I'll have to wait to confirm this.
Build "You have Microsoft Teams Version 0.6.00.32301 (64-bit). It was last updated on 11/30/16." still has the same issue.

Ivan,

 

You have the current build (I revised my post as I referenced the Mac version).  I will reach out to you directly on your issue.


Thank you.

Why is Sharepoint Integration not working?

 

The default sharepoint site for the Teams group I created inside MS Teams won't find documents:

 

These files are no longer available
Check to see if site is available and try again
List 'Documents' does not exist at site with URL 'https://xxx.sharepoint.com/sites/Core'. Scenario ID: B5A0D121F24644A4BABF390C25E3F0D0
 
I can also add our regular SP site, but again, files are not coming in.
 
We can't get your files
We're working on getting them back.
 
Totally useless for us at this point

Vincent sounds like a bug. I'll reach out directly for more details.

I did create a support ticket and wanted to post the results here too. Apparently, you cannot just add a sharepoint site. Even though you select the actual document library you want to sync with the team, it will just not show up.

 

What did work was uploading a file into 'Files' in Teams which would pop up in the sharepoint teamsite that was generated when creating the Team. From then on, all files that were added to that folder (called General) were being synced back and forth between SP and Teams. Not great, but at least it is something...

Thanks for sharing that Vincent.

 

The question remains though is (for the MS folks) - we have many teams which rely on existing processes which provision an internal SharePoint site - which is different than the "internal" SharePoint instance for the team created by Teams. The SharePoint connector should be able to surface the files from the existing SharePoint deployment as well. Is this something currently being looked into, and is there anything we can provide (logs, etc.) to help in that investigation? I can repro the problem with our instance as well (SharePoint on-prem document library). 

I just started using teams after having used Office365 for a couple of years. In that implementation we have several sharepoint sites and existing document libraries that I'm tring to make visibile in Teams. In one instance I was able to use the '+' to add a sharepoint site by providing a sharepoint link to the existing library. That worked for one instance where there is only one document library on that site.

 

I tried to do the exact same thing to a site that has several document libraries on it. In that process I was prompted to select the specific document library I wanted to include on my Teams general channel and I received the message 'We Can't get your files. We're working on getting them back.' Huh? What am I suppose to do? I don't really want to link/sync the same documents into two document libraries. that seems pointless. 

 

Any thoughts? is this a known issue?

Greg, you should be able to add libraries from sites with multiple. Sounds like this may be a bug. We just had a new update release this week, so please update your client or session first and try again.

 

I'll have a support member from my team pre-emptively reach out in the case that doesn't work and we need to debug the problem.

Hallo, we have Microsoft Teams Version 1.0.00.6501 (64-bit). The issue with the sharepoint tab described above is still present, no files are shown in that tab, with the message "We can't get your files. We are working on getting them back".

It would be nice if this would work.

That's pretty strange because I have a same version and by me it's working now. It was not working but I tried it few weeks back and I was succesfull. 

 

From which region you are? The reason of question is that I saw somewhere (maybe in this discussion) that some feature of MS Teams are released in some sequence by countries, regions or something like that. But now I'm not able to find this source of information. So I'm not 100 sure I'm right. Maybe you just need to wait little bit. 

 

 

sharepoint.png

I'm in the US. We use Office 365 and have a main site for our company with many document libraries on that site. Here are some screen shots that I just took trying this again.

So in that case please try to ask somebody from MS Teams's support Team. I had before same issue but not anymore. 

try to ask Rebecca Valdivia, she was very helpful last time.
Try to ask Rebecca Valdivia maybe

I have already reached out to those of you with an exisiting issue via private message (here on tech community).  Please gather the requested infromation and send that info to me so we can investigate your issue(s). Thanks!

same issue here. Can seem to add SP document library on MS Teams app. I'm on a mac by the way

Hi everyone,

 

Thank you for providing logs and assisting us with this issue. With your help we've narrowed down the possibilities, but need to make changes to our telemetry to find the root cause. The changes are already on the way - I'll provide another update based on the results.

 

Thank you for your patience!

 

Kyle

I've got this issue too if we can be of assistance to provide further clues.

Am getting the message These files are no longer available" when I click on the Files tab in a channel.

"File Not Found. Scenario ID: 21CE93E2137C4E0D9ED6E2964B0949A7"

It only happens for 1 of the 2 channels I have -- both have SharePoint integration added as a tab along the top.
For the 'broken' channel, I can still access files via the SharePoint tab
MS Teams version 1.0.00.6903 (64-bit). It was last updated on 3/13/17.
Highlighted
I actually think I might know what it is.

I think it 'breaks' if you rename the 'General' folder to something else.

I've just renamed the top level folder via the SharePoint link back to 'General' and now my Files tab works again.

Everyone owes me 1 beer.

@Greg Matthews

I have the same error:

These files are no longer available
Check to see if site is available and try again
File Not Found. Scenario ID: 04CA7FA4B01340B0A2C2D6FE43325E5C
 
Last week I created our first Team, and have a General and 3 other channels.  In one of the channels we uploaded some files, it was working fine for several days, but now when clicking on the Files tab in this particular channel, get the message above.  The files are still available on the Sharepoint site, and in Team under Files - Microsoft Teams.  It seems like the link is broken.  
 
The only change I can think that we did after uploading the files was to add the Sharepoint site to the General tabs, and added a Plan page to the failing channel.
 
I posted this onto the feedback button, but no response.  I am hoping this is where to request assistance for this software.
Hello all,

I just spoke to a SharePoint technician.

It seems that this message "We can't get your files. We're working on getting them back." appears when adding a document library from the root SharePoint-site:
(https://contoso.sharepoint.com/documentlibrary).

When adding a document library from a different site collection it actually works!
(i.e. https://contoso.sharepoint.com/sites/itdepartment/documentlibrary)

This case is now being sorted by the Skype for Business Team. I will keep you posted.

I'm having the same issue when using Teams. I create a Team, then click the Files tab and encounter the error.

 

I've been told "wait 24 hours" on a similar issue - with the idea being that "behind the scenes, Microsoft is provisioning the storage" and it can take up to 24 hours for that process to run.

 

#1: the error message should be more descriptive

#2: this error never should happen in the first place - come up with another way to provision file space if this is really what's happening. Nothing like having work interrupted.

Hi Kyle!

 

when adding sharepoint tab to teams channel, Is there any way to select specific path from documents instead of the whole document tree? That would be great!

 

Our proposal is to keep every project document in the sharepoint site instead of the teams file tab in order to keep it all together. 

 

Thanks in advance!

David

Dear Team,

 

I am happy that all the features are intigrated at one place...!

 

Reg: Sharepoint document library in Microsoft Teams - Will the customiused view of documents library can be dispayed as it is?

 

Thank you. 

Any update on the issue with using doc libraries from the root? Thanks.

Are there any remaining known issues with linkage to SharePoint?

 

We are in a hybrid situation - most of our SharePoint is at O365.  We do have a few sites on-prem.  I am unable to link to these on-prem sites.

 

"We couldn't find any SharePoint site or a folder. Check the link and try again."

 

Is this supported?

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
38 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies