Announcing general availability of the new Microsoft Teams app for virtual desktop infrastructure

Yes, we are still seeing the "Update" button in New Teams.

At first, when I updated our "image" with the latest version of FSLogix and New Teams (24091.214.2846.1452), the "Update" button was missing.

However, a new build of New Teams has been released, 24102.2223.2870.9480.

New Teams must be constantly checking for new versions, even though we have New Teams updates disabled.  We disabled New Teams updates as per the KB.  We only want to update New Teams on our image and deploy new VMs from the image (we use VMWare Templates, no Citrix/etc. provisioning tools).

If a user clicks the "Update" button, New Teams will close but never reopens automatically.  We can reopen manually, but New Teams does not update itself.  Which is, as expected.  But if updates are disabled, then the Update button should not appear.

The multiple Duo prompts is the issue that is preventing us from migrating to New Teams.  Multiple Duo prompts in quick succession seems suspicious.  We have trained our users to report such activity.  Duo support has told us that the issue is 'on Microsoft's end' and we should contact O365 Support.  O365 support will not assist us because we are using a server OS.  The server OS team will not help us because the issue is with O365.  We need someone to fix this issue for us and provide support for the products we pay for.