Native Teams Federation

Federation was always a really useful feature of Lync, then Skype for Business and now Teams - the ability to see presence and be able to chat and call a contact outside of your business. In fact, for quite some years now, the vast majority of people I work with are using Skype for Business (and now Teams) and I very, very rarely get an actual work phone call.

If you've got used to having features such as emoji, GIFs, stickers and rich text in your internal Teams chats, you'll be glad to hear that Microsoft have announced that native Teams federation is coming soon. Ever since Teams was originally launched, federation has been working via the original Skype for Business Online federation gateway, and hence subject to it's limitations, but Microsoft always said that they intended to move to a native Teams federation gateway in due course.

You'll be able to tell when it's live when you see the additional feature buttons just below the new message window. But as the feature will be rolled out gradually, both tenants must have received the feature for you to see extra options when initiating a chat with a contact - Microsoft say they'll "be gradually rolling this out to all customers starting end of July, and the roll out will be completed worldwide by the end of August." My own tenant does appear to have been 'upgraded' already, as one of my contacts does have the options, but none of the others do, as yet.

How do I configure federation in Teams?

There's not much to do - by default it's already setup, and is setup as what was known in Skype for Business as 'Open federation' - so anyone can contact you, and you can contact anyone (if they are also Open). The other options are to block specific domains, or to configure federation as 'Closed' - that is, only allowing specific domains to be able to contact your users. Microsoft's documentation on how to configure federation is here.


The Admin portal has changed some wording recently on this page, and it now clearly explains that the second button sets communication with Skype (i.e. 'Skype Consumer') but only for Skype for Business users in your tenant - currently, Teams users cannot communicate with Skype users.

One really important point to note if you're currently running Skype for Business in hybrid mode (where you still have on-prem Skype for Business servers as well as the ability to have users in the cloud) is that you must make sure that your federation settings are consistent between your on-prem setup and the cloud. If you currently use Closed federation, for example, you'll need to make sure that the list of domains is the same between on-prem and cloud.

What's Missing?

  • As noted, there's currently no communication between Teams and Skype Consumer. Microsoft have announced that this will be launched "in the first quarter of calendar year 2020".
  • If you're communicating with someone who is still using Skype for Business, you won't, of course, get the additional Teams-only features, but you also won't be able to share your desktop - to do that, you'll need to setup a meeting.
  • The biggest issue which may concern some customers is that currently there isn't a way to setup any policies regarding federation: for example, you can't stop file transfer. Some organisations might be happy to allow Giphys internally, but not externally - but that's currently not possible.

Update - December 10th 2019

This is, at long last, gradually working for me, anyway. Both parties need to be running in Teams-only mode, and at some, random point, you'll see a message like this one at the bottom of a chat:


When you click on the link, a completely new chat starts, and it's got all the features of a Native Teams federation chat:


There doesn't seem to be any way to speed up this 'switching' process, and you can find that you have Native chat functionality between yourself and one person in a federated tenant, but not another person. There's a very brief Microsoft write-up about the process here.

Comments

Post a Comment

Popular posts from this blog

Microsoft Whiteboard and Teams

Image
If you've tried to use the preview Whiteboard in Teams , you might have been a bit frustrated by its limitations. Currently, you can 'ink' - but that's about it. If your handwriting (with a mouse, anyway....) is as bad as mine, that's not great if you want to put text on your whiteboard. There also doesn't appear to be a way, from Teams, to export your creation. But there is a (relatively) easy workaround to get more functionality, it is actually documented in the Microsoft article Use Whiteboard in Microsoft Teams . Step 1 - install the Windows 10 Microsoft Whiteboard app from the Microsoft Store. Step 2 - Once it's installed, run the Whiteboard app and sign in with your Office 365 credentials, then close Whiteboard. Step 3 - Start your Teams meeting, click on the Share button and share a whiteboard (sometimes that menu item isn't immediately visible - scroll to the far right). Step 4 - Open the Windows 10 Whiteboard app, and you'll
Read more

Skype to Teams - which route?

Image
If you're currently using Skype for Business in your organisation, you have almost certainly started to think about how you might start to implement Microsoft Teams, and indeed, eventually, migrate fully to Teams. The question is, what's the best approach? Inevitably, there is no one answer, as every organisation is different. Microsoft's own guidance is here , and continues to evolve as they work with more and more organisations. Having worked with a customer on this topic recently, I've tried to put down some of the pros and cons of each approach. Straight-to-Teams This is my own name for this approach, and it's not covered in the Microsoft guidance, but I've included it for completeness. Pro No messing about with coexistence - users go straight from Skype for Business one day, to using Teams the next. Cons Large change brings the potential for technical risks. Users have to get used to a lot of change all at once. Realistically, you'
Read more

Microsoft Licensing for Small Businesses

Image
The other week, I was looking into using Teams as a phone system for a potential small business customer - and spotted a major problem. But it's not a technical one, it's a licensing (or commercial) one: if you're licensed with one of the Small Business Plans (for less than 300 users), you cannot add a Phone System licence. To be able to add a Phone System licence, you need to have at least an 'E3' licence, which really surprised me. I spent a little while trying to tabulate the relevant features of a number of different licence plans, and produced this table to help try to compare and understand the options. Some points: I've not listed every single product and feature, just what I thought the ones which would be most relevant to a small business customer. I've translated the 'features' into actual 'products' to make it easier for techies to understand. All pricing is standard, with no discounts applied, as of July 2019 in GBP
Read more