Subscriptions & Resource Groups are one of the most important aspects when looking at how to deliver/provide cloud resources to your staff/students
Here are some best practice principles around providing Azure at your institution.
1. Create new major subscriptions to hold resource groups, according to broad categories
2. Used Role Based Access Control
Here are some example of how subscriptions can be associated to Azure Resource Groups , which then can be used to enforce access to Azure Cloud Services based on Azure Role Based access control - https://docs.microsoft.com/en-us/azure/active-directory/role-based-access-built-in-roles
Resource groups are a new concept in the Azure Portal http://portal.azure.com
We think of them as "lifecycle boundaries," because when resources share a resource group, their lifecycles (from create, to update, to delete) are managed in an integrated way. Use resource groups to collect and manage all your application resources. Link resources across resource groups, share resources across lifecycle boundaries, and manage costs. View, monitor, and track your usage and billing for all the resources your application uses. New visuals show you every resource in the group, including any resources that are linked across groups.
https://docs.microsoft.com/en-gb/azure/azure-resource-manager/resource-group-portal
In terms of structure and management these groups can be built around the institutions Azure Active Directory or Office365 tenant to ensure only users of appropriate groups and team have access to the necessary resources.
Here is a an example of the types of users and role which they may undertake,
if your interested in learning more about Azure subscriptions in your institution please get in touch and we can introduce you to your institutions Microsoft account manager
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.