WAC is a great server management tool that, while offering tons of functionality, is lacking one essential feature: proper role based access control. There is almost no granularity between "Reader" and "Fulll Admin", save for the "Hyper-V Manager" role which, again, does not offer any granularity in terms of VMs, networks or storage locations that are allowed to a certain user. Features other than Hyper-V completely lack any access granularity.

In this session, we will explore the possibilities and the challenges of providing RBAC to WAC, the limits of what can be done without breaking stuff and ways to effectively cope with WAC updates and extensions.