We've been testing the option to have the Skype for Business client automatically download Teams as part of the DownloadTeams option in the Teams Upgrade Configuration. This was previously only available via PowerShell modifying the config directly, but is now available in the Teams Admin Center UI as well.
Based on the docs, I understand the download will only occur if the user is set to TeamsOnly mode, or if the user has NotifySfbUser set to true. We are trying to test this with users who have the SfBOnlyWithNotify policy applied, which should trigger the notification in the SfB client and have Teams "downloaded" in the background. What's not clear is if this means download and install, or just download; and if just download, what triggers the install. The documents are lacking in this.
Because the documentation is lacking, we're not sure if this isn't working for us or our tenant, if our expectations are incorrect, or if our firewall/proxy/etc may be blocking something. If anyone has more information about how this should be handled... or if these features aren't fully implemented despite being surfaced in the UI now... I'd appreciate it! Thanks!
Unfortunately, no, this is still a problem for us. We opened a Premier Support ticket and we're currently waiting for more information. Initially there was a thought that the documentation was unclear/incorrect, but after further research the support engineer found the docs and our understanding of the feature are correct. We're currently waiting for a response back from the engineering team as to why it isn't working as expected. I'll be sure to update here when I learn more.
It seems the issue is with the Skype for Business client and the logic behind the app within the code doesn’t have the ability to do this and confirmed with the lead Engineer that this won’t be rolled out until Q3 (July-Sept) of 2019. Engineering is going to work on fixing our Modern Portal and documentation which states this is possible today, as it’s not.
So, the DownloadTeams option does not, in fact, work at all. Very disappointing and a huge waste of time tracking this down.
Thanks for the update. Gobsmacked it appeared in documentation as ready months ahead of when it actually is. In the end, we used PDQ Deploy to push Teams out to our org then made users "Teams Only" to disable SfB.