Table output of Azure CLI 2.0 is not as user friendly as default output of Azure CLI 1.0

For instance under 1.0:

$ azure vm list-usage -l eastus  | head
info:    Executing command vm list-usage
data:    Name                          Unit   CurrentValue  Limit
data:    ----------------------------  -----  ------------  -----
data:    Availability Sets             Count  0             2000 
data:    Total Regional Cores          Count  246           560  
data:    Virtual Machines              Count  38            10000
data:    Virtual Machine Scale Sets    Count  0             2000 
data:    Standard NC Family Cores      Count  246           558  
data:    Basic A Family Cores          Count  0             20   
data:    Standard A0-A7 Family Cores   Count  0             20   

now same command with 2.0:

$ az vm list-usage -l eastus -o table | head
  Limit    CurrentValue
-------  --------------
   2000
    560             246
  10000              38
   2000
    558             246
     20
     20
     20

[ogrisel]

I found that this is not the only command. Pretty much all the az commands lack important infos that are displayed by default with the matching azure commands. For instance:

$ az vm list -o table
Name                    ResourceGroup           Location
----------------------  ----------------------  --------------
vm-name1                GROUP1                  eastus
vm-name2                GROUP1                  eastus

vs

$ azure vm list
data:    ResourceGroupName       Name                    ProvisioningState  PowerState      Location        Size         
data:    ----------------------  ----------------------  -----------------  --------------  --------------  -------------
data:    GROUP1                  vm-name1                Succeeded          VM deallocated  eastus          Standard_NC6 
data:    GROUP1                  vm-name2                Succeeded          VM deallocated  eastus          Standard_NC6 

I think a systematic review of all the commands is needed to ensure that UX is not degraded when switching from azure CLI 1.0 to azure CLI 2.0.

[yugangw-msft]

Closing this as both cases were taken care of. For showing powerState through -d, we would like keep this way, as it involves more expensive API invocation so opt-in is reasonable. For other commands, we have already fixed a lot. Let us can open individual ones for specific commands