API - Translator Text / Speech: Get a report of your consumption

When you are subscribed to the S1 pricing tier, Pay As You Go, for either the Microsoft Translator Text API or Translator Speech API in the Azure portal, you receive a day-by-day report of your consumption in a.csv file in the Azure billing portal. To view the report, follow the steps below.

There is a 24-hour delay between the actual consumption and when it is displayed in the report. To see the Microsoft Translator API consumption, filter by Meter Category = Cognitive Services. The report will display one line per day per service.

Consumption monitoring for all of the Microsoft Translator API subscription tiers is currently available in your Azure portal dashboard. The graphs are customizable based on the parameters available and can display usage for <30 days. For the monthly commitment tiers, such as the S2, S3 and S4 pricing tiers, when you reach the monthly commitment volume for those tiers during a subscription month, your usage goes into Overage. Generally, you will see a quantity of "1" in the Daily Units column in the .csv file. You'll know you're in Overage when you see in the "Daily Units' column a Quantity greater than "1".

Learn how to download or view your billing invoice and usage data at https://docs.microsoft.com/en-us/azure/billing/billing-download-azure-invoice-daily-usage-date

To view the Azure billing report (.csv file):
1) Visit https://account.windowsazure.com/Subscriptions
2) Choose the name of your Azure subscription
3) Choose the "Download usage details" link, on the right side of the page
4) Choose "Download usage"

Updated on September 21, 2017


  1. Announcements: Microsoft Translator Moves to the Azure portal
  2. API - Translator Data Centers
  3. API and Hub: Confidentiality
  4. API - Translator Text: How to report an issue with the API
  5. API - Translator Speech: Microsoft Translator Speech API references
  6. API - Translator Text / Speech: Get a report of your consumption
  7. API - Translator Text / Speech: Using the API key directly in the call. No more token.
  8. API - Translator Text / Speech: Why are there two keys for my API subscription?
  9. API - Translator Text: Hybrid Neural Machine Translation
  10. API - Translator Text: Using Neural MT Systems
  11. API - Translator Text: My CAT tool isn't working and is asking for the Client ID and Client Secret
  12. API - Translator Text: Limits
  13. API - Translator Text: How Microsoft Translator counts characters
  14. API - Translator Text: Gender selection in the Speak() method
  15. API - Translator Text: Trados plugin for Microsoft Translator
  16. API - Translator Text: Java- Using SSL with the Microsoft Translator API
  17. API - Translator Text: European datacenter
  18. API - Translator Text: Languages detected by the Detect() method
  19. API - Translator Text: Using the Collaborative Translation Framework (CTF)
  20. API - Translator Text: First few Microsoft Translator API requests succeed, then the calls fail
  21. API - Translator Text: Microsoft Translator with IP filtered firewalls
  22. API - Translator Text: Profanity filtering in the TranslateArray() method
  23. Hub: API Preview released
  24. Hub: Translator Hub Resource Guide
  25. Hub: August 2016 Release notes
  26. Hub: Deployment of a custom system requires a Microsoft Translator Text API subscription in the Azure portal
  27. Hub: Capacity of custom Microsoft Translator Hub systems
  28. Hub: Building a custom system using a dictionary only
  29. Business Applications: Security and Privacy in Microsoft Office Products

Feedback and Knowledge Base