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

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

Feedback and Knowledge Base