You can see the underlying API that issued by the Python Process.
To do that, you could use fiddler or any client application that can capture traffic.
For Fiddler you can download and install from here
You will have enable Decrypt HTTPS traffic as all the traffic to Azure through CLI is done through HTTPs. Refer this for more information
Fiddler on running will now act as a proxy and will capture all the network traffic.
However, you will NOT be able to run the Azure CLI directly with the Fiddler on (Proxy) in place. You will have to add the certificate of the Fiddler to that of CLI's.
The fiddler Certificate can be found at http://localhost:8888. You will have to export the certificate and convert it to PEM format. The exported format is in .CRT
You can locally do this like mentioned here or use online tool to do this example :https://www.sslshopper.com/ssl-converter.html
Once you have the PEM Certificate - append the contents of this to certificate file that the CLI uses :
C:\Program Files (x86)\Microsoft
SDKs\Azure\CLI2\Lib\site-packages\certifi\cacert.pem
<Original cacert.pem>
-----BEGIN CERTIFICATE-----
<Your proxy's certificate here>
-----END CERTIFICATE-----
Now you will be able to intercept the traffic issued from a python process.

More information on this is documented here