Skip to content

Commit c002223

Browse files
authored
Explain change in behavior with AzureAD cmdlets
1 parent 03254a3 commit c002223

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/cloud-shell/troubleshooting.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,11 @@ Known resolutions for troubleshooting issues in Azure Cloud Shell include:
2525

2626
## General troubleshooting
2727

28+
### Error running AzureAD cmdlets in PowerShell
29+
30+
- **Details**: When running AzureAD cmdlets such as `Get-AzureADUser` in Cloud Shell you may see an error `You must call the Connect-AzureAD cmdlet before calling any other cmdlets`.
31+
- **Resolution**: Run the Connect-AzureAD cmdlet. Previously, Cloud Shell ran this automatically during PowerShell startup. This has been removed in order to speed up start time. If desired, the previous behavior can be restored by adding `Connect-AzureAD` to the $PROFILE file in PowerShell.
32+
2833
### Early timeouts in FireFox
2934

3035
- **Details**: Cloud Shell utilizes an open websocket to pass input/output to your browser. FireFox has preset policies that can close the websocket prematurely causing early timeouts in Cloud Shell.

0 commit comments

Comments
 (0)