Container Apps environment stuck in "Scheduled for delete" for 40+ minutes, no VNet, blocks creating a new environment (Azure for Students)

Huy Vu 0 Reputation points
2026-11-18T21:01:48.3066667+00:00

My Container Apps environment (Workload profiles mode, East Asia) has been stuck in "Scheduled for delete" since 2026-11-18 20:17 UTC, and my production site is down because of it.

What I did:

  1. Deleted the only container app in it (succeeded at 20:17:27 UTC).
  2. Deleted the environment at 20:17:31 UTC with az containerapp env delete. The Activity log shows "Delete Managed Environment" as Accepted, and no Succeeded or Failed event has appeared since.

Current state:

  • provisioningState is ScheduledForDelete, and deploymentErrors is empty.
  • Applications: 0. No VNet integration (vnetConfiguration is null), no infrastructure resource group visible, and no locks on the resource group.
  • One managed certificate is still listed under the environment. Deleting it returns ManagedEnvironmentNotProvisioned ("The environment has not been provisioned successfully").
  • Azure Service Health shows no active issues.

Why it matters: This is an Azure for Students subscription, which allows only one Container Apps environment. Creating the replacement environment in Malaysia West fails with MaxNumberOfGlobalEnvironmentsInSubExceeded while the stuck one still counts. The subscription has no technical support plan, so I cannot open a support ticket.

Could someone from the Container Apps team force-complete the deletion on the backend, or raise the environment limit to 2 so I can recreate the environment? I can share the subscription ID, the resource ID and the correlation ID of the delete operation privately.

Thank you.My Container Apps environment (Workload profiles mode, East Asia) has been stuck in "Scheduled for delete" since 2026-11-18 20:17 UTC, and my production site is down because of it.

What I did:

  1. Deleted the only container app in it (succeeded at 20:17:27 UTC).
  2. Deleted the environment at 20:17:31 UTC with az containerapp env delete. The Activity log shows "Delete Managed Environment" as Accepted, and no Succeeded or Failed event has appeared since.

Current state:

  • provisioningState is ScheduledForDelete, and deploymentErrors is empty.
  • Applications: 0. No VNet integration (vnetConfiguration is null), no infrastructure resource group visible, and no locks on the resource group.
  • One managed certificate is still listed under the environment. Deleting it returns ManagedEnvironmentNotProvisioned ("The environment has not been provisioned successfully").
  • Azure Service Health shows no active issues.

Why it matters: This is an Azure for Students subscription, which allows only one Container Apps environment. Creating the replacement environment in Malaysia West fails with MaxNumberOfGlobalEnvironmentsInSubExceeded while the stuck one still counts. The subscription has no technical support plan, so I cannot open a support ticket.

Could someone from the Container Apps team force-complete the deletion on the backend, or raise the environment limit to 2 so I can recreate the environment? I can share the subscription ID, the resource ID and the correlation ID of the delete operation privately.

Thank you.

Azure Container Apps
Azure Container Apps

An Azure service that provides a general-purpose, serverless container platform.

0 comments No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-11-18T21:03:03.5933333+00:00

    Submit an Azure Container Apps managed-environment-count quota request first; if the request cannot be submitted or does not release the blocked slot, create a support request asking Microsoft to remove the stale environment record and complete the backend deletion.

    1. Request the environment-count quota

    The error MaxNumberOfGlobalEnvironmentsInSubExceeded explicitly identifies a quota limit. Container Apps documents Managed environment count as a subscription quota handled through Azure Quota Management System (QMS).^1^

    1. In the Azure portal, search for and open Quotas.
    2. Set Provider to Azure Container Apps.
    3. Select the Azure for Students subscription.
    4. Search for managed environment.
    5. Check both the relevant regional quota and the global environment quota.
    6. If an edit pencil is available, request a limit of 2. When increasing a regional environment quota, Microsoft recommends requesting the corresponding global quota increase as well.^2^

    Azure’s general quota documentation states that only paid subscriptions can request quota increases through this mechanism.^3^ Therefore, QMS might reject or omit the edit option for Azure for Students. If so, proceed directly to escalation.

    2. Request stale-record cleanup through Azure Support

    There is no documented customer-accessible command to force-complete an Azure Container Apps backend deletion. A closely matching ScheduledForDelete case describes backend cleanup as the required outcome once the managed environment is orphaned.^4^

    A paid technical-support plan is not required for subscription-management requests, including quota adjustments. Azure provides unlimited support for that category.^5^

    In the portal:

    1. Select ? in the global header → Support + Troubleshooting.
    2. Describe the issue as:

      Azure Container Apps managed-environment count remains consumed by an environment stuck in ScheduledForDelete.

    3. Select Create a support request.
    4. Choose:
      • Issue type: Service and subscription limits (quotas)
      • Service/provider: Azure Container Apps
      • Subscription: the affected Azure for Students subscription
    5. Ask for:
      • Completion of the pending managed-environment deletion.
      • Removal of the stale environment/quota record.
      • Alternatively, a temporary global and regional managed-environment-count increase to 2.
    6. Include:
      • Environment resource ID and name.
      • Resource group and source region.
      • Deletion timestamp in UTC.
      • Delete-operation correlation or operation ID.
      • Current ScheduledForDelete state.
      • Exact MaxNumberOfGlobalEnvironmentsInSubExceeded error.
      • Target replacement region.
      • Production impact.
      • Confirmation that the environment has no apps, jobs, VNet integration, private endpoints, or resource locks.
      • The managed-certificate deletion error.

    Microsoft’s Container Apps escalation guidance specifically requests the resource ID, region, full error, UTC timestamps, and correlation or operation IDs.^6^

    Do not post subscription IDs, resource IDs, or correlation IDs publicly in Q&A comments. Supply them only through the private support request.

    Actions that do not apply here

    The standard documented remediation for an environment stuck in ScheduledForDelete is to delete its associated VNet and then retry environment deletion.^7^ Your environment reports vnetConfiguration: null, so there is no customer VNet to remove. The subnet/service-association-link workaround from other cases is likewise inapplicable.

    Do not repeatedly retry deletion or attempt to manipulate the remaining managed certificate. The environment is already processing a delete operation, and the certificate endpoint is rejecting changes because the environment is no longer provisioned. The relevant next action is quota/support escalation, not certificate recreation.


    References

    1. Request quota changes for Azure Container Apps
    2. Azure Container Apps frequently asked questions (FAQs)
    3. Quickstart: Request a quota increase in the Azure portal
    4. Container Apps Managed Environment stuck in ScheduledForDelete for multiple days - Microsoft Q&A
    5. Create an Azure support request
    6. Troubleshoot environment capacity errors in Azure Container Apps | Microsoft Learn
    7. Troubleshoot a container app
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.