SOLVED

Internal linking not possible: We only support linking to files in your own organization.

%3CLINGO-SUB%20id%3D%22lingo-sub-907285%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-907285%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F356559%22%20target%3D%22_blank%22%3E%40simuuh%3C%2FA%3E%26nbsp%3BI%20have%20also%20had%20the%20same%20issue%20reported%20by%20our%20users.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUser%20was%20trying%20to%20link%20to%20a%20file%20in%20another%20site.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20replicated%20the%20issue%20by%20added%20a%20sample%20page%2C%20with%20the%20page%20viewer%20on%20it%2C%20and%20tried%20to%20link%20to%20a%20%3CU%3E%3CSTRONG%3Edocument%20in%20the%26nbsp%3Bsame%20site%20and%20also%20got%20the%20error.%26nbsp%3B%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FP%3E%3CP%3E%3CU%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20981px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F137066iD6A994524AF33AC1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22FileViewerUnsupportedLink.png%22%20title%3D%22FileViewerUnsupportedLink.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FU%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-907632%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-907632%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20has%20occurred%20for%20us%20too.%20We'd%20be%20keen%20to%20get%20an%20answer%20quickly.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-907737%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-907737%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F424026%22%20target%3D%22_blank%22%3E%40simonjking%3C%2FA%3EHave%20you%20already%20opened%20a%20ticket%20at%20Microsoft%3F%20its%20not%20possible%20to%20create%20link%20to%20any%20file%20-%20not%20even%20in%20same%20site%20collection.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-905093%22%20slang%3D%22en-US%22%3EInternal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-905093%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20few%20days%20we%20got%20this%20error%20message%20if%20we%20try%20to%20add%20a%20link%20to%20a%20file%20or%20document%20on%20a%20sharepoint%20site%3A%20%22%3CSPAN%3EWe%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20767px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F137136iBBCAA087995ABF25%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222019-10-10%2013_10_26-Window_02.png%22%20title%3D%222019-10-10%2013_10_26-Window_02.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ewhich%20option%20throw%20this%20error%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-905093%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-911363%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-911363%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F356559%22%20target%3D%22_blank%22%3E%40simuuh%3C%2FA%3E%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F236366%22%20target%3D%22_blank%22%3E%40Melinda%20Grant%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMorning%20Team%20-%20I%20left%20this%2024%20hours%20(actually%20longer%20due%20to%20the%20weekend).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20premier%20support%20with%20Microsoft%20and%20have%20raised%20a%20ticket%20-%20%3CSPAN%3ETicket%20%2317095544.%26nbsp%3B%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI%20will%20let%20you%20know%20the%20outcome.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-911393%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-911393%22%20slang%3D%22en-US%22%3E%3CP%3EEngineer%20assigned%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-913227%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-913227%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F356559%22%20target%3D%22_blank%22%3E%40simuuh%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F236366%22%20target%3D%22_blank%22%3E%40Melinda%20Grant%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFeedback%20is%20there%20has%20been%20multiple%20changes%20to%20this%20web%20part%20over%20the%20last%20two%20weeks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20engineer%20is%20in%20touch%20with%20the%20product%20owner%20of%20this%20web%20part%20and%20we%20are%20waiting%20a%20response%20from%20this%20team.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWatch%20this%20space!!!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-913268%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-913268%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F424026%22%20target%3D%22_blank%22%3E%40simonjking%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F356559%22%20target%3D%22_blank%22%3E%40simuuh%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F236366%22%20target%3D%22_blank%22%3E%40Melinda%20Grant%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20got%20a%20feedback%20on%20twitter%20that%20this%20issue%20is%20also%20affecting%20the%20Image%20viewer%20Webpart.%20Hopefully%20they%20will%20fix%20it%20soon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-914704%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-914704%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F424026%22%20target%3D%22_blank%22%3E%40simonjking%3C%2FA%3E%26nbsp%3Bthank%20you%20for%20the%20update.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F99168%22%20target%3D%22_blank%22%3E%40Jimmy%20Hang%3C%2FA%3E%26nbsp%3Bas%20we%20see%20it%2C%20no%20internal%20link%20can%20be%20created%20in%20any%20web%20part.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915092%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915092%22%20slang%3D%22en-US%22%3Eyeah%20same%20for%20me%2C%20sheer%20Boll....cks%20if%20you%20ask%20me.%20Fix%20already%20needed%203%20months%20ago.%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-916183%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916183%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F356559%22%20target%3D%22_blank%22%3E%40simuuh%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F236366%22%20target%3D%22_blank%22%3E%40Melinda%20Grant%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F99168%22%20target%3D%22_blank%22%3E%40Jimmy%20Hang%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F370006%22%20target%3D%22_blank%22%3E%40Sarnst%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EProduct%20Owner%20has%20provided%20the%20following%20feedback%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%22This%20issue%20has%20been%20identified%20as%20a%20bug%2C%20and%20the%20product%20team%20is%20working%20on%20the%20fix%20now.%20I%20will%20monitor%20the%20progress%20and%20keep%20you%20all%20updated.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tested%20this%20issue%20against%20the%20following%20web%20parts%20and%20all%20are%20impacted.%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Image%3C%2FP%3E%3CP%3E-%20File%20Viewer%3C%2FP%3E%3CP%3E-%20Image%20Gallery%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-916733%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916733%22%20slang%3D%22en-US%22%3E%3CP%3EExperiencing%20the%20same%20issue%2C%20any%20updates%20today%3F%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20there%20any%20public%20board%20where%20it%20is%20possible%20to%20follow%20this%20issue%3F%20There's%20no%20notice%20of%20it%20in%20our%20admin%20center%20regarding%20service%20health.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-917040%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-917040%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F307336%22%20target%3D%22_blank%22%3E%40NiclasDahl%3C%2FA%3E%26nbsp%3Bonly%20way%20I%20think%20is%20to%20raise%20a%20support%20ticket%20in%20Office%20365.%20I%20just%20created%20one%26nbsp%3B%3CSPAN%3E%23%E2%80%8E17146737%E2%80%8E%2C%20maybe%20MS%20will%20aknowledge%20this%20as%20a%20BUG%20if%20more%20of%20us%20report%20it%20in.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-917111%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-917111%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F307336%22%20target%3D%22_blank%22%3E%40NiclasDahl%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F99168%22%20target%3D%22_blank%22%3E%40Jimmy%20Hang%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20already%20have%20a%20ticket%20raised%20-%20they%20have%20identified%20this%20as%20a%20bug%20but%20have%20yet%20to%20provide%20a%20ETA%20for%20fix.%20They%20confirmed%20the%20fix%20will%20apply%20to%20the%20File%20Viewer%2C%20Image%20%26amp%3B%20Image%20Gallery%20web%20parts.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CEM%3EYes%20the%20bug%20info%20has%20included%20the%20image%20issue.%20Thanks%20for%20updating%20the%20information%20in%20the%20community.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EThe%20bug%20fix%20may%20take%20a%20little%20long%20time%2C%20and%20currently%20I%20haven%E2%80%99t%20got%20ETA%20for%20the%20fix.%3C%2FEM%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20going%20to%20put%20pressure%20on%20providing%20an%20ETA%20-%20as%20this%20is%20something%20that%20was%20working%2C%20a%20change%20has%20been%20made%20and%20now%20it%20is%20not%20working%20as%20intended.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-917119%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-917119%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20asked%20the%20following%20in%20my%20Ticket%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CU%3EETA%20for%20fix%20%E2%80%93%20Can%20this%20be%20provided%20%E2%80%93%20these%20were%20working%20web%20parts%3A%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EA%20change%20to%20SPO%20web%20parts%20has%20broken%20them%20%E2%80%93%20a%20little%20nervous%20that%20changes%20can%20be%20made%20to%20Office%20365%20that%20effectively%20break%20the%20functionality%20and%20then%20it%20could%20be%20days%2Fweeks%20before%20it%20is%20fixed%2C%20what%20was%20the%20QA%2FTesting%20process%20involved%20%E2%80%93%20how%20did%20this%20bug%20get%20into%20production.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECould%20these%20answers%20be%20provided%20to%20provide%20assurance%20that%20steps%20have%20been%20taken%20to%20prevent%20these%20things%20from%20happening%20again%20e.g.%20improved%20QA%2FTesting%20process.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20860px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F138053iB607583FD843F12F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22rings.png%22%20title%3D%22rings.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-917634%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-917634%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Everyone%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFirst%2C%20apologies%20for%20any%20inconveniences%20during%20this%20investigation.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20believe%20we%20have%20identified%20the%20issue%20and%20applied%20a%20fix%20early%20today.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20still%20seeing%20any%20issues%20with%20this%20functionality%20please%20let%20me%20know.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegards%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESam%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-917653%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-917653%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F49589%22%20target%3D%22_blank%22%3E%40Sam%20Larson%3C%2FA%3E%26nbsp%3BI%20checked%20the%20%22Quicklink%22%20webpart%20with%20an%20Icon%20from%20an%20library%20and%20it%20works.%20thank%20you.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20next%20time%2C%20a%20message%20in%20%22Service%20health%22%20would%20be%20nice%20...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-917656%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-917656%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F356559%22%20target%3D%22_blank%22%3E%40simuuh%3C%2FA%3E%20Thank%20you%20for%20confirming%20and%20I%20appreciate%20the%20feedback.%20We%20always%20try%20to%20report%20issues%20to%20our%20service%20health%20dashboard%20as%20quickly%20as%20possible%20%2C%20once%20again%20I%20apologize%20for%20the%20delay%20here.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-918381%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-918381%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F49589%22%20target%3D%22_blank%22%3E%40Sam%20Larson%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20also%20confirm%20web%20parts%20are%20working%20again%20-%20tested%20Image%20Viewer%2C%20Filer%20Viewer%20and%20Image%20Gallery.%20'%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExcellent%20work%2C%20thank%20you%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F49589%22%20target%3D%22_blank%22%3E%40Sam%20Larson%3C%2FA%3E%26nbsp%3B.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1072717%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1072717%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F49589%22%20target%3D%22_blank%22%3E%40Sam%20Larson%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20ran%20across%20this%20thread%20trying%20to%20troubleshoot%20the%20same%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20been%20using%20Document%20Sets%20recently%20and%20found%20that%20if%20we%20try%20to%20link%20images%20and%20documents%2C%20stored%20in%20Document%20Sets%2C%20to%20these%20web%20parts%2C%20we%20still%20get%20the%20same%20error%20mentioned.%20Do%20you%20know%20if%20this%20scenario%20was%20considered%20while%20applying%20the%20fix%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3CBR%20%2F%3EKirtan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1072755%22%20slang%3D%22en-US%22%3ERe%3A%20Internal%20linking%20not%20possible%3A%20We%20only%20support%20linking%20to%20files%20in%20your%20own%20organization.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1072755%22%20slang%3D%22en-US%22%3EHey%20Kirtan%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20fixed%20applied%20previously%20was%20to%20all%20web%20parts.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20are%20running%20into%20a%20similar%20error%20with%20Document%20Sets%20I'd%20suggest%20opening%20a%20support%20ticket%20so%20we%20can%20investigate%20the%20cause.%3CBR%20%2F%3E%3CBR%20%2F%3ERegards%2C%3CBR%20%2F%3E%3CBR%20%2F%3ESam%3C%2FLINGO-BODY%3E
Occasional Contributor

