Guiding Users to Install the Team Version First for Apps with Both Scopes

[sangdelattre]

Hi Team,

BACKGROUND:
We have developed an app that need to be installed in a team / channel so it can work.
We also have developped a personal scope module that act as an add-in to the channel app.

It’s important to note that the Personal App is not a standalone product — it requires users to also have access to the Channel App.
when publishing the app, in the manifest, our app has both scope: personnal and team

CURRENT CHALLENGE:
When users attempt to install our app from the Store, the first call-to-action they see is “Open.” This leads them into installing the Personal App first.

As a result, many users end up with the Personal App only. When they open it without having access to the Channel App, we display a guidance page inviting them to install the Channel App. Unfortunately, this approach has not been effective. Despite testing several variations of the guidance, users rarely find their way to install the channel app. Over 50% of organizations that install the Personal App first never proceed to install the Channel App, representing a significant opportunity loss.

We also experimented with configuration options, such as setting defaultInstallScope to “team.” However, this does not alter significantly the installation dialog, so it does not resolve the issue.

OUR REQUEST:
Having a new property, or changing the behavior of Today App installation dialog window, so we can guide user to install the app in channel first.

Not a long time ago, the app installation dialog window was showing a button + dropdown with action: Add to team + Add, and that was fine for us since the CTA was really inviting user to add app to a team first.

Feel free to contact us if you have any question about this enquiry.

Looking forward to hearing from you.
Best Regards
Sang

[m365-agent-toolkit-assistant]

👋 Hi @sangdelattre,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 1 business day

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

This is a known and recurring limitation: when both personal and team scopes are present in your Teams app manifest, Teams Store installation defaults to the Personal App via the "Open" button. Even with defaultInstallScope set to "team", users aren’t clearly guided to install to a team/channel first. There is no manifest property or API to force or prioritize the team install experience currently.

Workarounds:

• Remove the personal scope from your manifest if the personal component is not critical.
• Use deep links to direct users to install your app directly into a team:

  https://teams.microsoft.com/l/app/{appId}?installAppPackage=true&context=team
  

• Enhance in-app guidance, but as you noted, this is often ineffective.

Feature request links:

• GitHub Issue #1536 (Related discussion on manifest and install experience).

Summary:
This is platform behavior—raising a feature request with Microsoft or upvoting existing ones is the best path. Sorry for the limitation!

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[microsoft-github-policy-service]

Hi @@sangdelattre! We will investigate and if we require further information we will reach out to you. Please use this link to escalate if you don't get replies in two working days.

Best regards, Teams Platform

[sayali-MSFT]

Hello @sangdelattre ,Thank you for your suggestion! To better achieve your requirements, we recommend submitting this feature request through the Teams Feedback Portal. This is the best way to ensure your idea is considered for future updates.

We appreciate your input and encourage you to share any additional thoughts!

[ingmaramzan]

Hi, I'm an engineer who's a colleague of @sangdelattre, I have tried the workaround provided by the m365-agent-toolkit assistant to use this deeplink:

https://teams.microsoft.com/l/app/{appId}?installAppPackage=true&context=team

This link does not work, and the documentation itself does not say anything about the installAppPackage or the context parameter in the deeplink, it will return "App not found" message: