Had a strange issue today, and looking into it, found even more strange issues, particular revolving around Teams finally providing the admin access to a user’s calling settings.
Continue reading “Teams Calling Settings Not Consistent”Teams Direct Routing – No Ringtone when Transferring from AutoAttendant
One thing I noticed is that when setting up voicemail in Teams, if you set up an autoattendant to transfer directly to an individual, there’s no “ringing” tone. One would expect this to just be a standard thing when transferring anywhere, so how can we fix it?
Continue reading “Teams Direct Routing – No Ringtone when Transferring from AutoAttendant”Microsoft Teams prompting for Sign-In Daily (Bad SSO) after Endpoint Manager/Intune Registration
In doing some searching for this issue, I see a handful of people searching for the issue with varying degrees of successful answers. Since I ran into this recently, I figured I’d post up my own experience with fixing this.
Continue reading “Microsoft Teams prompting for Sign-In Daily (Bad SSO) after Endpoint Manager/Intune Registration”Microsoft Teams Direct Routing – SIP 404 Not Found
My first experience with switching a user from an existing calling plan in Microsoft Teams to Direct Routing did not go as planned. Not at all. I’ll walk you through what I did…and what I did wrong, as googling this particular error didn’t really lead me to the answer!
I seemingly had everything right – I followed the Configure Direct Routing documents to the T, and to switch the user over, I removed their calling plan, and then used powershell to add the ONPREMURI property (aka the user’s phone number) in E.164 format with the tel: prefix to the Teams user. I have the SBC all set up and outbound calls are working fine, yet inbound calls don’t seem to be working, as I’m getting a “404 Not Found” reply to the SBC invites in the SIP traces.
Continue reading “Microsoft Teams Direct Routing – SIP 404 Not Found”Microsoft Teams Voice – Call Queue Troubleshooting
Had a funky issue to work through the other day; I set up a basic call queue with 2 attendants in Microsoft Teams voice. For this queue I used “serial” routing so that it followed a specific order for the attendants. Oddly, the first person couldn’t answer the phone.
Continue reading “Microsoft Teams Voice – Call Queue Troubleshooting”Microsoft Teams and the Missing Teams Meeting Outlook Addin
With the ongoing pandemic, the last thing we want is more software glitches to deal with. In my case, I had to set up a number of new systems for new users, and naturally on the last few, just happened to notice that in Outlook, the Teams addin didn’t seem to be loading.
Notably, I didn’t see the big purple “New Teams Meeting” button under the Calendar function in Outlook.
Office365: Teams Mode is configurable per-user
Today I learned (thanks to Reddit) that although my Office365 tenant is still set to “islands” mode, the setting is actually applied per-user with each user actually defaulted to tenant global setting). You can enable any individual user for Teams-only mode, and even then, the setting can be reverted if need be, so it’s not permanent like most people tend to think.
It seems that amongst the settings, each one simply varies of the amount of work “Skype” will do, with “Teams-only” being the only one that truly switches things over to Teams. Even with both Skype and Teams installed, with the Tenant/User in “Islands” mode, calls get routed to Skype by default, including the mobile apps. You need to use Teams-Only mode to have Teams actually accept calls.
I also found some really interesting notification rules in the mobile app I don’t think I’ve seen before (Quiet Time and Quiet Days), and in addition, Teams -FINALLY- has a secondary ringer option so you can actually hear calls when you have a usb receiver or headset plugged in. (This may not be true for mac users yet, at least according to a couple other Reddit posts I’ve seen recently.)
Anyhow, it seems good things continue to come for Teams, and I can only imagine the onslaught of new features that’ll be announced at Ignite, I just hope they all work!
Powershell – Getting Group Membership in Office365
As I’m trying to clean up some accounts, I found that it’s -not easy- to simply get a list of all the groups a user is a member of in powershell, at least not like the one that displays in the admin portal. In doing some hunting (admittedly, not a lot of hunting) I came across this site that has just about what I was looking for, but I will warn you that the one-liners provided are not efficient – they have to populate the members of all groups, therefore if you have a LARGE directory, these may take a very long time to run, and be data-intensive. If you’re an SMB or SME with only a couple hundred users, they should be OK.
The problem was, it didn’t work! It looked good, but the variable it stored the results in was empty. After a quick review I realized the problem; the $mailbox.Alias at the end of the scripts should have been $mailbox.Name, since the alias will never match the name shown in the group membership. Once I changed that, it worked as it should:
$Office365GroupsMember = Get-UnifiedGroup | where { (Get-UnifiedGroupLinks $_.Alias -LinkType Members | foreach {$_.name}) -contains $mailbox.Name}
However…this only works for “Office365” Groups, and not all Office365 group types, that may include groups sync’ed from Active Directory/DirSync, like distribution lists and so on. I took the one-liner from that site, and modified it slightly to use “get-msolgroup” rather than get-unifiedgroup, which worked as it should.
$UserEmail= "someperson@somecompany.com"
$Mailbox = Get-Mailbox | Where {$_.PrimarySmtpAddress -eq $UserEmail}
Get-msolGroup | where { (Get-msolGroupmember -GroupObjectId $_.objectid | foreach {$_.displayname}) -contains $mailbox.name}
From there you can pipe the output of that command into others, like remove-msolgroupmembership (although it needs the member objectid which is odd), or store it in a variable. Keep in mind you may want to filter group types as well, as I’m not sure you can remove a user from an Office365 group that was added/created as part of a Teams teams.
Last but not least, see these commands to do simliar roles for Active Directory:
get-adprincipalgroupmembership
remove-adprincipalgroupmembership
I figured this might help someone out, and kudos to the other page for having a one-liner that worked as the basis for this!