Deployment of Azure SQL Managed Instance stuck in Step 3 - New Instance Startup

Johannes Maly 101 Reputation points
2025-02-05T11:29:47.73+00:00

Yesterday I started to create a SQL Managed Instance (Creation date: 2025-02-04 11:31 (UTC)).

I tried to create the SQL-MI in West Europe as General Purpose Standard-series (Gen 5) (4 vCores, 300 IOPS, 64 GB storage, Locally-redundant backup storage).

Deployment startet and no error was reported but since several hours the process got stuck:

Creating managed instance

Requested parameters

GP / Standard-series (Gen 5) / 4vCores / 64GB

Step 3/3: New SQL Instance Startup

In Progress

I also tried to create a SQL-MI a few days before with the same result - stuck in step 3:

User's image

A colleague of mine from another company also tried it and got the same result. Step 3 got stuck. Creation of SQL-MI was running for more than 22 hours before he canceled the deployment.

No errors were reported so far. As far as I heard a normal deployment would take between one up to four hours.

Does anybody know how to locate the huge delay in SQL-MI creation?

BR Johannes

Azure SQL Database
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Mahesh Kurva 2,920 Reputation points Microsoft External Staff
    2025-02-05T13:27:14.45+00:00

    Hi @Johannes Maly,

    Welcome to Microsoft Q&A forum.

    As I understand, you're facing an issue with your SQL Managed Instance (SQL-MI) creation process being stuck for so long.

    We have reproduced your issue, but we were able to successfully create the SQL Managed Instance with your specifications.

    User's image

    • If you're using the Azure portal, try using Azure CLI or PowerShell instead.
    • If you're facing issues in the West Europe region, try deploying in a different region.
    • Ensure that your subscription and region have sufficient resources available for the deployment. Sometimes, resource constraints can cause delays.
    • Sometimes, deployments get stuck due to temporary issues that can be fixed by retrying.

    For more information, please refer the document: https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/instance-create-quickstart?view=azuresql&tabs=azure-portal

    Hope this helps. Do let us know if you any further queries.

    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


  2. Johannes Maly 101 Reputation points
    2025-03-05T16:19:05.5+00:00

    According to MS support:

    "Due to the maximum capacity over the region it has been stuck for such long time"

    I retried to deploy another SQL MI to region West Europe. This time it worked but the deployment took more than one day.

    Today I also tried to reconfigure the update policy for SQL MI. Even this process image

    takes a very very long time and has not finshed yet after several hours.

    Anyhow ... SQL MI deployment to West Europe seems to work. Even though you have to be VERY patient.

    Thanks to all for your support

    Johannes


Your answer

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