Anonymous
My feedback
-
78 votesAnonymous
supported this idea
·
-
1,626 votesAnonymous
supported this idea
·
-
489 votesAnonymous
supported this idea
·
-
360 votesAnonymous
supported this idea
·
-
57 votesAnonymous
supported this idea
·
-
1,370 votes
This request has been reviewed and declined by the feature team.
You can continue to up vote this topic as well as leave comments. Depending on the ongoing feedback, there is always a chance a topic will be revisited based on user demand.
-Warren
Anonymous
commented
I'd guess this is linked to the inability to nest groups in 365, another non-feature that's hampering real progress with 365. Currently reminiscent of managing NT4 before AD came along. If Microsoft want customers to properly embrace cloud, they need to provide basic features that their on-premise systems do. Also, having denied to consider this three times within this thread, it would at least be a courtesy to have an explanation - Warren??
Anonymous
supported this idea
·
One of the big issues we have with further adoption of Teams is the poor support for auto attendant, group numbers and call routing. I have had to set up an an instance of Asterisk to front group numbers for routing, and it seems others are taking up similar services from their Telco providers to overcome these issues. These are features that other platforms have had forever and it shouldn't be necessary to insert an intermediate system to overcome such basic inadequacies.
As a footnote, any enhanced functionality needs to be manageable with a GUI as this is something we'd delegate to non-technical admin staff who wouldn't be proficient with powershell.