If we currently want to be able to allow guest invitations for Teams we need to configure Azure AD as follows:
Members can invite: Yes

https://docs.microsoft.com/en-us/microsoftteams/teams-dependencies

With that setting all tenant users are eligible to invite guests to the tenant. So how can we achieve to limit the guest invitation functionality to certain users?

We previously had configured the following:
Members can invite must be set to: No
Admins and users in the guest inviter role can invite: Yes

This resulted in being unable to add any guests to Teams even if the user was holding the guest inviter role. Inviting guests to Office 365 groups however was possible.

Hello. We have been trying to get our university community to adopt Teams as a collaboration suite. We run into the problem that external/guest Team users have to switch to our organization/tenant to take part in the relevant Teams in order to collaborate with us. The same also applies with our users participating as guests in other organisations. We are getting feedback from external partners, consultants and even from some of our own faculties that this not the best user experience. We also get comments that other tools on the market (even Microsoft skype for business) handle it in a more elegant and user friendly fashion. We are aware that Teams is relatively a new Microsoft offering, but could we at least ask to make Teams work more like Skype for business in that regard? or handle federation with other entities a different way?

best regards.

Over the years with SfB, I have seen users struggle when joining Skype audio conferences. Inevitably, they join both by phone and computer, causing feedback. I think the join process could be made much more intuitive for Teams by making just a few small changes to the meeting join workflow and making the process identical for both guests and hosts, using the client, browser or app.

When a user joins via the web or client, first present an option of which audio to join. I know this was available to a certain extent in SfB… but the verbiage can be confusing (more on this below). It needs to be much more plain and obvious.

1. Join using computer


2. Call Me / Dial Out


3. Dial In (then display the dial-in information)


4. Don’t join audio / I already dialed in

Regarding the confusing verbiage, I have had users dial in using the invite, then select the “Use Skype for Business (full audio and video experience)” option simply because they thought they needed to select that option to see the screen share.

Obviously, for any of the phone dial in options to work, they'll need to have the audio conference license applied. The meeting join workflow should adapt to accommodate those who do not have an audio conference license and omit all options to dial in/out.

We would like to see some kind of configuration setting for guest access to expire after a specified period of time. Often times teams change and reorganize in a way that it may not be clear if a guest user still should have access. We work with contractors and consultants for a specified period of time and it would be beneficial for us to grant access to a contractor who might only be working with us for 6 months or so. When that contract is up then all access to Teams or any shared files is revoked. This would help keep our information secure without solely relying on team admins/owners to do membership cleanup.