How to share Content to Stage for external Users in Teams App?

[sdenninger]

Hello!

We have implemented a team app in React and one of our core functions is to share certain content (Video) in the stage.
There are users from the tenant in which the app is installed as well as users from external tenants who want to see the content of the app in the stage of a meeting. The teamsapp is only controlled by users of the tenant in which the app was installed.
The use of microsoftTeams.meeting.shareAppContentToStage() generates the following error message for users from other tenants, when starting sharing:

When testing locally via the teams toolkit, this works without any problems for users of different tenants. Only when the app is installed via admin.teams.microsoft.com does the error occur for external users.

Another user has already noted similar behavior at:

https://github.com/OfficeDev/microsoft-teams-library-js/issues/1524#issuecomment-1459629569.

The answer there was: "This is by design. Cross-tenant is not supposed to work."

Is there a way for external/anonymous users to see the content of the stage without this error message appearing? Does anyone know of another way to share content with external users?

Here is some more information:

It is not necessary for the users to authenticate themselves or anything similar in the stage frame. The shared website is a subpage of the Teamsapp and is therefore hosted in the same domain. 

The users simply want to see the content of the shared URL that was passed to the shareAppContentToStage method.

Thank you very much for your help/tips and have a nice day.

Used Teams Version (new Teams): 1415/24031414714

Used Teams-js Version: "@microsoft/teams-js": "^2.19.0",

Update: It would be like the YouTube app. This app also works with external and anonymous users

[#2]

Hello @sdenninger ,
Thanks for raising your issue. We will check this at our end and will update you accordingly.

[#3]

Hello @Vaibhav-MSFT,

Have you been able to check this topic yet?

[#4]

Hello @sdenninger ,
We are checking this with engineering team and will get back to you once we get any update.

[#5]

Hello @Vaibhav-MSFT,

Can you please tell me when I can expect an answer from the engineering team? One of our customers has just asked again whether it is possible to use our TeamsApp with external users.

[#6]

Hello @sdenninger,
We have again informed engineering team regarding this issue. We will let you know as soon as we get any update from them  

[#7]

Hi @sdenninger,
Sorry for the delay in the response. We check this issue internally with engineering team. They have fixed this issue. To help you better, please ensure the following steps are completed to support anonymous users seeing pre-pinned apps:

• The app must have static tabs with groupChat scope.
• The app must be added as part of the setup policy in the admin center and applied to the user.
• The app must have supportsAnonymousGuestUsers in the app manifest under meetingExtensionDefinition.
• The tenant must allow anonymous user interaction with apps in meetings.

[#8]

Hi @Dinesh-MSFT ,

When you announced the information a month ago, I did a quick test and I was able to see the shared content as a user from another tenant and as an anonymous user without authentication after adding “supportsAnonymousGuestUsers” in “meetingExtensionDefinition” to the manifest. In addition, the 2nd bullet point (The app must be added as part of the setup policy in the admin center and applied to the user) and the 4th bullet point (The tenant must allow anonymous user interaction with apps in meetings.) were applied.

A retest now shows that it no longer works for users from external tenants and the old error screen “Can't show this window Something went wrong” appeared again. We tested users from 2 different external tenants.
As an anonymous user I can see the shared content.
Has something been adjusted here again? Or could it be due to a security policy that was set in the external tenants that this is no longer possible? Unfortunately, we do not have administrative access here.

You describe that the app requires “static tabs with groupChat scope”.

Our app is built from ConfigurableTabs as there is a need to customize query parameters of the URL at runtime. (a dynamic channel ID is passed to the content shared via the API, which cannot be defined in the manifest)

If this is the reason, could you ask again whether the feature could also be implemented for ConfigurableTabs?

I ran the tests in the Teams client (new; Windows) and in the web app with the latest version in each case.

Thanks for your information,

Sebastian