Can't Open Linked Document in Teams

%3CLINGO-SUB%20id%3D%22lingo-sub-2279214%22%20slang%3D%22en-US%22%3ECan't%20Open%20Linked%20Document%20in%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2279214%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20using%20the%20Government%20subscription%20of%20Teams.%20I%20needed%20to%20share%20a%20document%20via%20Teams%20from%20another%20SharePoint%20site%20outside%20of%20the%20Teams%20collection.%20I%20went%20through%20the%20process%20to%20link%20a%20document.%20The%20file%20extension%20that%20results%20is%20.aspx.%20When%20I%20add%20the%20.aspx%20to%20the%20Teams%20SharePoint%20site%20the%20file%20launches%20fine%20via%20SharePoint.%20When%20I%20navigate%20to%20the%20file%20via%20Teams%20and%20try%20and%20launch%20the%20file%20I%20get%20the%20following%20message%20(Screenshot%20attached).%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%20image-alt%3D%22mbracher_0-1619095568914.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F274701i14237936EC4A11F9%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22mbracher_0-1619095568914.png%22%20alt%3D%22mbracher_0-1619095568914.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2279214%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Visitor

I am using the Government subscription of Teams. I needed to share a document via Teams from another SharePoint site outside of the Teams collection. I went through the process to link a document. The file extension that results is .aspx. When I add the .aspx to the Teams SharePoint site the file launches fine via SharePoint. When I navigate to the file via Teams and try and launch the file I get the following message (Screenshot attached).

 

mbracher_0-1619095568914.png

 

0 Replies