Install Microsoft Teams plugin
Creating a Teams App and app configuration
In order to use Microsoft Teams, an app will be need to be created to allow access to Microsoft Teams.
Note Teams is still in beta, so it is possible the setup and permissions required will change once it is out of beta.
- Your company must have Azure
- The user account that creates the app must be present in the Azure AD directory of your company and have the rights to create apps (this is possible by default unless limited by an admin)
- A global admin will have to go to an admin consent url in order to allow accounts of this Azure AD directory to use it, since Teams requires permissions normally reserved for admins. By consenting a global admin allow regular users to have these permissions in the app.
- Go to https://apps.dev.microsoft.com/ and login with a work account. This requires that your company has Azure. Any account present in your Azure will do (so it does not need to be an admin).
- You will end up on the application registration portal. If not, go to this url: https://apps.dev.microsoft.com/#/appList. Choose add an app at Converged Applications.
- This will take you to the register app screen, choose a name for your app, then choose create.
- You will now see app settings screen. You will also see a message to which Azure AD Tenant the app belongs. Check that this is the correct Azure environment. You will also the see the application id, which we will use in the admin consent url and in the attendant to access the app. The app is at this point also added to your application list under converged applications. Clicking on the app there will take you to the same settings screen.
- Go to platform and choose Add Platform. Choose Native Application. This will mark your app useable as a native application. The data generated afterwards can be left alone, we do not need to alter any of this.
- Under Graph Permissions we need to add two delegated permissions. Delegated permissions are meant for apps that require the user to login themselves. By default User.Read is already set, you can remove this setting since we will use a higher level permission of this. The two permissions you need to add are User.Read.All (In order to have access to the teams you are part of) and Directory.Read.All (In order to see the members of each team you are part of). Both these permissions require the admin consent of a global admin before a non-global admin user can access this data.
- The last thing that we need to do is to add to the app is the homepage url. This works as the return url in the app. This does not have to be an existing url, the default is http://localhost. The return url in the attendant will have to match the url you set here.
- Finally, go to the bottom of the page and click save to update all the settings. In order to give admin consent you can use the link below, replace clientid marked in red with the id of your application. You can also do this from the settings page of the teams plugin in the attendant. Login as a global admin and accept the permissions given here. After this is done regular users can also make use of the Teams App. https://login.microsoftonline.com/common/adminconsent?client_id=[clientid]&state=12345&redirect_uri=http://localhost.
Installation & folders
The installation folder is default set to “C:\Program Files (x86)\Anywhere365 Attendant\” but can be changed on installation. All the plugins will be installed in the folder called plugins, if this is not present when you install a plugin it will be created.
The default installation location should be: “C:\Program Files (x86)\Anywhere365 Attendant\plugins\Wsp.Anywhere365.TeamsPlugin”. After installation this folder will be present.
Settings in the attendant
When opening the attendant click on the bottom right circle to open the settings tab. Then click on plugins in the right bar. Then select the Teams Plugin to open the settings page where you can configure the settings for the Teams Plugin.
There are three settings in the attendant that are configurable,. If you stick to the default settings there is only one setting that is required, the clientid.
Client Id: The client id of the teams app.
Authority Url: The authority url is MS’ authority url that is required to make connection to the app. By default this is already set to https://login.microsoftonline.com/common/. You can change the common with the name of your azure tenant if you wish to limit app access to only those present in your azure ad.
Return Url: The return url is specified in the settings of your app. See the create app document for further information. The return url is only a formality and does not have to exist, but does need to match the url specified in the setting of your app. By default this is set to http://localhost.
Apart from the settings there are also two buttons.
Admin Consent Url: opens an url in your default browser to the admin consent url required for the app, in case this has not yet been done. This requires a global admin user account in Azure to consent to. The url will only be opened if all three setting contains a value, since all three are required in the admin consent url.
Login User: Logs off and on a user. This is only required if you wish to log in with a different user or if a mistake occurred when you logged into the app. The app will also pop up when you save the settings, so you do not need to use this button under normal circumstances.
When you are done with setting the settings either press the save or cancel option to save / cancel your settings. Attempting to leave the settings tab will also prompt the save / cancellation option
Assuming a client id has been filled in, the Teams App you created will pop up with the request that you log into it. Put in your user account and password and the Teams plugin will work. If you have both a school / work and personal account under this user it will ask you to make a choice which one should be used. This should be the school / work account. If this is the first time you log into the app it will also ask you to allow the required permissions to run the Teams App.
Accept these permissions. Like said before, should there be a reason you cannot log in the app, make the necessary changes and login via the login button on the settings page. Below is a screen of the app. Microsoft will alter how the app screen looks in 2018, so if the screen looks different do not be alarmed.
We will now go into detail about the look and possibilities of the plugin. On the right side of the attendant click the following icon to open the plugin
The teams plugin is meant for transferring. You can transfer to all members shown in the team, assuming they have a phone number / skype for businessSkype for Business (formerly Microsoft Office Communicator and Microsoft Lync) is an instant-messaging client used by Anywhere365. In order to use SFB, a Microsoft Skype for Business Server is required. Skype for Business is enterprise software; compared to Skype, it has different features that target businesses. account known by Microsoft Teams.
The teams are loaded one by one, so depending on size of the teams it might take a few seconds before all are visible. By selecting the team all members beneath it are shown. There is also a search bar for each team if you wish to look for specific members in the event the team is large. If a call is made this will appear above the tabs. Click on the picture of the person that is calling and drag that to the team member you wish to transfer to.
Did you find this page helpful?
Sorry about that
Why wasn't this helpful? (check all that apply)
Thank you for your feedback.
Want to tell us more?
Email your feedback to our documentation team.
Thanks for taking the time to give us some feedback.