Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
Azure Cloud Shell disabled at tenant level ("TenantDisabled") - request to re-enable
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 36%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Sean M
20
Reputation points
Azure Cloud Shell is failing to provision for my tenant with a "TenantDisabled" error. It appears to have been disabled at the directory (tenant) level. I'm the Global Administrator and would like it re-enabled.
Error message (launching Cloud Shell from the Azure portal) Sorry, your Cloud Shell failed to provision: {"code":"TenantDisabled","message":"Cloud Shell has been disabled in directory 'xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx'."} Please refresh the page.(masked the directory # for the community)
When it started / likely cause This began on 15 June 2026. I believe it was triggered by Azure's fraud-prevention thresholds reacting to a one-off, legitimate engineering task in Cloud Shell installing a CLI tool (crane), pulling and extracting a container image from our own Azure Container Registry, and running builds during a source-code recovery. This was normal development work on our own subscription, not abuse.
What I've checked
- I am the Global Administrator of the tenant.
- No Azure Policy is blocking Cloud Shell or Microsoft.Storage in the tenant.
- There is no portal toggle to re-enable it. The error is server-side / tenant-level.
- My current support plan doesn't allow opening a technical support request, which is why I'm posting here.
<personal info>
Request Could the Cloud Shell / engineering team please investigate and re-enable Cloud Shell for this tenant? I am the Global Administrator and I approve re-enablement, and I'm happy to provide any further details, including via private message.
Azure Cloud Services
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2026-06-15T03:15:12.0733333+00:00 Hello Sean
sorry you’re running into this. When you see
code: TenantDisabledwith the message that “Cloud Shell has been disabled in directory …”, it means Azure has disabled Azure Cloud Shell at the tenant level (even if you’re a Global Administrator).This can happen in rare cases where Cloud Shell appears to have out-of-the-ordinary resource consumption that triggers fraud-prevention safeguards.
What to do to get it re-enabled
To investigate and restore Cloud Shell for a tenant disabled state, you need an Azure internal/engineering re-enable request (via IcM) submitted by the engineering/support process.
In practice, that involves:
- Opening a support request / escalation that requests Cloud Shell re-enable for the tenant
- Including:
- Tenant ID
- Business justification for needing Cloud Shell
- A description of how you use Cloud Shell (and that it was legitimate work)
Note: The Cloud Shell documentation also calls out that the reason could be unusual workloads (for example, large job patterns). The Microsoft Azure engineering team can help identify why the tenant was disabled and then re-enable it once tenant admin approval/justification is provided. Why there may be no self-service toggle in the portal
This is described as a server-side / tenant-level disablement, so portal toggles or UI options typically won’t exist for you to reverse it yourself.
Once you have the above, you (or support on your behalf) can submit the re-enable request with the required tenant details and approval context.
Reference links (relevant docs)
- Cloud Shell disabled on tenant (internal escalation / re-enable workflow): https://portal.microsofticm.com/imp/v5/incidents/details/2510080030004188/summary
- CloudShell disabled for the entire tenant (IcM request guidance + TenantDisabled handling): https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/597002/SME%20Topics/Cloud%20Shell/TSGs/CloudShell%20disabled%20for%20the%20entire%20tenant_Cloud%20Shell
- How to enable CloudShell at tenant level (tenant-level unblock process overview): https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/1518268/SME%20Topics/Cloud%20Shell/How%20Tos/How%20to%20enable%20CloudShell%20at%20tenant_Cloud%20Shell
- Azure Cloud Shell FAQ (TenantDisabled/fraud-prevention explanation + what to provide): https://learn.microsoft.com/azure/cloud-shell/faq-troubleshooting?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#troubleshoot-errors
Sign in to comment
Sign in to answer