|
1 | 1 | ---
|
2 | 2 | description: This article answers common questions and explains how to troubleshoot Cloud Shell issues.
|
3 |
| -ms.date: 08/29/2024 |
| 3 | +ms.date: 11/04/2024 |
4 | 4 | ms.topic: troubleshooting
|
5 | 5 | tags: azure-resource-manager
|
6 | 6 | ms.custom: has-azure-ad-ps-ref
|
@@ -189,6 +189,27 @@ command that requires elevated permissions.
|
189 | 189 | Alternately, you can deploy your own private Cloud Shell instance. For more information, see
|
190 | 190 | [Deploy Cloud Shell in a virtual network][01].
|
191 | 191 |
|
| 192 | +### Terminal output - Sorry, your Cloud Shell failed to provision: {"code":"TenantDisabled" ...} |
| 193 | + |
| 194 | + |
| 195 | +- **Details**: In rare cases, Azure may detect fraudulent activity based on out-of-the-ordinary |
| 196 | + resource consumption based on the payload being submitted from Cloud Shell. When this occurs, |
| 197 | + Azure disables Cloud Shell at the tenant level and you see the following error message: |
| 198 | + |
| 199 | + > Sorry, your Cloud Shell failed to provision: {"code":"TenantDisabled","message":"Cloud Shell has |
| 200 | + > been disabled in directory<>."} Please refresh the page. |
| 201 | + |
| 202 | + There can be legitimate use cases where CPU usage within your Azure Cloud Shell instances exceeds |
| 203 | + the thresholds that trigger fraud prevention and block your tenant. Large AZCopy jobs could be |
| 204 | + cause this event. The Microsoft Azure engineering team can help to figure out why the tenant was |
| 205 | + disabled and reenable it, if required. |
| 206 | + |
| 207 | +- **Resolution**: Open a new Microsoft Azure support request to investigate the cause and reenable |
| 208 | + Cloud Shell for your tenant. Include the following details: |
| 209 | + |
| 210 | + 1. Tenant ID |
| 211 | + 2. The business justification and a description of how you use Cloud Shell. |
| 212 | + |
192 | 213 | ## Managing Cloud Shell
|
193 | 214 |
|
194 | 215 | ### Manage personal data
|
|
0 commit comments