MYSTERIOUS ELASTIC POOLS USAGE ON SPONSORED SUBSCRIPTION

Question

MYSTERIOUS ELASTIC POOLS USAGE ON SPONSORED SUBSCRIPTION

pierre shiraziefard 40

Existing ticket 2602260040003689 handled by Billing, suggested I create this here.

some history summary:

this is a very small app, storage is 50mb and drive space is 50GB, 2 core VCPU. the spikes started in NOV 2025 forwards (I have attached one pic based on usage for this subscription). we did not make any changes. prior to that it used to be $25-$50 monthly now its close to $300-$500 and is depleting our sponsored credits.

upon investigation with billing department this started Aug 12th 2025 , cannot locate these resources on the azure portal yet I see them referenced on the sponsorship usage reports.

No dramatic changes were initiated by us as far as i know, yet it used up $1200 from our credits.

Would like to know WHO STARTED THIS service back in August 12th 2025, and also our billing for this spiked starting in December 1 2025 through Feb 27th 2026.

Manoj Kumar Boyini 9,410 Reputation points Microsoft External Staff Moderator

2026-03-05T16:51:08.7333333+00:00

Hi pierre shiraziefard

The charges occurred because an Azure SQL Elastic Pool was created in the subscription. Elastic Pools are billed per hour as long as they exist, regardless of database size or actual usage. Even if databases are small or later removed, the pool continues to generate charges until it is deleted.

The charges starting around August 12, 2025 indicate that an Elastic Pool was explicitly created at that time. Azure does not automatically create Elastic Pools.

The higher costs seen from December 2025 onward are consistent with the pool being scaled up or remaining at a higher configuration, which increases the hourly rate.

Identifying who created the Elastic Pool is not available from the Azure portal or Azure SQL service. The only supported way to determine this is by reviewing Azure Activity Logs at the subscription level.

To stop further charges, please confirm whether the Elastic Pool still exists and delete it if it’s not required. For historical credit impact, Azure Billing Support is the appropriate team to assist further.

Hope this helps, Please let us know if you have any questions and concerns.
Manoj Kumar Boyini 9,410 Reputation points Microsoft External Staff Moderator

2026-03-12T16:00:08.58+00:00

Hi pierre shiraziefard

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
pierre shiraziefard 40 Reputation points

2026-03-12T16:26:38.03+00:00

The Microsoft conversion team must have created that back in Aug 12, 2025 as we did not. it took the backend team at Microsoft 3 weeks to move us from MS Action Pack to Sponsored. How do we need to resolve this error, so we get our billing credits back?