Anyone else experiencing extreme slowness when provisioning almost anything in teams voice?
Our setup is Hybrid with Direct routing. Roughly 3500 total users, 3000 of them on-prem voice in SfB, another 500 have made the journey to Teams voice.
We've found that moving users from SfB to Teams an excruciating slow one. The commands 'take' instantly - but the application of the commands take forever. For instance - I can do a move of a user from on-prem to cloud, and it shows the user in-cloud reasonably within a few moments. However - it takes (seemingly) minimal of 4-6 hours, but usually closer to 20-22 hours before a user gets policy, a dial-pad, the ability to call etc. (Receiving calls is usually near instant - but the ability to get a dial-pad takes forever). Creating a new call queue (Resource account, queue, adding a # etc) takes similar times. We even tried to pre-build accounts (unassign a phone # and assign it later) and even assigning a fake # and flipping it during a migration window. Both of which caused outages between 12-20 hours for those call queues.
Queue memberships are done via security group on prem (AD connect to Azure, etc). Changing group membership takes 4+ hours (minimum) and worst I've had is 14+ hours. I can force a delta sync, and see it in Azure AD near instantly, but before Teams picks it up or 'applies' the change is forever.
Also - Hybrid routing (Audiocodes SBC) there's a substantial lag in answering calls (5-10 seconds regularly). We're not using Direct Media which may make this better; but driving our users nuts (we didn't/don't have this issue in SfB on premise before).
Also on the call queues - (not a slowness issue, but just another issue reporting): SfB firmware phones (3pip) cannot answer a cloud call queue (yet it rings) - it must be answered by a Teams Client (3pip phones can answer direct calls just fine). Also - any response group (on premise) if it includes any 'Teams' user - the calls to queue instantly get picked up by the voicemail of that Teams user. However - if you have a Teams call queue, it appears you can have an on-premise SfB user answer fine.
Teams as a single-line handset seems to work well (direct calls in/out - once you move past the delay in provisioning) - but any advanced feature and it seems to completely fall apart. Everything else about Teams is fantastic - I'm a huge advocate for Teams; but this delay/provisioning is killing us.
Last note: We did bring up the slowness with MSFT Premier (which we talked directly to product group); and the answer was "Well we met a 24 hour SLA" which is complete b.s. Try troubleshooting something with your end users - make a change. Take a guess if it will take effect within 2 hours or 20 hours, try again - and only then to realize you need one more change and rinse/repeat.
