We are setting up your file directory...someday

%3CLINGO-SUB%20id%3D%22lingo-sub-31212%22%20slang%3D%22en-US%22%3EWe%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-31212%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20number%20of%20teams%20I%20have%20setup%20as%20part%20of%20an%20internal%20test%20we%20are%20running.%20Some%20of%20the%20teams%20and%20some%20of%20the%20channels%20under%20the%20Teams%20continually%20say%20in%20the%20File%20and%20Notes%20tab%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22We%20are%20setting%20up%20your%20file%20directory.%20Try%20refreshing%20the%20page%20after%20a%20few%20minutes%20or%20check%20back%20later.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20keep%20things%20interesting%2C%20I%20have%20a%20set%20of%20teams%20and%20channels%20under%20them%20that%20do%20work%20properly%20and%20have%20fully%20functioning%20Files%20and%20Notes%20tabs.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20else%20seen%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-Rob%20Lavin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-31212%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-328164%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328164%22%20slang%3D%22en-US%22%3EThis%20is%20a%20powershell%20script%20you%20can%20run%20on%20any%20computer%20with%20powershell!%20You%20also%20first%20need%20to%20import%20and%20connect%20with%20the%20correct%20modules!%20I%20haven%E2%80%99t%20looked%20at%20the%20script%20but%20I%E2%80%99ll%20guess%20the%20exchange%20module%20for%20groups%20and%20maybe%20teams%20and%20sharepoint%20online%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328157%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328157%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Jason%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20still%20have%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20checking%20for%20app%20registration%2C%20i%20saw%20your%20post%20about%20special%20characters.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ea%20few%20more%20searches%20i%20stumbled%20across%20this%20post..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgallery.technet.microsoft.com%2FCheck-for-obsolete-Office-c0020a42%2Fview%2FDiscussions%23content%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgallery.technet.microsoft.com%2FCheck-for-obsolete-Office-c0020a42%2Fview%2FDiscussions%23content%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3Bthis%20is%20a%20report%20that%20can%20give%20admin%20a%20list%20of%20all%20sharepoint%20and%20shapoint%20%2F%20team%20sites.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Edoes%20anyone%20know%20if%20this%20is%20run%20from%20powershell%20on%20windows%20AD%20or%20somewhere%20else%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETHanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207632%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207632%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20are%20considered%20special%20characters%3F%26nbsp%3B%20I%20have%20a%20Team%20I%20just%20created%20that%20has%20a%20slash%20%22%2F%22%20in%20the%20name%20and%20I'm%20currently%20stuck%20on%20the%20files%20area.%26nbsp%3B%20I%20thought%20it%20might%20be%20the%20slash%20but%20I%20have%20other%20teams%20that%20have%20a%20slash%20in%20the%20name%20and%20they%20work%20just%20fine%20so%20not%20sure%20if%20that's%20the%20problem%20or%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20it%20is%2C%20can%20I%20simply%20rename%20the%20team%20or%20do%20I%20need%20to%20delete%20it%20and%20create%20a%20new%20one%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-188427%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-188427%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20extra%20tip!%20Makes%20perfect%20sense%2C%20so%20I'll%20keep%20it%26nbsp%3Bin%20mind.%20Overall%2C%26nbsp%3BI%20have%26nbsp%3Bbeen%20seeing%20less%20of%20this%20issue%20(sometimes%20when%20I'm%20doing%20training%20with%20someone%20it%20will%20pop%20up%20but%20it%20works%20itself%20out%20in%20a%20few%20minutes)%20Thanks%20again!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-187915%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-187915%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20having%20the%20same%20problem.%3C%2FP%3E%3CP%3EA%20team%20was%20created%20for%20the%20group%20I%20am%20in%20yesterday.%3C%2FP%3E%3CP%3EStill%20have%20the%20setting%20up%20message.%3C%2FP%3E%3CP%3EThe%20only%20special%20character%20we%20have%20in%20the%20name%20is%20a%20dash%20%22-%22.%3C%2FP%3E%3CP%3EWe%20are%20a%20multi%20university%20tenant.%3C%2FP%3E%3CP%3EEach%20university%20has%20its%20own%20abbreviation%20that%20is%20prefixed%20to%20names%20followed%20by%20the%20name%20we%20asked%20for%20(i.e.%20WSU-DataServices).%3C%2FP%3E%3CP%3EThere%20are%20other%20teams%20like%20this%20and%20they%20work%20just%20fine.%3C%2FP%3E%3CP%3EI%20have%20created%20a%20ticket%20with%20our%20system%20office%2C%20they%20administer%20the%20tenant%2C%20no%20response%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177808%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177808%22%20slang%3D%22en-US%22%3E%3CP%3EI%20saw%20this%20briefly%20when%20I%20joined%20a%20Team%20and%20after%20I%20added%20a%20channel%20to%20it.%26nbsp%3B%20It%20resolved%20itself%20in%20less%20than%205%20minutes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177805%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177805%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20sure%20if%20it's%20too%20late%2C%20but%20if%20anyone%20is%20still%20encountering%20this%20issue%2C%20it's%20usually%20caused%20by%20a%20special%20characters%20in%20your%20Teams%2FTeams%20channel%20name.%20This%20is%20also%20related%20to%20a%20OneDrive%20issue%20where%20files%20would%20not%20sync%20if%20they%20had%20special%20characters%20in%20the%20filename.%20Just%20remove%20the%20special%20characters%20and%20it%20should%20complete%20file%20directory%20setup%20in%202-3%20minutes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-127268%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-127268%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Alexander%2C%3C%2FP%3E%3CP%3EThe%20custom%20app%20for%20my%20issue%20was%20an%20MVC%20web%20app%20with%20the%20intent%20of%20consuming%20data%20from%20SharePoint%20Online.%20When%20I%20registered%20the%20application%20I%20entered%20the%20SharePoint%20Online%20Url%20as%20the%20Sign%20In%20Url.%26nbsp%3B%20To%20correct%20the%20issue%20I%20could%20have%20just%20updated%20the%20Sign-in%20Url%20with%20a%20new%20one%20but%26nbsp%3Bapplication%20was%20no%20longer%20in%20use%20and%20was%20more%20for%20testing%2C%20so%20I%20proceeded%20with%20deleting%20the%20application.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%2C%3C%2FP%3E%3CP%3EBobby%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125041%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125041%22%20slang%3D%22en-US%22%3E%3CP%3EI%20haven't%20seen%20anything%20new%20in%20regards%20to%20the%20issue%20Bobby%20had%2C%20but%20definitely%20check%20to%20see%20if%20his%20fix%20he%20outlined%20above%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-122145%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-122145%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37019%22%20target%3D%22_blank%22%3E%40Bobby%20Cruz%3C%2FA%3EJust%20found%20this%20post%2C%20thanks%20for%20sharing%20the%20information!%20We%20just%20started%20seeing%20this%20issue%20here%20and%20will%20check%20to%20see%20if%20this%20might%20work%20for%20us.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3328%22%20target%3D%22_blank%22%3E%40David%20Rosenthal%3C%2FA%3E%26nbsp%3Bsince%20this%20post%20are%20there%20any%20new%20MS%20updates%20on%20improving%20this%20experience%20when%20users%20create%20a%20new%20team%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-90741%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-90741%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ecould%20you%20please%20be%20a%20little%20more%20specific%20about%20the%20custom%20apps%20and%20their%20urls.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20two%20apps%20currently%20that%20have%20the%20url%20https%3A%2F%2F%3CTENANT%3E.sharepoint.com%2Fsites%2F%3CNOT%20a%3D%22%22%20group%3D%22%22%3E.%3C%2FNOT%3E%3C%2FTENANT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20I%20have%20to%20delete%20those%20even%20though%20they%20are%20legit%20and%20working%20apps%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65618%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65618%22%20slang%3D%22en-US%22%3EThat's%20great%20to%20hear%20Andy!%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%3CBR%20%2F%3E%3CBR%20%2F%3EBobby%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65615%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65615%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Bobby%20thats%20solved%20it%20for%20me%20too!%20Finally%20am%20able%20to%20use%20Teams%20properly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20so%20much.%20Hopefully%20it%20helps%20others%20too.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3CP%3EAndy%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65503%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65503%22%20slang%3D%22en-US%22%3EHi%20All%2C%20Just%20wanted%20to%20provide%20an%20update.%20So%20with%20the%20help%20of%20the%20Microsoft%20Support%20Engineers%20and%20Azure%20Engineers%20they%20were%20able%20to%20isolate%20the%20problem%20to%20a%20custom%20app%20I%20built%20that%20used%20my%20SharePoint%20Online%20address%20as%20the%20Sign-in%20Url.%20To%20eliminate%20the%20possibly%20of%20this%20being%20the%20same%20issue%20for%20all%20experiencing%20this%20problem%2C%20I%20would%20recommend%20checking%20any%20custom%20apps%20registered%20in%20Azure%20AD%20and%20verify%20they%20are%20not%20using%20your%20SharePoint%20Online%20address.%20I%20deleted%20the%20app%20in%20my%20case%20since%20it%20was%20not%20used%20by%20anyone%20and%20was%20more%20for%20testing.%20Once%20deleted%2C%20Microsoft%20Teams%20Files%20are%20now%20visible%20and%20all%20my%20Tabs%20new%20and%20old%20are%20working.%20I%20was%20also%20experiencing%20issues%20with%20the%20mobile%20apps%20for%20Delve%20and%20SharePoint%20Mobile%2C%20and%20they%20now%20working.%20Lastly%2C%20I%20also%20was%20unable%20to%20create%20a%20SharePoint%20Connection%20in%20Flow%20and%20now%20that%20is%20working%20as%20expected.%20I%20cannot%20say%20the%20resolution%20is%20the%20same%20for%20everyone%20but%20it%20is%20worth%20a%20check.%20Best%2C%20Bobby%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65502%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65502%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%20Just%20wanted%20to%20provide%20an%20update.%20So%20with%20the%20help%20of%20the%20Microsoft%20Support%20Engineers%20and%20Azure%20Engineers%20they%20were%20able%20to%20isolate%20the%20problem%20to%20a%20custom%20app%20I%20built%20that%20used%20my%20SharePoint%20Online%20address%20as%20the%20Sign-in%20Url.%20To%20eliminate%20the%20possibly%20of%20this%20being%20the%20same%20issue%20for%20all%20experiencing%20this%20problem%2C%20I%20would%20recommend%20checking%20any%20custom%20apps%20registered%20in%20Azure%20AD%20and%20verify%20they%20are%20not%20using%20your%20SharePoint%20Online%20address.%20I%20deleted%20the%20app%20in%20my%20case%20since%20it%20was%20not%20used%20by%20anyone%20and%20was%20more%20for%20testing.%20Once%20deleted%2C%20Microsoft%20Teams%20Files%20are%20now%20visible%20and%20all%20my%20Tabs%20new%20and%20old%20are%20working.%20I%20was%20also%20experiencing%20issues%20with%20the%20mobile%20apps%20for%20Delve%20and%20SharePoint%20Mobile%2C%20and%20they%20now%20working.%20Lastly%2C%20I%20also%20was%20unable%20to%20create%20a%20SharePoint%20Connection%20in%20Flow%20and%20now%20that%20is%20working%20as%20expected.%20I%20cannot%20say%20the%20resolution%20is%20the%20same%20for%20everyone%20but%20it%20is%20worth%20a%20check.%20Best%2C%20Bobby%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65501%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65501%22%20slang%3D%22en-US%22%3EHi%20All%2C%20Just%20wanted%20to%20provide%20an%20update.%20So%20with%20the%20help%20of%20the%20Microsoft%20Support%20Engineers%20and%20Azure%20Engineers%20they%20were%20able%20to%20isolate%20the%20problem%20to%20a%20custom%20app%20I%20built%20that%20used%20my%20SharePoint%20Online%20address%20as%20the%20Sign-in%20Url.%20To%20eliminate%20the%20possibly%20of%20this%20being%20the%20same%20issue%20for%20all%20experiencing%20this%20problem%2C%20I%20would%20recommend%20checking%20any%20custom%20apps%20registered%20in%20Azure%20AD%20and%20verify%20they%20are%20not%20using%20your%20SharePoint%20Online%20address.%20I%20deleted%20the%20app%20in%20my%20case%20since%20it%20was%20not%20used%20by%20anyone%20and%20was%20more%20for%20testing.%20Once%20deleted%2C%20Microsoft%20Teams%20Files%20are%20now%20visible%20and%20all%20my%20Tabs%20new%20and%20old%20are%20working.%20I%20was%20also%20experiencing%20issues%20with%20the%20mobile%20apps%20for%20Delve%20and%20SharePoint%20Mobile%2C%20and%20they%20now%20working.%20Lastly%2C%20I%20also%20was%20unable%20to%20create%20a%20SharePoint%20Connection%20in%20Flow%20and%20now%20that%20is%20working%20as%20expected.%20I%20cannot%20say%20the%20resolution%20is%20the%20same%20for%20everyone%20but%20it%20is%20worth%20a%20check.%20Best%2C%20Bobby%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61218%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61218%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20experiencing%20the%20same%20issue%20as%20described%20-%20Teams%20files%2Fwiki%20not%20setting%20up%20and%20Flow%20giving%20an%20OAuth2%20error%20when%20connecting%20to%20SharePoint.%20I'm%20using%20an%20MSDN%20tenant%20which%20i've%20had%20for%20a%20couple%20of%20years.%20I%20also%20have%20a%20support%20ticket%20with%20Microsoft%20so%20will%20post%20if%20I%20find%20out%20anything%20more..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61134%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61134%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20David%2C%3C%2FP%3E%3CP%3EAgreed%2C%20I%20can%20rule%20out%20networking%20and%20the%20only%20reason%20I%20am%20pointing%20to%20a%20configuration%20issue%20with%20my%20tenant%2C%20specifically%20Azure%20AD%2C%20is%20with%20the%20multiple%20AAD%20errors%20I%20see%20when%20using%20not%20only%20Teams%2C%20but%20with%20PowerApps%20and%20Flow.%20%26nbsp%3B%20Of%20course%2C%20I%20am%20cannot%20say%20with%20any%20certainty%20Azure%20AD%20is%20the%20issue.%20Hopefully%2C%20I%20will%20hear%20from%20Microsoft%20soon%20with%20a%20solution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EBobby%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61129%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61129%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20being%20able%20to%20get%20tokens%20is%20identity%20or%20network%20issues%2C%20and%20since%20all%20the%20rest%20of%20us%20are%20running%20fine%20it%20would%20have%20to%20be%20something%20with%20your%20configuration.%20Possible%2C%20but%20I%20would%20doubt%20it%20is%20something%20actually%20wrong%20with%20your%20tenant%20as%20I'm%20assuming%20support%20would%20have%20checked%20the%20health%20of%20your%20tenant%20fairly%20early%20in%20their%20process.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20been%20through%20this%20to%20make%20sure%20Teams%20has%20access%20to%20everything%20it%20needs%3F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FOffice-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2%23bkmk_teams%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FOffice-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2%23bkmk_teams%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61095%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61095%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Fedja%2C%3C%2FP%3E%3CP%3ENo%2C%20I%20have%20been%20working%20with%20Microsoft%20for%20almost%20a%20month%20now.%20%26nbsp%3BMost%20of%20the%20effort%20has%20been%20in%20gathering%20information%20for%20Microsoft.%20%26nbsp%3BA%20recorded%20fiddler%20session%2C%20a%20few%20Powershell%20commands%20and%20outputting%20the%20results%20to%20a%20file%20to%20send%20etc...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20Teams%20is%20one%20of%20many%20issues%20I%20am%20having%20with%20my%20tenant.%20In%20addition%20to%20Teams%2C%20I%20also%20cannot%20authenticate%20against%20SharePoint%20using%20Flow%20or%20PowerApps%20nor%20tIOS%20mobile%20app.%20Also%2C%20Delve%20mobile%20app%20does%20not%20work%20either.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20the%20error%20message%20captured%20in%20Fiddler%2C%20which%20has%20been%20consistent%20across%20of%20all%20testing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3Emessage%3DFailed%20to%20acquire%20token%20for%20resource%20https%3A%2F%2F%7Btenant%7D.sharepoint.com%2F.Failed%20to%20acquire%20token%20for%20resource%20https%3A%2F%2F%7Btenant%7D.sharepoint.com%2F.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20moment%20I%20switch%20to%20the%20Files%20Tab%20or%20add%20a%20new%20Tab%20for%20Excel%20(Any%20app%20I%20add%20produces%20the%20message)%20in%20Teams%20the%20response%20returned%20is%20the%20message%20above.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20should%20check%20if%20it's%20the%20same%20for%20you.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61091%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61091%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20still%20an%20issue%20for%20our%20teams%20as%20well.%3C%2FP%3E%3CP%3EFiles%20does%20not%20work%20-%20it%20says%20that%20files%20directory%20is%20setting%20up%2C%20but%20it%20has%20done%20this%20for%20at%20least%20a%20month.%3C%2FP%3E%3CP%3EWith%20that%20comes%20the%20issue%20not%20having%20to%20create%20tabs%20for%20Microsoft%20Word%20or%20Excel.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20progress%20with%20the%20original%20issue%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54776%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54776%22%20slang%3D%22en-US%22%3EI%20have%20an%20E3%20subscription%20so%20I%20pretty%20much%20have%20all%20the%20services.%20I%20also%20think%20or%20at%20least%20leaning%20towards%20a%20problem%20with%20my%20Office%20365%20E3%20tenant%20profile%20and%20how%20Microsoft%20Teams%20communicates%20with%20the%20other%20services.%20Everything%20else%20works%20perfect%20and%20has%20been%20for%20years.%20Office%20365%20Groups%20and%20Team%20Sites%20work%20great.%20I%20see%20the%20Channel%20Folders%2C%20I%20can%20upload%20docs%2C%20create%20pages%20etc..%20but%20on%20the%20Microsoft%20Team%20side%2C%20nothing%20works.%20If%20I%20hear%20anything%20new%20from%20MSFT%2C%20I'll%20update%20the%20post.%20Just%20in%20case%20I%20am%20also%20configured%20as%20a%20First%20Release%20tenant.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54773%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54773%22%20slang%3D%22en-US%22%3E%3CP%3EAh%2C%20you're%20well%20down%20the%20path%20already%2C%20forgive%20me%20throwing%20basics%20at%20you%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20they%20looked%20at%20licensing%20to%20confirm%20there%20are%20no%20conflicts%20there%3F%20Not%20being%20able%20to%20generate%20an%20email%20address%20(provided%20you%20have%20the%20email%20integration%20feature%20turned%20on)%20has%20me%20wondering%20if%20you%20are%20Exchange%20licensed%2C%20SharePoint%20licensed%2C%20etc%20etc.%20You%20may%20have%20already%20checked%20this%20stuff%2C%20but%20if%20not%20this%20is%20worth%20a%20look%20to%20make%20sure%20this%20isn't%20causing%20some%20of%20these%20issues.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54767%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54767%22%20slang%3D%22en-US%22%3EHi%20David%2C%3CBR%20%2F%3EYes%2C%20it%20has%20been%20a%20tough%20issue%20to%20figure%20out.%20I%20opened%20a%20support%20ticket%20with%20Microsoft%20about%20two%20weeks%20ago%20and%20so%20far%20they%20have%20been%20unable%20to%20figure%20the%20root%20cause.%20Browser%20vs.%20Desktop%20(same%20issue)%2C%20Uninstall%20then%20re-install%20(same%20issue)%2C%20Turn%20Off%20Teams%20then%20On%20(same%20issue)%2C%20Delete%20all%20Teams%20and%20create%20new%20ones%20(same%20issue).%20That%20is%20also%20not%20the%20only%20problem%2C%20there%20are%20bugs%20throughout%20for%20example%20if%20I%20click%20the%20ellipse%20next%20to%20the%20name%20of%20the%20Channel%20(above%20Conversation%20Tab)%20and%20select%20%22get%20email%20address%22%20I%20get%20an%20error.%20When%20I%20check%20Fiddler%2C%20a%20%22failed%20to%20acquire%20token%22%20is%20returned.%20This%20message%20appears%20for%20most%20POST%20requests.%20This%20is%20a%20small%20tenant%20and%20I%20tested%20two%20AzureAD%20cloud%20accounts%20(no%20directory%20sync)%20and%20same%20issue%20for%20both.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54759%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54759%22%20slang%3D%22en-US%22%3E%3CP%3EAll%20Teams%20all%20users%3F%20or%20All%20Teams%20but%20just%20for%20Bobby%20Cruz%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20all%20users%2C%20you%20should%20get%20a%20support%20ticket%20opened%20with%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20just%20you%2C%20I'd%20confirm%20whether%20this%20happens%20just%20in%20the%20application%2C%20or%20in%20the%20web%20version%20also.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20just%20the%20application%2C%20I'd%20first%20try%20signing%20out%20completely%20and%20back%20in.%20If%20that%20doesn't%20clear%20it%2C%20try%20uninstalling%20and%20resintalling.%20If%20that%20doesn't%20clear%20it%2C%20support%20ticket%20time%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20both%20application%20and%20web%20version%2C%20potentially%20something%20about%20your%20id%20that%20Teams%20doesn't%20seem%20to%20like%20and%20probably%20support%20ticket%20time%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%2C%20wish%20I%20had%20a%20quick%20fix%20for%20you%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54752%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54752%22%20slang%3D%22en-US%22%3EAll%20Teams%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54750%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54750%22%20slang%3D%22en-US%22%3E%3CP%3EInteresting.%20Sounds%20like%20a%20Teams%20issue%20for%20sure.%20Is%20this%20happening%20just%20for%20you%2C%20or%20for%20all%20users%20of%20this%20specific%20Team%3F%20Trying%20to%20narrow%20to%20whether%20it%20is%20a%20you%20or%20your%20app%20problem%2C%20or%20the%20Team%20itself.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54734%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54734%22%20slang%3D%22en-US%22%3EAlso%2C%20I%20cannot%20open%20the%20Office%20365%20Group%20Team%20Site%20from%20within%20Teams%20nor%20can%20I%20search%20for%20a%20Team%20Site%20or%20Document%20Library%20to%20add%20as%20a%20Channel%20Tab.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54730%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54730%22%20slang%3D%22en-US%22%3EDavid%2C%3CBR%20%2F%3EThe%20Office%20365%20Group%20Team%20Site%20works%20great%2C%20no%20issues%20there.%20The%20issue%20is%20only%20from%20Teams.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54717%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54717%22%20slang%3D%22en-US%22%3E%3CP%3EDoes%20the%20SharePoint%20side%20of%20things%20exist%20at%20all%20and%20just%20Teams%20isn't%20working%3F%20Or%20can%20you%20not%20even%20get%20to%20anything%20in%20SharePoint%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETry%20going%20to%20this%20URL%2C%20replace%20the%20%26lt%3B%26gt%3B%20stuff%20with%26nbsp%3Bthe%20appropriate%20information%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehttps%3A%2F%2F%3CTENANT%3E.sharepoint.com%2Fsites%2F%3CTEAMNAME%3E%2FSitePages%2FHome.aspx%3C%2FTEAMNAME%3E%3C%2FTENANT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20that%20works%20and%20everything%20you%20would%20expect%20is%20available%20through%20the%20various%20Office%20365%20Group%20navigation%2C%20you%20have%20a%20Teams%20issue.%20If%20that%20doesn't%20work%2C%20you%20probably%20have%20a%20Groups%20issue%20-%20my%20guess%20would%20be%20a%20failed%20or%20stuck%20provisioning.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54705%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54705%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20recommended%2C%20I%20added%20a%20post%20to%20the%20feedback%20forum%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54704%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54704%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20message%20%22We%20are%20setting%20up%20your%20file%20directory%22%20has%20been%20persistent%20since%20Microsoft%20Team%20Preview%20became%20available%20for%20First%20Release%20customers.%20%26nbsp%3B%20I%20also%20cannot%20open%20the%20SharePoint%20Site%20from%20Microsoft%20Teams%2C%20it%20displays%20the%20same%20message.%20I%20have%20a%20ticket%20open%20with%20Microsoft%20and%20so%20far%20no%20luck.%20I%20did%20use%20Fiddler%20to%20capture%20the%20request%2Fresponse%20for%20Microsoft%20Teams%20and%20it%20did%20return%20an%20error%20which%20I%20forwarded%20to%20the%20Microsoft%20Support%20Engineer%20working%20on%20my%20case.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20the%20error%3A%3C%2FP%3E%3CDIV%20class%3D%22_n_d3%22%3E%3CDIV%20class%3D%22conductorContent%22%3E%3CDIV%20class%3D%22_n_e%22%3E%3CDIV%20class%3D%22conductorContent%22%3E%3CDIV%20class%3D%22_n_O%22%3E%3CDIV%20class%3D%22_n_S%22%3E%3CDIV%20class%3D%22_n_S%22%3E%3CDIV%20class%3D%22_n_S%22%3E%3CDIV%20class%3D%22_n_T%22%3E%3CDIV%20class%3D%22allowTextSelection%22%3E%3CDIV%20class%3D%22conductorContent%22%3E%3CDIV%20class%3D%22_rp_f%22%3E%3CDIV%20class%3D%22_rp_f%20allowTextSelection%22%3E%3CDIV%20class%3D%22_rp_g%20allowTextSelection%20customScrollBar%20scrollContainer%22%3E%3CDIV%20class%3D%22_rp_h%22%3E%3CDIV%20class%3D%22ms-font-color-neutralPrimary%20ms-font-xl%20ms-fwt-r%20_rp_i%20_rp_j%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%3E%3CDIV%20class%3D%22_rp_75%22%3E%3CDIV%20class%3D%22_rp_K4%20ms-border-color-neutralLight%20ShowReferenceAttachmentsLinks%20ShowConsesusSchedulingLink%22%3E%3CDIV%3E%26nbsp%3B%3CPRE%3EJSON%20-%20response%0A%0AerrorCode%3DForbidden%0Amessage%3DFailed%20to%20acquire%20token%20for%20resource%20https%3A%2F%2Fmytenant.com.Failed%20to%20acquire%20token%20for%20resource%20https%3A%2F%2Fimaginecode.sharepoint.com%2F.%3C%2FPRE%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40453%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40453%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20update%20on%20this%3F%26nbsp%3B%20The%20same%20message%20has%20been%20persistent%20since%20they%20released%20Microsoft%20Teams.%26nbsp%3B%20I%20also%20want%20point%20out%20that%20with%20the%20Office%20365%20Group%20linked%20to%20my%20Team%20the%20files%20and%20folders%20under%20the%20site%20document%26nbsp%3B%20library%20render%20and%20work%20as%20expected.%20This%20issue%20is%20only%20with%20Microsoft%20Teams.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-33172%22%20slang%3D%22en-US%22%3ERE%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-33172%22%20slang%3D%22en-US%22%3ESame%20here%2C%20will%20open%20a%20Ticket.%20BTW%2C%20Teams%20file%20Directory%20displays%20Access%20Files%20as%20One%20Note%2C%20this%20may%20confuse%20People%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32536%22%20slang%3D%22en-US%22%3ERE%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32536%22%20slang%3D%22en-US%22%3EThanks%20for%20reporting%20this%2C%20Robert.%20Can%20you%20please%20share%20the%20bug%20via%0AFeedback%20in%20the%20Microsoft%20Teams%20app%20(lower%20left%20hand%20corner)%20or%20via%20User%0AVoice%3A%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fteamspublicfeedback%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fteamspublicfeedback%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-32140%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-32140%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20we%20are%20seeing%20the%20same%20issue%2C%20been%20getting%20that%20message%20for%20over%20two%20weeks%20now.%20%26nbsp%3BOur%20O365%20admin%20has%20opened%20a%20ticket%20with%20Microsoft%2C%20no%20fix%2C%20no%20eta.%20%26nbsp%3BI%20believe%20it%20has%20to%20do%20with%20some%20sort%20of%20security%20on%20our%20tenant.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-31258%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-31258%22%20slang%3D%22en-US%22%3ENot%20in%20my%20side%2C%20I%20think%20you%20should%20open%20a%20ticket%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-992047%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-992047%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37019%22%20target%3D%22_blank%22%3E%40Bobby%20Cruz%3C%2FA%3E%26nbsp%3Bthanks%20for%20documenting%20this!%26nbsp%3B%20We%20had%20a%203%20year%20old%20app%20stub%20at%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faad.portal.azure.com%2F%23blade%2FMicrosoft_AAD_RegisteredApps%2FApplicationsListBlade%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faad.portal.azure.com%2F%23blade%2FMicrosoft_AAD_RegisteredApps%2FApplicationsListBlade%3C%2FA%3E%20that%20listed%20the%20root%20SP%20site%20as%20the%20authentication%20redirect.%26nbsp%3B%20Removing%20it%20fixed%20our%20Teams%20issue%20(we're%20getting%20ready%20to%20roll%20it%20out)%20and%20about%203%20other%20issues%2C%20including%20preventing%20cloud%20backups%20from%20accessing%20SharePoint%20online%20via%20REST%20API%20and%20MS%20Office%20accessing%20SharePoint%20files%20directly...%26nbsp%3B%20thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1242376%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1242376%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20user%20reported%20this%20issue%20with%20a%20new%20Team%20created.%20I%20tried%20it%20and%20I%20got%20the%20same%20issue%20(going%20from%20Teams%20to%20Sharepoint).%3C%2FP%3E%3CP%3EIt%20got%20resolved%20after%20I%20tried%20my%20other%20teams%2C%20and%20tried%20to%20access%20Sharepoint%20successfully%2C%20somehow%2C%20that%20allowed%20that%20specific%20team%20to%20allow%20accessing%20SharePoint%20for%20that%20specific%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1949439%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1949439%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2774%22%20target%3D%22_blank%22%3E%40Robert%20Lavin%3C%2FA%3E%26nbsp%3BI%20am%20having%20the%20same%20issue%2C%20only%20on%20one%20of%20the%20teams%20channel.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20you%20find%20a%20solution%20for%20it%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22drag-cta%22%3E%3CEM%3E%3CSTRONG%3EWe%20are%20setting%20up%20your%20file%20directory.%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%20class%3D%22drag-cta-subtext%22%3E%3CEM%3E%3CSTRONG%3ETry%20refreshing%20the%20page%20after%20a%20few%20minutes%20or%20check%20back%20later.%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1949748%22%20slang%3D%22en-US%22%3ERe%3A%20We%20are%20setting%20up%20your%20file%20directory...someday%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1949748%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F698034%22%20target%3D%22_blank%22%3E%40marbaque%3C%2FA%3E%26nbsp%3B%20I%20did%20have%20to%20use%20Fiddler%20to%20isolate%20the%20problem%20or%20at%20the%20very%20least%20try%20to%20determine%20if%20this%20was%20a%20configuration%20issue%20i.e.%20endpoint%20url%2C%20or%20token.%26nbsp%3B%20In%20my%20case%20it%20was%20an%20endpoint%20(Sign%20Url)%20url%20for%20a%20custom%20Azure%20App%20I%20created%20which%20was%20incorrect.%26nbsp%3B%20%26nbsp%3BOnce%20I%20deleted%20the%20application%2C%20everything%20began%20to%20work%20as%20expected.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hello,

 

I have a number of teams I have setup as part of an internal test we are running. Some of the teams and some of the channels under the Teams continually say in the File and Notes tab:

 

"We are setting up your file directory. Try refreshing the page after a few minutes or check back later."

 

To keep things interesting, I have a set of teams and channels under them that do work properly and have fully functioning Files and Notes tabs. 

 

Has anyone else seen this?

 

Thanks,

 

-Rob Lavin

41 Replies
Not in my side, I think you should open a ticket

Yes we are seeing the same issue, been getting that message for over two weeks now.  Our O365 admin has opened a ticket with Microsoft, no fix, no eta.  I believe it has to do with some sort of security on our tenant.

Thanks for reporting this, Robert. Can you please share the bug via Feedback in the Microsoft Teams app (lower left hand corner) or via User Voice: http://aka.ms/teamspublicfeedback
Same here, will open a Ticket. BTW, Teams file Directory displays Access Files as One Note, this may confuse People

Any update on this?  The same message has been persistent since they released Microsoft Teams.  I also want point out that with the Office 365 Group linked to my Team the files and folders under the site document  library render and work as expected. This issue is only with Microsoft Teams.

The message "We are setting up your file directory" has been persistent since Microsoft Team Preview became available for First Release customers.   I also cannot open the SharePoint Site from Microsoft Teams, it displays the same message. I have a ticket open with Microsoft and so far no luck. I did use Fiddler to capture the request/response for Microsoft Teams and it did return an error which I forwarded to the Microsoft Support Engineer working on my case.  

 

Here is the error:

 

As recommended, I added a post to the feedback forum

Does the SharePoint side of things exist at all and just Teams isn't working? Or can you not even get to anything in SharePoint?

 

Try going to this URL, replace the <> stuff with the appropriate information:

 

https://<tenant>.sharepoint.com/sites/<TeamName>/SitePages/Home.aspx

 

If that works and everything you would expect is available through the various Office 365 Group navigation, you have a Teams issue. If that doesn't work, you probably have a Groups issue - my guess would be a failed or stuck provisioning.

David,
The Office 365 Group Team Site works great, no issues there. The issue is only from Teams.
Also, I cannot open the Office 365 Group Team Site from within Teams nor can I search for a Team Site or Document Library to add as a Channel Tab.

Interesting. Sounds like a Teams issue for sure. Is this happening just for you, or for all users of this specific Team? Trying to narrow to whether it is a you or your app problem, or the Team itself.

All Teams all users? or All Teams but just for Bobby Cruz?

 

If all users, you should get a support ticket opened with Microsoft.

 

If just you, I'd confirm whether this happens just in the application, or in the web version also.

 

If just the application, I'd first try signing out completely and back in. If that doesn't clear it, try uninstalling and resintalling. If that doesn't clear it, support ticket time again.

 

If both application and web version, potentially something about your id that Teams doesn't seem to like and probably support ticket time again.

 

Sorry, wish I had a quick fix for you :(

Hi David,
Yes, it has been a tough issue to figure out. I opened a support ticket with Microsoft about two weeks ago and so far they have been unable to figure the root cause. Browser vs. Desktop (same issue), Uninstall then re-install (same issue), Turn Off Teams then On (same issue), Delete all Teams and create new ones (same issue). That is also not the only problem, there are bugs throughout for example if I click the ellipse next to the name of the Channel (above Conversation Tab) and select "get email address" I get an error. When I check Fiddler, a "failed to acquire token" is returned. This message appears for most POST requests. This is a small tenant and I tested two AzureAD cloud accounts (no directory sync) and same issue for both.

Ah, you're well down the path already, forgive me throwing basics at you :)

 

Have they looked at licensing to confirm there are no conflicts there? Not being able to generate an email address (provided you have the email integration feature turned on) has me wondering if you are Exchange licensed, SharePoint licensed, etc etc. You may have already checked this stuff, but if not this is worth a look to make sure this isn't causing some of these issues.

I have an E3 subscription so I pretty much have all the services. I also think or at least leaning towards a problem with my Office 365 E3 tenant profile and how Microsoft Teams communicates with the other services. Everything else works perfect and has been for years. Office 365 Groups and Team Sites work great. I see the Channel Folders, I can upload docs, create pages etc.. but on the Microsoft Team side, nothing works. If I hear anything new from MSFT, I'll update the post. Just in case I am also configured as a First Release tenant.

This is still an issue for our teams as well.

Files does not work - it says that files directory is setting up, but it has done this for at least a month.

With that comes the issue not having to create tabs for Microsoft Word or Excel.

 

Any progress with the original issue? 

Hi Fedja,

No, I have been working with Microsoft for almost a month now.  Most of the effort has been in gathering information for Microsoft.  A recorded fiddler session, a few Powershell commands and outputting the results to a file to send etc...

 

Microsoft Teams is one of many issues I am having with my tenant. In addition to Teams, I also cannot authenticate against SharePoint using Flow or PowerApps nor tIOS mobile app. Also, Delve mobile app does not work either.

 

This is the error message captured in Fiddler, which has been consistent across of all testing.

 

message=Failed to acquire token for resource https://{tenant}.sharepoint.com/.Failed to acquire token for resource https://{tenant}.sharepoint.com/.

 

The moment I switch to the Files Tab or add a new Tab for Excel (Any app I add produces the message) in Teams the response returned is the message above.

 

You should check if it's the same for you. 

Not being able to get tokens is identity or network issues, and since all the rest of us are running fine it would have to be something with your configuration. Possible, but I would doubt it is something actually wrong with your tenant as I'm assuming support would have checked the health of your tenant fairly early in their process.

 

Have you been through this to make sure Teams has access to everything it needs? https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-ab...