Portal UI Format about avdaccelerator HOT 2 CLOSED

I've made a lot of progress here, and it seems to be coming together. UI testing can be viewed here.

I am going to move the KV selector and Image customizations out of the initial deployment UI. There are a couple of reasons for this.

1. If we allow a user to select an existing Key Vault the deployment may not work. This is because we create a user assigned identity to access the Key Vault, and an existing vault will not have this identity with proper IAM or vault access policies. An end user selecting one of these vaults may not have IAM permissions to modify the existing vault.
2. We want to create out own Key Vault to store VM secrets (domain join, local admin password, etc.)

What I propose we do is just create the Key Vault as part of the initial deployment. This will allow the selection of the vault to inject and upload certificates in the image build deployment. Since we will use GUID to help create the name it will be deterministic and allow us to hard-code the selection of just this vault in the image build template.

I am going to replace the existing Image build section with HostPool properties including scaling plans (now GA), and RDP properties.

from avdaccelerator.

closing as done

from avdaccelerator.