Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Enhancement: extend teams app install to support installing personal apps
See original GitHub issueCurrently the teams app install command only supports installing apps to teams. We should extend it to support installing personal apps. This would be beneficial especially for developers who want to quickly deploy the app they’re working on Teams to preview it. To indicate that you want to install a personal app, use a newly added --personal option.
Requires the TeamsAppInstallation.ReadWriteForUser scope
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Extend a Teams personal tab across Microsoft 365 app
From Visual Studio Code, open the command palette ( Ctrl+Shift+P ), type Teams: Create a new Teams app . Select Create a new...
Read more >Set up your dev environment for extending Teams apps ...
Sign in to Teams admin center with your test tenant credentials. · Go to Teams apps > Manage apps. · At the top...
Read more >Add an app to Microsoft Teams
Learn how to add an app, bot, tab, connector, or messaging extension to Microsoft Teams.
Read more >Understand Microsoft Teams apps and their capabilities
Learn about apps and decide what apps to allow in Teams based on your organization's profile and business requirements.
Read more >Embed an app in Teams - Power Apps - Microsoft Learn
Add to Teams using the web player · Go to Power Apps > Apps > select the app to launch in a new...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m not against adding
--personalto explicitly indicate that it’s a personal app and which could function as a guardrail in case we allow installing apps by name and both the ID and name become optional which could lead to undesired side-effects. Thank you for bringing it up. Good call 👍I’ve updated the spec to reflect this.
If you misspell
teamId, CLI would throw an error saying that you’re using an unknown option. If you misspell its value, it would fail because it wouldn’t find the team with the specified ID. I understand what you’re getting at. I don’t think we have this risk with the current guardrails, but perhaps we should make it explicit like we do with tenant-wide deployment for SPFx apps.