Share via

Microsoft.SqlVirtualMachine Resource Provider returning GatewayTimeout for specific VM in East US 2 — CLI and Terraform both affected

Dharati Parmar 0 Reputation points
2026-03-19T08:42:34.0833333+00:00

The Azure Resource Provider Microsoft.SqlVirtualMachine is returning a GatewayTimeout for a specific SQL VM resource in East US 2. All API calls to read this resource fail — both via Azure CLI and Terraform — while the same configuration works fine for identical VMs in other regions. The SQL IaaS Agent Extension is showing as Successfully Provisioned and the RP is Registered at subscription level. This appears to be a backend RP issue specific to this resource.
Has anyone faced this exact issue? Can anyone suggest solution/ workaround?

Thank you.

SQL Server on Azure Virtual Machines

2 answers

Sort by: Most helpful
  1. Dharati Parmar 0 Reputation points
    2026-03-24T06:39:40.8733333+00:00

    Thank you all for your assistance, It seems like issue from Azure side form Azure resource manager and it got Auto -resolved yesterday. Able to connect to the VM through terraform and CLI both.

    0 comments No comments

  2. SUNOJ KUMAR YELURU 18,171 Reputation points MVP Volunteer Moderator
    2026-03-19T09:54:28.3866667+00:00

    Hello @Dharati Parmar,

    The issue you are experiencing with the Azure Resource Provider Microsoft.SqlVirtualMachine returning a GatewayTimeout for a specific SQL VM resource in East US 2 may indicate a backend problem specific to that resource.

    This is particularly relevant since the SQL IaaS Agent Extension shows as successfully provisioned, and the resource provider is registered at the subscription level, which are both necessary for proper functionality.

    In general, if the SQL Server VM is not registered with the SQL IaaS Agent extension, you might encounter issues like the one described.

    To resolve such issues, ensure that your SQL Server VM is properly registered with the SQL IaaS Agent extension, which can be done through the Azure portal or using Azure CLI commands. If problems persist, consider deleting and reinstalling the SQL IaaS Agent extension if it is in a failed state, as this can sometimes resolve underlying issues with the resource provider.

    Additionally, if you are seeing errors related to the resource not being found, it may indicate that the SQL virtual machine resource is not properly linked to the underlying VM resource, which can also lead to timeouts and failures in API calls


    If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

    0 comments No 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.