Since few days we got this error message if we try to add a link to a file or document on a sharepoint site: "We only support linking to files in your own organization."

 

2019-10-10 13_10_26-Window_02.png

 

which option throw this error?

20 Replies

@simuuh I have also had the same issue reported by our users. 

 

User was trying to link to a file in another site. 

 

I replicated the issue by added a sample page, with the page viewer on it, and tried to link to a document in the same site and also got the error. 

FileViewerUnsupportedLink.png

This has occurred for us too. We'd be keen to get an answer quickly.

@simonjkingHave you already opened a ticket at Microsoft? its not possible to create link to any file - not even in same site collection.

@simuuh@Melinda Grant 

 

Morning Team - I left this 24 hours (actually longer due to the weekend). 

 

We have premier support with Microsoft and have raised a ticket - Ticket #17095544. 

I will let you know the outcome. 

@simuuh @Melinda Grant 

 

Feedback is there has been multiple changes to this web part over the last two weeks.

 

The engineer is in touch with the product owner of this web part and we are waiting a response from this team. 

 

Watch this space!!! 

@simonjking @simuuh @Melinda Grant 

 

I got a feedback on twitter that this issue is also affecting the Image viewer Webpart. Hopefully they will fix it soon.

 

Cheers

@simonjking thank you for the update.

 

