My service has been disabled and need assistance to get it back up

IQSR 0 Reputation points
2026-06-25T14:05:56.1766667+00:00

One of my SQL Servers has been disabled. There was a billing issue due to an expired card, etc., but that was resolved 48 Hours ago. The other services have been running for 24 hours, but this service is still disabled.

Please help.

SQL Server on Azure Virtual Machines

3 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-06-25T14:06:14.6466667+00:00

    Since the billing issue with the expired card is already resolved and other services are running again, the remaining disabled SQL Server VM is most likely affected by the subscription’s prior disabled state and may not have fully resumed.

    Take these steps:

    1. Confirm the subscription is fully active
      • In the Azure portal, go to Subscriptions and verify the subscription that hosts the SQL Server VM is in Active state (not Disabled/Cancelled).
      • If it still shows disabled due to billing, follow the guidance in Reactivate a disabled Azure subscription to ensure all billing issues are cleared and the subscription is reactivated. For past-due or card issues, use the banner in the portal to go to Settle balance or update the card as described in the billing articles.
    2. Allow for reactivation propagation
      • After a subscription is reactivated or billing is fixed, it can take up to 24 hours for all resources to be fully usable again. Since this SQL Server has been unavailable longer than that while others are working, treat it as a stuck resource and continue with the next steps.
    3. Manually check and start the SQL Server service (inside the VM)
      • Connect to the Azure VM that hosts SQL Server.
      • Open SQL Server Configuration Manager and select SQL Server Services.
      • Locate the SQL Server instance:
        • If Status is Stopped, start it.
        • If Start Mode is Disabled (shown as Other (Boot, System, Disabled or Unknown)), re-enable it:
          1. Right‑click the service → Properties.
          2. On the Service tab, change Start Mode from Disabled to Manual or Automatic (per requirements).
          3. Apply and then start the service.
    4. Check if the SQL Server service is paused
      • If connections fail with a message that the SQL Server service is paused, resume it using SQL Server Configuration Manager or the Windows Services console, as indicated for error 17142.
    5. Verify the VM and quotas
      • Ensure the Azure VM itself is Running in the Azure portal.
      • If the VM or related App Service endpoints show messages like “This web app is stopped” or quota/billing limit messages, follow the guidance to:
        • Confirm no spending limit or quota is still blocking the resource.
        • If a spending limit was hit, remove the spending limit or wait for the quota reset, or scale up the plan if applicable.
    6. If the SQL Server service still cannot be started
      • If the service remains disabled or fails to start after these steps, or if the subscription/resources still appear partially blocked more than 24 hours after payment, open a support request so Azure Billing/Support can check the subscription and resource state.
      • Use the Azure portal → Help + support to create a support request and reference that the subscription billing issue was resolved 48 hours ago but one SQL Server VM remains disabled.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Megha Ramakrishnan 500 Reputation points
    2026-06-26T02:31:46.5566667+00:00

    Hi @IQSR ,

    Since the issue with the billing is already cleared, the issue is due to Azure subscription getting disabled due to a past-due balance, the billing platform flags your account.

    After you pay, the backend billing system clears most of the resources automatically, but Azure SQL Database and SQL Managed Instances frequently get stuck in a "Disabled" or "Disconnected" state because the database resource providers don't always catch the subscription's state change sync.

    You can follow the below steps to see if the issue is resolved.

    1. Force a Configuration Refresh If the portal shows the subscription is active, but the SQL Server or its underlying databases still report as disabled or won't accept connections, you need to force Azure to redeploy/update the resource metadata. This triggers a sync with the billing layer.

    For an Azure SQL Database (Singleton / Elastic Pool):

    1. Navigate to the specific SQL database in the Azure Portal.
    2. In the left-hand menu under Settings, click Compute + storage.
    3. Make a minor change to the scale settings. For example, scale your vCores or DTUs up or down by one step, or adjust your data storage limit by 10 GB. (If it's Serverless, you can just toggle the Auto-pause delay by a few minutes).
    4. Click Apply. This forces Azure to run a deployment script on the underlying container, which re-evaluates the subscription status and breaks the database out of the billing freeze. You can scale it right back down to your original setting immediately afterward.

    For Azure SQL Managed Instance:

    1. Since scaling anManaged Instance takes a long time, try changing a lighter configuration setting. Go to Networking under Settings.
    2. Make a minor adjustment (like temporarily associating/disassociating an unused network security rule or modifying a tag).
    3. Check for an Unpaid Invoice

    Sometimes a credit card clears the most recent bill, but an older, tiny outstanding balance or a separate invoice is still blocking the resource provider.

    1. Navigate to Cost Management + Billing > Invoices.
    2. Look through the list carefully. Ensure every single invoice shows as Paid.
    3. Create a billing support ticket

    If none of the above steps succeed, you can try creating a billing ticket.

    1. In the top right of the Azure portal, click the Help (?) icon and select Help + Support.
    2. Click Create a support request.
    3. Set Issue type to Billing.
    4. Select your affected subscription. 
    5. Set the Problem type to Reactivate a disabled subscription or Assistance with an unpaid balance. Provide the necessary description.

    Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

    Thank you!

    Was this answer helpful?

    0 comments
  3. Manoj Kumar Boyini 19,590 Reputation points Microsoft External Staff Moderator
    2026-06-30T13:42:41.23+00:00

    Hi @IQSR

    Since the billing issue was resolved about 48 hours ago and your other Azure resources are already running, your subscription has most likely been reactivated. Microsoft documentation indicates that reactivation after resolving a past-due balance typically completes within 24 hours.

    If only this SQL Server on Azure Virtual Machine remains affected, the issue is likely isolated to that VM or the SQL Server service running on it, rather than the subscription itself.

    Please check the following:

    1. Confirm the subscription is Active
      1. In the Azure portal, go to Subscriptions and verify the affected subscription shows Active.
      2. Also check Cost Management + Billing > Invoices to ensure there are no outstanding unpaid invoices.
      3. If the subscription still shows Disabled after 48 hours, please create a Billing support request.
      Reference: https://learn.microsoft.com/azure/cost-management-billing/manage/subscription-disabled
    2. Check the Virtual Machine
      1. Open the VM hosting SQL Server.
      2. Verify the Power State (Running / Stopped / Stopped (Deallocated)) and Provisioning State (Succeeded / Failed / Updating).
      3. If the VM is Stopped (Deallocated), try starting it and note any error message if the operation fails.

      Note: If the VM was deallocated while the subscription was disabled, its temporary public IP address may have changed after it is started unless a static public IP is being used.

    3. Review Resource Health and Activity Log
      1. Check Resource Health for any platform-related issues affecting the VM.
      2. Review the Activity Log for any failed Start, Restart, or provisioning operations after the subscription was reactivated.
    4. If the VM is running but SQL Server is unavailable
      1. Connect to the VM using RDP.
      2. Verify that the SQL Server (MSSQLSERVER) service (or the named instance service) is running.
      3. If the service fails to start, review the SQL Server ERRORLOG and Windows Event Viewer for the specific error.
      Reference: https://learn.microsoft.com/troubleshoot/sql/database-engine/startup-shutdown/sql-server-startup-errors

    To help narrow this down further, could you clarify what you mean by "disabled"?

    • Is the Azure Virtual Machine shown as Stopped, Unavailable, or Disabled in the Azure portal?
    • Or is the SQL Server service inside the VM stopped?
    • Or do you receive an error when attempting to connect to SQL Server?

    If possible, please also share:

    • A screenshot of the Azure portal showing the affected resource.
    • The VM's Power State and Provisioning State.
    • Any error message or error code when starting the VM or connecting to SQL Server.

    This information will help determine whether the issue is related to the Azure VM itself or the SQL Server service running inside it.

    Was this answer helpful?

    0 comments

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.