Teaming in Azure Stack HCI

I understand your need for a GUI in Windows Server, that makes sense, but all of this is exposed in Windows Admin Center, and you can create your Switch Embedded Teaming in Admin Center quite easily in the Cluster Creation Wizard. So while you are disappointed it is not exposed in the Server Manager, I have to ask, why are you using that in the first place. Your Hyper-V hosts should be running Server Core edition of Windows Server, or better yet be running Azure Stack HCI OS on your nodes, which doesn't even have a Desktop Experience. You can also use Virtual Machine Manager to create the Switch Embedded Team, and I have a blog article out there on that exact process. The point is, this process has been around since 2016 and has only become better, the fact that there is no GUI method of management built into the OS really tells you that you should be running your Hyper-V hosts as Server Core, its the default installation. If you are not comfortable with Core, well you have Windows Admin Center as a primary method of Management which gives you the PowerShell processes it is using.

MilitantPoet  you mention that you would assume creating a SET Team would be in the same place as creating a Team before in Server Manager, well I am sure you know that an LBFO team and a SET team are NOT the same thing at all. A NetLBFO team is an OS function and creates a Team of the NICs, where a Switch Embedded Team is a Hyper-V feature, and you create a Virtual Switch which contains your Physical NICs as the uplinks with a Load Balancing setting of Switch Independent, the documentation is clear the LACP is no longer supported. 

I would be happy to help you understand how to deploy Switch Embedded Teams both in Admin Center or in Powershell, the process is actually quite easy and as we move more toward a Cloud friendly world, either Private or Public Cloud we need to embrace CLI methods of deployment for speed, consistency and compliance methods. I would encourage you to challenge yourself to do things "outside of the GUI" and always via CLI methods, you will find it slow at first but will gain speed and efficiency with each day.