@@ -336,7 +336,7 @@ In order to use a VIM target based on Azure, the following information needs to
- Access credentials:
-`client_id`: In the case of a service principal (recommended for production deployments), this attribute corresponds to the Azure `application Id`. For regular users, this value is the `object Id` from user profile in portal (this approach can be more convenient for casual OSM testing).
- The `authentication Key`.
- Resource Group: all Azure resources for a VIM target will be created into the same `resource_group`. Said resource group could exist before or, in case it did not exist, OSM would try to create it upon the creation of the VIM target (the latter would require that your user/service principal had sufficient privileges in the subscription - check with your administrator).
- Resource Group: All Azure resources for a VIM target will be created into the same `resource_group`. Said resource group could exist before or, in case it did not exist, OSM would try to create it upon the creation of the VIM target (the latter would require that your user/service principal had sufficient privileges in the subscription - check with your administrator).
The above data can be accessed through the Azure portal, but can also be obtained through the CLI. For instance, once logged in, the commands `az ad signed-in-user show ` and `az account list` returns, among other information, `application Id`, `object Id`, `tenant Id` and `subscription Id`.
