@Connor Sullivan
Thank you for your post and I apologize for the delayed response!
When it comes to restricting users from deploying resources, you can definitely leverage Azure role-based access control (Azure RBAC) to manage who has access to Azure resources, what they can do with those resources (i.e. create/deploy, deleted, view, etc.), and what areas they have access to. Azure RBAC is an authorization system built on Azure Resource Manager that provides fine-grained access management of Azure resources.
Here are some examples of what you can do with Azure RBAC:
- Allow one user to manage virtual machines in a subscription and another user to manage virtual networks
- Allow a DBA group to manage SQL databases in a subscription
- Allow a user to manage all resources in a resource group, such as virtual machines, websites, and subnets
- Allow an application to access all resources in a resource group
If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.
----------
Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.