@Jimmy Hang as we see it, no internal link can be created in any web part.

yeah same for me. Fix already needed 3 months ago. :)

@simuuh @Melinda Grant @Jimmy Hang @Sarnst 

 

Product Owner has provided the following feedback 

"This issue has been identified as a bug, and the product team is working on the fix now. I will monitor the progress and keep you all updated."

 

I have tested this issue against the following web parts and all are impacted. 

- Image

- File Viewer

- Image Gallery

Experiencing the same issue, any updates today?

Is there any public board where it is possible to follow this issue? There's no notice of it in our admin center regarding service health.

@NiclasDahl only way I think is to raise a support ticket in Office 365. I just created one #‎17146737‎, maybe MS will aknowledge this as a BUG if more of us report it in.

@NiclasDahl @Jimmy Hang 

 

I already have a ticket raised - they have identified this as a bug but have yet to provide a ETA for fix. They confirmed the fix will apply to the File Viewer, Image & Image Gallery web parts.

 

"Yes the bug info has included the image issue. Thanks for updating the information in the community.

The bug fix may take a little long time, and currently I haven’t got ETA for the fix."

 

I am going to put pressure on providing an ETA - as this is something that was working, a change has been made and now it is not working as intended. 

 

 

I have asked the following in my Ticket 

 

ETA for fix – Can this be provided – these were working web parts:

A change to SPO web parts has broken them – a little nervous that changes can be made to Office 365 that effectively break the functionality and then it could be days/weeks before it is fixed, what was the QA/Testing process involved – how did this bug get into production.

 

Could these answers be provided to provide assurance that steps have been taken to prevent these things from happening again e.g. improved QA/Testing process.

rings.png

 

 

 

Best Response confirmed by simuuh (Occasional Contributor)
Solution

Hello Everyone,

 

First, apologies for any inconveniences during this investigation. 

 

I believe we have identified the issue and applied a fix early today. 

If you are still seeing any issues with this functionality please let me know.

 

Regards,

 

Sam

 

@Sam Larson I checked the "Quicklink" webpart with an Icon from an library and it works. thank you.

 

The next time, a message in "Service health" would be nice ...

@simuuh Thank you for confirming and I appreciate the feedback. We always try to report issues to our service health dashboard as quickly as possible , once again I apologize for the delay here. 

@Sam Larson 

 

I can also confirm web parts are working again - tested Image Viewer, Filer Viewer and Image Gallery. '

 

Excellent work, thank you @Sam Larson . 

Hello @Sam Larson,

 

I ran across this thread trying to troubleshoot the same issue.

 

We have been using Document Sets recently and found that if we try to link images and documents, stored in Document Sets, to these web parts, we still get the same error mentioned. Do you know if this scenario was considered while applying the fix?

 

Regards,
Kirtan