Share via

Storage Accounts - High Standard Data Transfer Out Costs across region (where no resource exists)

Vidyanath Vemula 0 Reputation points
2024-10-21T01:20:28.7266667+00:00

We use Azure Table Storage extensively in our platform. Of late, we have been noticing surging Data Transfer Out Costs from our region (Meter Region: AU EAST), while we do not have any resources in that region. All our storage accounts and APIs (Different cloud provider) are in (South India).

After working with Azure support team, we have undertaken multiple configuration changes with no luck. Summary of changes are as below:

1 ) Originally we might have enabled Geo-Redundant Storage (GRS) for couple of storage accounts but after that we switched back to Local Redundant Storage (LRS). It's been more then 60 days that change has occured.

  1. We have ensured to enable firewall restrictions to provide acccess to specific IPs.
  2. Changed "Network Routing" from "Microsoft" to "Internet" and also "Internet" for "end points".

Please suggest any solution to find the root cause for this cost and how to minimize the same.

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
3,192 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sumarigo-MSFT 46,286 Reputation points Microsoft Employee
    2024-10-22T13:49:02.8833333+00:00

    @Vidyanath Vemula Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

    It sounds like you've already taken several steps to address the issue with surging Data Transfer Out Costs from the AU EAST region.

    Based on your scenario I would recommened, please contact Azure Billing and Subscription team would be the best to provide more insight and guidance on this scenario: https://azure.microsoft.com/en-us/support/options/ it's free, and it's the best choice for your scenario, They can provide detailed information on your issue.

    Additional information:

    Here are a few additional suggestions that might help you identify the root cause and minimize the costs: To find the root cause of the cost surge, you may want to check if there are any applications or services that are accessing your storage account in the AU EAST region. You can use Azure Monitor to track the usage and performance of your storage accounts. You can also check the logs and metrics for your storage accounts to see if there are any unexpected activities or spikes in data transfer.

    1. Check for Hidden Dependencies: Ensure that there are no hidden dependencies or services that might be causing data transfer to the AU EAST region. Sometimes, services like Azure Traffic Manager or Azure CDN might route traffic through different regions.
    2. Review Network Configuration: Double-check your network configuration to ensure that all traffic is being routed correctly. Misconfigurations can sometimes lead to unintended data transfers.
    3. Analyze Logs and Metrics: Use Azure Monitor and Azure Storage Analytics to analyze logs and metrics. This can help you identify any unusual patterns or spikes in data transfer that might indicate the source of the issue.
    4. Evaluate Firewall Rules: Re-evaluate your firewall rules to ensure that only the necessary IPs have access to your storage accounts. This can help prevent unauthorized access and data transfer.
    5. Consider Using Azure Cost Management: Utilize Azure Cost Management and Billing to get detailed insights into your data transfer costs. This tool can help you identify specific services or resources that are contributing to the high costs.

    Please let us know if you have any further queries. I’m happy to assist you further.    

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments

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.