Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing the access control model from Key Vault access policies to Azure RBAC for an existing deployment of Microsoft Industrial IoT (IIoT) suites 2.9.2 #2143

Open
vikas-azureiot opened this issue Dec 19, 2023 · 1 comment
Labels
feature request New feature or request
Milestone

Comments

@vikas-azureiot
Copy link

Is your feature request related to a problem? Please describe.
Currently we installed IIoT suites 2.9.2 where script has created key vault and assigned the Key Vault access policies. However, If we change access control model from Key Vault access policies to Azure RBAC on key vault then what would be the impact on solution.

Describe the solution you'd like
we want to change access control model from Key Vault access policies to Azure RBAC on key vault which was created by IIoT 2.9.2 as this is the requirement for one of the client.

Describe alternatives you've considered
If we change access control model from Key Vault access policies to Azure RBAC so what would be the impact and how we can fix for existing solutions.

Additional context
If we want to deploy new IIoT suites where key vault created with Azure RBAC so where we need to change in IIoT suite script, Please suggest and guide.

@marcschier marcschier added this to the Future milestone Dec 19, 2023
@marcschier marcschier added the feature request New feature or request label Dec 19, 2023
@marcschier
Copy link
Collaborator

You then need to give the managed identity that is used by app service rbac permissions to the keyvault, technically it should be possible to do this using ARM.

@marcschier marcschier modified the milestones: Future, 2.9.10 Jul 5, 2024
@marcschier marcschier modified the milestones: 2.9.10, 2.9.11 Jul 24, 2024
@marcschier marcschier modified the milestones: 2.9.11, 2.9.12 Aug 7, 2024
@marcschier marcschier modified the milestones: 2.9.12, Future Sep 3, 2024
@marcschier marcschier modified the milestones: Future, 2.9.12 Sep 26, 2024
@marcschier marcschier modified the milestones: 2.9.12, 2.9.13 Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants