Key Vault Admin and Readers

`2.1.3 edit the config yaml files found in /iac-adb-360/pipelines/azure/configdev.yml and configprd.yml to reflect the correct Resource Group name, location and the group object id's for the kvadmins as well as the kvsecretreaders. This groups are added as keyvault admins and keyvault secret readers in the key vault, which is going to be automatically deployed by the pipeline. So if not already done so, you'll have to create two groups p.ex. kvadmins and kvsecretreaders in Microsoft Entra ID, retrieve the OIDs and edit them in the two files accordingly. After you edit this files, they need to be updated in the repo. So if you were working locally, you'll have to commit and push to the repo.(make sure you are on the 'dev' branch)
`
I am not sure the purpose of this? Is it to assign the service principals the roles? If so wouldn't that be done directly against the service principal?

Inizia da iac-adb-360/pipelines/azure/configdev.yml e configprd.yml, quindi esamina come la pipeline usa questi file per distribuire il key vault. Verifica la Resource Group prevista, la posizione e gli object ID dei gruppi Entra ID per kvadmins e kvsecretreaders; il lavoro è completato quando entrambi i file contengono i valori confermati e sono stati aggiornati nel branch dev.

Scritto dal modello di indicizzazione a partire dal testo della issue.