Home

Error adding contact to Group

%3CLINGO-SUB%20id%3D%22lingo-sub-668484%22%20slang%3D%22en-US%22%3EError%20adding%20contact%20to%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-668484%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20currently%20having%20issues%20placing%20internal%20contacts%20into%20contact%20groups%20within%20our%20free%20version%20of%20Teams.%20We%20get%20the%20error%3A%20%22%3CSPAN%3EWe%20couldn't%20add%20a%20buddy%20to%20the%20group.%22%20I%20have%20encountered%20this%20error%20on%20both%20the%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fteams.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fteams.microsoft.com%3C%2FA%3E%26nbsp%3Bwebsite%20and%20on%20multiple%20locally%20installed%20applications.%20I%20have%20verified%20that%20each%20are%20also%20using%20the%20latest%20version%20of%20the%20software.%20Is%20there%20a%20way%20to%20correct%20this%20issue%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-668484%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-668500%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20adding%20contact%20to%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-668500%22%20slang%3D%22en-US%22%3EHmm%2C%20we%20saw%20this%20issue%20here%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FError-quot-We-coudn-t-add-the-buddy-quot-while-adding-internal%2Ftd-p%2F394051%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FError-quot-We-coudn-t-add-the-buddy-quot-while-adding-internal%2Ftd-p%2F394051%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20Deepak%20didn%E2%80%99t%20confirm%20a%20resolution.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F224928%22%20target%3D%22_blank%22%3E%40Deepak%20Mehta%3C%2FA%3E%2C%20did%20you%20get%20a%20resolution%20for%20this%20through%20raising%20to%20support%3F%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-812297%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20adding%20contact%20to%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-812297%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20recently%20had%20a%20ticket%20open%20with%20Microsoft%20for%20this%20exact%20issue%20and%20we%20came%20across%20a%20fix.%20It%20seems%20like%20the%20issue%20is%20to%20do%20with%20the%20mail%20attribute%20not%20being%20filled%20for%20users%2C%20this%20happens%20if%20you%20do%20not%20have%20an%20Exchange%20license%20assigned.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20still%20using%20an%20on-prem%20mail%20solution%2C%20so%20we%20aren't%20using%20O365%20for%20Exchange.%20However%2C%20assigning%20a%20O365%20E3%2FE5%20trial%20license%20to%20the%20user%20(which%20should%20include%20an%20Exchange%20license)%20fills%20in%20the%20mail%20attribute%20for%20the%20user.%20You%20can%20use%20the%20graph%20explorer%20to%20query%20a%20user's%20attributes%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fgraph%2Fgraph-explorer%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fgraph%2Fgraph-explorer%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUse%20a%20GET%20request%2C%20beta%2C%20and%20query%20the%20user%20with%20the%20following%3A%20%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%2Fbeta%2Fusers%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%2Fbeta%2Fusers%2F%3C%2FA%3E%3CSTRONG%3Eemailaddresshere%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20also%20found%20that%20removing%20the%20trial%20license%20after%20a%20few%20hours%20keeps%20the%20mail%20attribute%20filled%2C%20which%20in%20turn%20should%20resolve%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3CP%3EJames%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We are currently having issues placing internal contacts into contact groups within our free version of Teams. We get the error: "We couldn't add a buddy to the group." I have encountered this error on both the http://teams.microsoft.com website and on multiple locally installed applications. I have verified that each are also using the latest version of the software. Is there a way to correct this issue?

2 Replies
Highlighted
Hmm, we saw this issue here

https://techcommunity.microsoft.com/t5/Microsoft-Teams/Error-quot-We-coudn-t-add-the-buddy-quot-whil...

But Deepak didn’t confirm a resolution. @Deepak Mehta, did you get a resolution for this through raising to support?

Best, Chris
Highlighted

Hi all,

 

I've recently had a ticket open with Microsoft for this exact issue and we came across a fix. It seems like the issue is to do with the mail attribute not being filled for users, this happens if you do not have an Exchange license assigned.

 

We're still using an on-prem mail solution, so we aren't using O365 for Exchange. However, assigning a O365 E3/E5 trial license to the user (which should include an Exchange license) fills in the mail attribute for the user. You can use the graph explorer to query a user's attributes:

 

https://developer.microsoft.com/en-us/graph/graph-explorer

 

Use a GET request, beta, and query the user with the following: https://graph.microsoft.com/beta/users/emailaddresshere

 

We've also found that removing the trial license after a few hours keeps the mail attribute filled, which in turn should resolve this.

 

Cheers

James