Connect-exchangeonline in azure shell not possible anymore

Two days later, the issue disappeared.
Steps to debug after first noticing the error:

• determine the current exchangeonlinemanagement module baked in in the cloud shell: 3.8.0
• test "connect-exchangeonline" error (module 3.8.0)
• install a previous version (3.7.0)in the home folder, which overrides the default one
• restart cloud shell
• test "connect-exchangeonline" error (a different one, module 3.7.0)

Now:

• test "connect-exchangeonline" (module 3.7.0): OK
• unistall 3.7.0 module
• restart cloud shell
• test "connect-exchangeonline" (module 3.8.0): OK

To sum up: no corrective actions were possible to resolve the issue. However, it disappeared on its own after two days.
Output below:

PS /home/myself> connect-exchangeOnline -Verbose                                                                                                        VERBOSE: Computed version info: 3.7.0          
VERBOSE: ModuleVersion: 3.7.0
VERBOSE: [ThreadID: #] Trying to get a new token from AAD for cloudshell login
VERBOSE: [ThreadID: #] Uri string for cloudshell login http://localhost:50342/oauth2/token?resource=https%3A%2F%2Foutlook.office365.com%2F&api-version=2018-02-01.
VERBOSE: [ThreadID: #] Successfully got a token from AAD
----------------------------------------------------------------------------------------
This V3 EXO PowerShell module contains new REST API backed Exchange Online cmdlets which doesn't require WinRM for Client-Server communication. You can now run these cmdlets after turning off WinRM Basic Auth in your client machine thus making it more secure.

Unlike the EXO* prefixed cmdlets, the cmdlets in this module support full functional parity with the RPS (V1) cmdlets.

V3 cmdlets in the downloaded module are resilient to transient failures, handling retries and throttling errors inherently.

REST backed EOP and SCC cmdlets are also available in the V3 module. Similar to EXO, the cmdlets can be run without WinRM basic auth enabled.

For more information check https://aka.ms/exov3-module

Starting with EXO V3.7, use the LoadCmdletHelp parameter alongside Connect-ExchangeOnline to access the Get-Help cmdlet, as it will not loaded by default.
----------------------------------------------------------------------------------------
VERBOSE: AutoGen EXOModule created at  /tmp/tmpEXO_ffgmmmwi.30x
VERBOSE: Running Configure-AppSettings
VERBOSE: Setting PrintWarningsReceivedFromServer to False
VERBOSE: Logs location is reset to /tmp/EXOCmdletTelemetry
VERBOSE: Max directory size reset to 2000000000
VERBOSE: Max log size reset to 100000000
VERBOSE: Log level reset to Default
VERBOSE: Logger reset to null.

PS /home/myself> get-module -listAvailable | ? {$_.name -match "exch" }                 
    Directory: /home/myself/.local/share/powershell/Modules
ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Script     3.7.0                 ExchangeOnlineManagement            Desk      {Add-VivaModuleFeaturePolicy, Get-ConnectionInformation, Get-DefaultTenantBr…
    Directory: /usr/local/share/powershell/Modules
ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Script     3.8.0                 ExchangeOnlineManagement            Desk      {Add-VivaModuleFeaturePolicy, Add-VivaOrgInsightsDelegatedRole, Get-Connecti…
PS /home/myself> Uninstall-Module -name exchangeonlinemanagement -MaximumVersion 3.7.0
PS /home/myself> get-module -listAvailable | ? {$_.name -match "exch" }               
    Directory: /usr/local/share/powershell/Modules
ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Script     3.8.0                 ExchangeOnlineManagement            Desk      {Add-VivaModuleFeaturePolicy, Add-VivaOrgInsightsDelegatedRole, Get-Connecti…

# CLOUD SHELL RESTART

PS /home/myself> Connect-ExchangeOnline -verbose                       
VERBOSE: Computed version info: 3.8.0
VERBOSE: ModuleVersion: 3.8.0
VERBOSE: [ThreadID: #] Trying to get a new token from AAD for cloudshell login
VERBOSE: [ThreadID: #] Uri string for cloudshell login http://localhost:50342/oauth2/token?resource=https%3A%2F%2Foutlook.office365.com%2F&api-version=2018-02-01.
VERBOSE: [ThreadID: #] Successfully got a token from AAD
----------------------------------------------------------------------------------------
This V3 EXO PowerShell module contains new REST API backed Exchange Online cmdlets which doesn't require WinRM for Client-Server communication. You can now run these cmdlets after turning off WinRM Basic Auth in your client machine thus making it more secure. 
Unlike the EXO* prefixed cmdlets, the cmdlets in this module support full functional parity with the RPS (V1) cmdlets.
V3 cmdlets in the downloaded module are resilient to transient failures, handling retries and throttling errors inherently. 
REST backed EOP and SCC cmdlets are also available in the V3 module. Similar to EXO, the cmdlets can be run without WinRM basic auth enabled. 
For more information check https://aka.ms/exov3-module
Starting with EXO V3.7, use the LoadCmdletHelp parameter alongside Connect-ExchangeOnline to access the Get-Help cmdlet, as it will not be loaded by default
----------------------------------------------------------------------------------------
VERBOSE: AutoGen EXOModule created at  /tmp/tmpEXO_ual3f402.itr
VERBOSE: Running Configure-AppSettings
VERBOSE: Setting PrintWarningsReceivedFromServer to False
VERBOSE: Logs location is reset to /tmp/EXOCmdletTelemetry
VERBOSE: Max directory size reset to 2000000000
VERBOSE: Max log size reset to 100000000
VERBOSE: Log level reset to Default
VERBOSE: Logger reset to null.