External connectivity not working for older Azure AD users

Hello everyone, As title says we have issues with external connectivity for Azure AD users. Some time ago we switched to MS Teams, and to make user life a bit easier we integrated on-prem AD ...

microsoft teams

James1
Sep 06, 2019
Hello and thanks to everyone that contributed to this post.

I managed to find the issue. It was indeed related to previously used Skype for Business. When a SFB user is created, a certain attributes are added. And those stay until they change (for example if user migration are used ((didnt work for us since SFB servers were deleted)) or until they are removed.

What happened was there was a conflict with those attributes. Teams "thought" that we still use SFB due to these previous SFB msRTC attributes. Once removed after a while External connectivity appeared.

Rob Ellis

Bronze Contributor

Sep 02, 2019

Do the AD synced users have the same UPN suffix as cloud-only users? e.g. are all users signing into 365 with username@company.com - or do the synced users have username@company.onmicrosoft.com userids?

James1
Brass Contributor
Sep 02, 2019
Hello Rob Ellis , thank you for the reply.

Synced users show up with onmicrosoft.com. After they show up we changed the suffix and add the licenses.
We made a test account on whom we left the default suffix, it does not work aswell.
- Rob Ellis
  Bronze Contributor
  Sep 02, 2019
  I assume you changed the suffix in on-premises AD, then waited for another sync?
  - James1
    Brass Contributor
    Sep 02, 2019
    Rob Ellis Suffix on our AD is .local, we left it like that. Should that be changed aswell?

Forum Discussion

External connectivity not working for older Azure AD users

Resources