Deployment without Administrative rights on the Azure subscription

[microsoft]

Deployment without Administrative rights on the Azure subscription

[wisbech]

Thank you for the response @dayland.

I do understand it is not possible to have lower level access due to these RBAC requirements for Azure.

My observation is that it does not really accelerate adoption much with such restrictions in deployment hence it limits the number of people significantly that can actually deploy this codebase in most public sector companies.

I will most likely go for a different deployment model using the Azure openai infrastructure and have the application layer and vector store as a kubernetes application instead.

[dayland]

The minimum access levels required are "Contributor" and "User Access Administrator". The overall BICEP deployment is a "Subscription" level deployment but could be altered to be a "Resource Group" level deployment in your fork. However, we do need to create Service Principals, App Registrations and make RBAC assignments at both the resource group and individual resources levels. The ability to make RBAC assignments are not included in the "Contributor" role thus the need for "User Access Administrator".

[dayland]

@wisbech , I intend to close this ticket as we do not plan to change the required permissions at this time. If you have any objections please let me know or this ticket will be closed in 48 hours.

[wisbech]

@wisbech , I intend to close this ticket as we do not plan to change the required permissions at this time. If you have any objections please let me know or this ticket will be closed in 48 hours.

No objections on this one - it was an aha requirement and is described in the README.md

[champski]

Hi,
How exactly what do I need to do for it to be a "Resource Group" level deployment?
Kind Regards