01-23-2018 02:03 AM
01-23-2018 02:03 AM
Something went wrong :(
I am trying to add a connector to Teams (I've tried a few) but when I do, I get an error "Unified group access is not supported for this user.:Unified groups aren't supported."
Can't find any significant from searching online. I had a colleague try and they managed to add a connector successfully. I am also unable to manage an existing connector due to the same error.
What is this Unified Group Access thing? And how do we resolve this for an individual, given that it seems to work at the organisational level?
01-23-2018 02:31 AM
01-23-2018 08:44 AM
Are connectors enabled for the Office 365 Group that the team belongs to?
Get-UnifiedGroup MyTeam | Select ConnectorsEnabled
03-26-2018 06:49 AMSolution
So after much mulling, this boils down to an Exchange license.
We don't use Exchange 365, so nobody has licenses assigned. But "Unified groups" seems to be a security group concept that is backed by the Exchange functionality, and for some reason, Teams requires this to be able to configure connectors.
It makes absolutely no sense to me as there are no permissions to be setup for this. Feel like this is a bug in the Teams system that relies on something that isn't necessary (but possibly provides optional functionality). The error message is also, useless.
Workaround is, have an exchange license assigned to you - there is no requirement to have a mailbox or anything setup.
03-26-2018 07:42 AM
03-26-2018 08:06 AM
The likely cause is that connectors is a feature first designed for Office 365 Groups. Teams picked up connectors pretty well as they work in Groups, and that's where the license requirement is probably inherited from.
03-26-2018 09:02 AM
I don't think it is a mailbox requirement as no mailbox has been setup, just the license assigned. Tony's explanation seems the most likely. There is possibly some refactoring work required in Teams to handle default behaviour in the absence of an Exchange license.
That said, this doesn't appear to be a widely reported issue, so I assume I'm working in a rare situation where Teams is being used by not Exchange 365.