diff --git a/04-vim-setup.md b/04-vim-setup.md
index 309339ef1e023253f64bc46cc17cf7dffb161989..a61e83afb4c5c8c36ea7fa6302d75ad6e23c1420 100644
--- a/04-vim-setup.md
+++ b/04-vim-setup.md
@@ -334,17 +334,21 @@ In order to use a VIM target based on Azure, the following information needs to
 - Azure `subscription Id`.
 - The `tenant Id`, to be created or obtained in the Microsoft portal.
 - 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 simply the `username` (this approach can be more convenient for casual OSM testing).
+  - `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 command `az account list` returns, among other information, `application Id`, `username`, `tenant Id` and `subscription Id`.
+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`.
 
 #### 2. Create Microsoft Azure Virtual Network
 
 The virtual networks created for the Azure VIM will all be created as subnets from a base virtual network. This base virtual network should be created before adding the VIM target and will also be provided as a configuration parameter.
 
-It is also recommended to create a management network for the VIM network services.
+It is also recommended to create a management subnet in that virtual network for the VIM network services, and both vnet and subnet can be created in a single step. For example, this command creates in `osmRG` resource group (must exist) the `osm_vnet` virtual network and the `internal` management subnet which uses `10.0.0.0/24` address prefix:
+ 
+```bash
+az network vnet create --resource-group osmRG --name osm_net --subnet-name internal --subnet-prefixes "10.0.0.0/24"
+```
 
 ### Adding Microsoft Azure as VIM target in OSM
 
@@ -359,8 +363,8 @@ osm vim-create --name azure --account_type azure --auth_url http://www.azure.com
 
 where:
 
-- `client_id`: Corresponds to the `application id` (for service principals) or the `username` (for regular users).
-- `client secret: `authentication key` (for a service principal) or `password`(for regular users).
+- `client_id`: Corresponds to the `application id` (for service principals) or the `object Id` (for regular users).
+- `client secret`: Authentication key (for a service principal) or `password` (for regular users).
 - `subscription_id`: Azure `subscription Id`
 - `tenant`: Azure `tenant Id`