use an AD group. For example, developers could have access to a development cloud.
My guidance changes when good processes are not in place to add users to groups, and
it’s beyond the control of the team implementing the private cloud to fix it or effect
change. In those cases, I may lean toward adding users directly into user roles within
SCVMM, which can be automated through PowerShell and can cut out potentially
large delays associated with adding the user to an AD group. Add the users and/or
groups and click Next.
On the next page, you select the clouds to which the user roles apply. Note there are
no host groups shown, only clouds. With System Center Virtual Machine Manager
self-service access is via clouds or nothing. Select the clouds and click Next.
Next you set the quotas for the user role. Remember, when creating the actual cloud,
you set the capacity. Now you are setting the quotas for this specific user role in the
cloud as well as the quotas of each user within the user role. Note that you may have
multiple Self-Service user roles for a single cloud with different quotas and different
actions available. In Figure 9.12, I have set an unlimited quota for the role, giving it
full access to the cloud, but each user has far smaller limits. Make your
configurations, and click Next.
Figure 9.12 Setting the quotas for a specific tenant
The next step is adding the resources that should be available to the role, such as
virtual machine templates, hardware profiles, service templates, and so on. These
resources are what will be available when the users of this role create virtual
machines, so make sure that the right templates are available for them. Additionally,
you can specify a location for user role data that is shared between all members of the