Hi DM IT,
Thank you for reaching out to Microsoft QA.
We found that the issue is not with your setup but with how the system handles your Azure Sponsorship subscription in the Southeast Asia region.
When the SQL Server creation starts, Azure tries to create some background network components such as a public IP address. In this case, the network part returned a different configuration than what the SQL service expects in this region under a sponsorship plan. Because of that mismatch, the SQL Server creation stopped before it could even begin.
This usually happens when the selected region or the subscription offer does not support that resource tier.
To fix this, please try the following:
- Create the SQL Server in another supported region such as East US, West US 2, or North Europe. These regions work fine for Azure Sponsorship plans.
The SQL provider setup for your subscription is already registered correctly, so no further action is needed there.
Please let us know if you have any questions and concerns