You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resource groups are very restrictive and although they might be the answer for simple projects, there are not the solution for complex projects. Particularly, they don't play nicely with Service Principals and Application Principals which many services require to themselves create resource. For example, CycleCloud is actually an orchestrator which creates resource itself. It needs to be given a Service Principal with the correct access roles to dynamically spin-up resources.
The most flexible approach is to allocate subscriptions at the appropriate level within the organisation. This can be used in conjunction with Education Portal to manage allocating resource at a school/ course/ module level.
Should research groups/ RSE teams be given allocated a subscription or a resource group?
Are there advantages or disadvantages with each approach?
The text was updated successfully, but these errors were encountered: