External Websites Published as Apps through App Studio

%3CLINGO-SUB%20id%3D%22lingo-sub-1679544%22%20slang%3D%22en-US%22%3EExternal%20Websites%20Published%20as%20Apps%20through%20App%20Studio%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1679544%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20new%20to%20creating%20app%20packages%20in%20app%20studio.%20I%20have%20an%20external%20web-delivered%20application%20that%20I%20want%20to%20turn%20into%20a%20packaged%20app%20so%20it%20can%20be%20pinned%20to%20the%20sidebar.%20It's%20setup%20and%20working%2C%20but%20unfortunately%2C%20the%20site%20launches%20a%20new%20window%20after%20a%20user%20logs%20in%2C%20and%20that%20new%20window%20is%20kicking%20off%20a%20browser%20session%20instead%20of%20loading%20inside%20the%20app.%20Is%20there%20anyway%20to%20constrain%20things%20to%20launching%20within%20the%20teams%20client%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1679544%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApp%20Studio%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELOB%20Apps%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1683551%22%20slang%3D%22en-US%22%3ERe%3A%20External%20Websites%20Published%20as%20Apps%20through%20App%20Studio%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1683551%22%20slang%3D%22en-US%22%3Edo%20you%20own%20the%20target%20website%2C%20such%20that%20you're%20able%20to%20make%20changes%20to%20it%3F%20If%20so%2C%20you%20could%20detect%20that%20it's%20a%20Teams%20visitor%20and%20change%20the%20behaviour.%20If%20not%2C%20what%20exactly%20would%20you%20expect%20to%20happen%2C%20given%20that%20this%20is%20the%20site's%20behaviour%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1684742%22%20slang%3D%22en-US%22%3ERe%3A%20External%20Websites%20Published%20as%20Apps%20through%20App%20Studio%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1684742%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F150%22%20target%3D%22_blank%22%3E%40Hilton%20Giesenow%3C%2FA%3E%26nbsp%3B-%20Sadly%20we%20do%20not%20own%20the%20target%20website.%20It's%20a%20SaaS%20app%20that%20we%20pay%20for.%20The%20underpinning%20for%20Teams%20is%20an%20HTML5%20framework.%20What%20I%20was%20hoping%20was%20that%20in%20the%20desktop%20app%20there%20might%20be%20a%20way%20to%20have%20new%20windows%20that%20are%20opened%20by%20an%20app%20launch%20inside%20the%20teams%20client%20windows%20(potentially%20replacing%20the%20previously%20displayed%20page%2C%20or%20maybe%20by%20creating%20a%20tab%3F).%26nbsp%3B%20Right%20now%20when%20I%20package%20the%20website%20in%20App%20Studio%20and%20then%20pin%20it%20to%20the%20sidebar%2C%20the%20site%20launches%2C%20authenticates%2C%20and%20then%20launches%20a%20new%20window%20which%20spawns%20a%20browser%20and%20takes%20the%20user%20outside%20of%20teams%20(boooo).%20I'd%20like%20to%20keep%20them%20inside%20the%20teams%20framework.%26nbsp%3B%20I%20hope%20that%20helps%20%2F%20makes%20sense.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1684744%22%20slang%3D%22en-US%22%3ERe%3A%20External%20Websites%20Published%20as%20Apps%20through%20App%20Studio%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1684744%22%20slang%3D%22en-US%22%3EI%20should%20also%20mention%20too%20that%20I%20was%20assuming%20that%20if%20it%20was%20possible%2C%20it%20might%20require%20putting%20a%20Sharepoint%20wrapper%20around%20it%2C%20or%20doing%20some%20code-work%20inside%20App%20Studio...%20I'm%20not%20specifically%20looking%20for%20a%20Teams%20desktop%20client%20hack...%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1688691%22%20slang%3D%22en-US%22%3ERe%3A%20External%20Websites%20Published%20as%20Apps%20through%20App%20Studio%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1688691%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F797627%22%20target%3D%22_blank%22%3E%40Todd_Knapp%3C%2FA%3E%26nbsp%3Bthis%20is%20tricky%20because%20it's%203rd%20party.%20Is%20that%20popup%20-necessary-%2C%20or%20would%20it%20be%20fine%20to%20block%20it%20entirely%20(would%20the%20user%20miss%20it%20if%20it%20wasn't%20there%3F)%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I'm new to creating app packages in app studio. I have an external web-delivered application that I want to turn into a packaged app so it can be pinned to the sidebar. It's setup and working, but unfortunately, the site launches a new window after a user logs in, and that new window is kicking off a browser session instead of loading inside the app. Is there anyway to constrain things to launching within the teams client? 

12 Replies
do you own the target website, such that you're able to make changes to it? If so, you could detect that it's a Teams visitor and change the behaviour. If not, what exactly would you expect to happen, given that this is the site's behaviour?

@Hilton Giesenow - Sadly we do not own the target website. It's a SaaS app that we pay for. The underpinning for Teams is an HTML5 framework. What I was hoping was that in the desktop app there might be a way to have new windows that are opened by an app launch inside the teams client windows (potentially replacing the previously displayed page, or maybe by creating a tab?).  Right now when I package the website in App Studio and then pin it to the sidebar, the site launches, authenticates, and then launches a new window which spawns a browser and takes the user outside of teams (boooo). I'd like to keep them inside the teams framework.  I hope that helps / makes sense. 

I should also mention too that I was assuming that if it was possible, it might require putting a Sharepoint wrapper around it, or doing some code-work inside App Studio... I'm not specifically looking for a Teams desktop client hack...

@Todd_Knapp this is tricky because it's 3rd party. Is that popup -necessary-, or would it be fine to block it entirely (would the user miss it if it wasn't there?)?

@Hilton Giesenow - Yeah.... it's a needed popup unfortunately. The software does something strange with MFA and launches a window temporarily during auth. I suspected this would be difficult. I was hoping that I could put the whole thing into a frame in Sharepoint and then publish that into the app? I dunno... I'm grasping at straws :) 

What happens once the user is authenticated? Can they just close the browser tab?
Unfortunately, no.... the content portion is what's launching in the other browser. If you'd like to see some examples, I can do a screen cap or a short video for you...
ahhh ok, that's tricky. I'm out of ideas, I'm afraid :(
Thanks for trying! :)
Sure thing, sorry I couldn't help more

@Todd_Knapp If your external app have any auth implemented, you need to implement authentication for your tabs else it will redirect to browser also please make sure you have added your URL to validDomain array

@Hilton Giesenow What can be the proper way to detect if it's a Teams visitor?
I've been looking around for a solution to this.
Please let me know.
Thank you