Deployment options
Typically, the Microsoft Teams team owner can independently install the MS Teams - Smart Connect app in their teams where needed and useful.
Who is in charge?
The Microsoft Teams team owner typically installs the MS Teams - Smart Connect app for their teams or for specific / all users.
If not possible, the Microsoft Teams admin needs to take action (see: Deployment Teams app). They install the app centrally or for specific teams.
In some cases, the Microsoft admin has to change settings to allow the installation of third party apps for their team owners (see: Exception: environment restrictions).
Anchor | ||||
---|---|---|---|---|
|
📌 Follow instructions below if:
the team owner cannot install (or is not allowed to install) the app on their own
the Microsoft Teams admin wants to deploy the app centrally for teams
Note |
---|
In case If the app is not allowed permitted by default, it might also be necessary to allow the app first you may need to grant permission for the app to function properly. (see: Exception: environment restrictions). |
Deploy app to (all/specific) users
📌 Follow instructions below if:
the team owner cannot install (or is not allowed to install) the app for the users
the Microsoft Teams admin wants to deploy the app centrally for users
Anchor | ||||
---|---|---|---|---|
|
By default, the option for team owners to independently install applications is typically enabled. If this is not the case, action must be taken by your MS 365 administrator or MS Teams administrator.
In some cases, there may be environments where the owner of a Microsoft Teams team is restricted from installing apps independently for their teams or users.
To enable the installation, please follow the steps outlined below.
Note |
---|
Please note: It may take up to 24 hours for the app to be visible for users in Teams. |
Heads up
In case If you see this the error message below, it usually works and the app should be installed. There currently seems to be install without issue. It seems there is a bug on the Microsoft side regarding thisMicrosoft's end causing this problem.