Accidentally switched dev SQL database from DTU to vCore – Advice on preventing unexpected charges? can not create support ticket.

Question

Hello Azure Support Team,

I am writing to request a one time billing concession for my current unbilled usage. I have a small development/testing Azure SQL Database that is normally kept on the DTU purchasing model, which costs me around $5 per month.

Unfortunately, while doing some testing earlier this month, I mistakenly switched the database compute tier into the vCore purchasing model. Because this is just a dev environment, I didn't realize the massive price difference until I checked my Cost Management dashboard today and saw the accumulated charges for this month have already spiked to over $70.

I have already gone into the portal and immediately reverted the database back to the DTU model to stop the bleeding and ensure this doesn't happen again. Since the invoice has not yet been generated and this was an honest mistake on a non-production database, is it possible to get a one time courtesy credit applied to my account to offset these unbilled vCore charges?

I have attached a screenshot of the current cost analysis for reference. Thank you for your time and understanding.

Answer 1

Hi @vinod warnakulasooriya We understand that you unintentionally switched dev/test Azure SQL Database from the DTU model ($5/month) to the vCore model, which caused charges to spike to over $70 this month. However you have already reverted the database back to the DTU model to prevent further charges.

On the Microsoft Q&A Community forum we typically do not have access to your billing information or the ability to process refunds, as there is a dedicated support team for billing inquiries and issues. We kindly request you to create a support request with the billing team for further assistance. They will contact you via email or call to resolve it.

Here are the steps you can follow to create billing support requests:

• Go to Azure portal > Search for Help + Support or https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview
•  Click on Create a Support Request.
• On right-side panel, enter Billing and click Go > select the issue with "Billing" > select your Subscription then click Next.
• Click on the Create support request on top of the panel.
• Select the Issue type as Billing and, select the summary, problem type and problem subtype as below > click on Next.
• Do not click on any recommendation solution/article, instead click on the Return to support request then click Next.
• Fill all the required information and provide a clear description of your issue and click Next.
• Review and create as submit the support request.
• You should receive an automated email within a few minutes and then be contacted by support team.

Kindly check the documentation to know how to Create an Azure support request https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

If you have further questions regarding this answer, feel free to click "Comment". If you find the answer helpful, please click "upvote" and accept it. This helps the community by allowing others with similar queries to easily find the solution.

Answer 2

Hello vinod warnakulasooriya,

Greetings! Thanks for raising this question in the Q&A forum.

It is completely understandable how this happened the DTU to vCore switch is a configuration change that looks similar in the portal but carries a very significant price difference, and it is easy to apply accidentally in a dev environment. You have already done the right thing by switching back to DTU immediately. Now let's focus on how to get the billing concession you need and how to prevent this from happening again.

Important clarification: Billing support is completely free

You mentioned that you cannot create a support ticket. This is likely because the portal's support flow redirects you through technical support options that require a paid plan. However, billing support is a separate category and is available to all Azure customers at no cost. Billing support is free — there is no need to purchase a support plan. The trick is navigating to it correctly without getting stuck in the loop. Here is the exact path that works:

Step 1: Create a billing support request the correct way

1. Go to https://portal.azure.com/#view/Microsoft_Azure_CostManagement/Menu/~/support/openedBy/AzurePortal (this link takes you directly to the billing support path)
2. Click + New support request
3. In the search box, type Billing and select it
4. Select your subscription and click Next
5. When a list of automated suggestions appears, scroll past all of them and look for the "Create a support request" button at the top of the page. Do not click any of the suggested solutions — click the "Create a support request" button at the top.
6. If you are taken back to the suggestions screen again, click "Return to support request" in the upper left corner
7. Fill in the Problem type as Billing management and Problem subtype as Unexpected charges or credits
8. Click Next, fill in your details, and submit

You should receive an automated email within a few minutes and then be contacted by a billing engineer within one business day.

Step 2: What to say in your billing support request

Be clear and concise in your request. Include the following:

• Your Subscription ID
• The date range when the vCore charges were incurred
• That you accidentally switched from DTU to vCore during a configuration change on a dev/test database
• That you have already reverted back to DTU (mention the date you switched back)
• That you are requesting a one-time billing concession for the vCore charges incurred during this period
• Attach the Cost Management screenshot you already have showing the spike

Billing engineers have authority to apply one-time goodwill credits for accidental configuration changes, especially when you have already corrected the issue and the charges are still unbilled.

Step 3: Alternative way to reach billing support if the portal still blocks you

If you still cannot create a ticket through the portal, use this direct link:

https://azure.microsoft.com/en-us/support/create-ticket/

Select Billing as the support category. This bypasses the portal's support plan check entirely for billing issues.

You can also reach Microsoft's global customer service by phone. The India toll-free number for Microsoft billing support is 000 800 440 2442. Full global numbers are listed at: https://support.microsoft.com/en-us/topic/global-customer-service-phone-numbers

Step 4: Prevent this from happening again — set a Budget Alert

Once this is resolved, set up a Cost Management budget alert so you are notified immediately if your SQL Database spend exceeds your expected monthly amount. Go to Azure Portal > Cost Management > Budgets > Add and set a budget of, for example, $10/month for your dev database resource group with an alert threshold at 80%. This way any accidental tier change will trigger an email alert before the bill gets significant.

Step 5: Lock the database configuration with an Azure Policy (optional but recommended)

For a dev database you want to keep on DTU, you can apply an Azure Policy that restricts allowed SKUs. Go to Azure Portal > Policy > Definitions, search for "Allowed SKUs" for SQL Database, and assign it to your resource group scoped to only the DTU-based SKUs (Basic, Standard, Premium). This prevents accidental vCore switches from being saved.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.