Earlier this year we saw the Microsoft 365 Admin App introduced into Microsoft Teams. Now, we have the Support App. The app is designed to 'Troubleshoot problems they [as in any user] encounter while using or managing Teams, such as failed login or trouble with changing Teams backgrounds, escalate a problem to Microsoft support [admin] and track the status of service requests [also admin]'. In other words, it is bringing the support bot, ticket escalation and monitoring into what Microsoft market as its front end. In terms of time saving - considering that many admins work daily within Microsoft Teams it may shave minutes off from having to login and navigate to raise a ticket when in the flow of the work. Exposing troubleshooting to users may also work in terms of self-service. Additionally, if Power Apps have been built for Internal support, then these may also sit nicely alongside the Support App in regards of having things to hand. But it's a lot of 'may' as opposed to will. Naturally, some admins will wonder - why another app? Why split the ticket function further between the Microsoft 365 admin centre, the Teams app, the Mobile Admin App, and now the Support app. It's bringing apps to hand but there's also a conversation to be had about duping functionalities, increasing unnecessary complexity and surfacing everything everywhere. Why wasn't this surfaced in the help section of the client? Is Support too broad and vague a name and actually cause confusion? These sort of conversations I think we'll see more of in the not-too-distant future