Reporting Hub Knowledge Center
  • Reporting Hub Knowledge Center
  • GETTING STARTED
    • Required Azure Services
    • Deployment Step-by-Step
      • Self-Serve Guided Install
      • Enable Power BI Service Settings
      • Configure Reporting Hub App Settings
      • Set Your Home Page
    • Azure Marketplace Install
  • CONCEPTS
    • Reporting Hub Architecture
    • AaaS end-to-end Architecture
    • Security & Trust Center
  • TUTORIALS
    • Azure Portal Administration
    • App Settings
      • Tenant Admin
        • Tenant Switching
      • Managing Your Subscription
      • Authentication Admin
      • Language Admin
      • SMTP Setup
      • Payment Provider Integrations
      • Notifications Admin
    • Embedded Capacity Admin
      • Switching to a Fabric Capacity
    • Connect Power BI Workspaces
    • Customize Theme
      • Branding (Images and Text)
      • Theme and Layout
      • Colors
        • Colors Overview
      • Fonts
    • Managing Content
      • The Manage Navigation Menu
      • Adding a Category
      • Embedding Power BI Content
      • Row Level Security
      • Search Tags
      • Content Page Options
      • Embedding a URL Page
      • Create Embed URL Links
    • Report Options
      • Create Report Bookmarks
      • Schedule Email Reports
      • Favorites
    • Managing Your Gateway
    • User Management
      • Managing User Access
      • Managing Groups
      • Managing Users in Entra ID
    • Secondary Environment (Test/Prod)
    • Embed the Reporting Hub in Your App
    • Usage Analytics
      • App Usage Tracking with Google Analytics
      • App Usage Tracking with SQL DB
    • App Performance
    • Azure Resource Monitoring
    • Self-Serve Guided Updates
  • Reference
    • What's new in the Reporting Hub?
    • Troubleshooting
    • Support Runbooks
      • Critical System Outage (L1)
      • Users Unable to Access (L2)
      • Content Not Available (L2)
      • Application is slow/getting slower (L2)
      • Capacity not starting/stopping automatically
Powered by GitBook
On this page
  • Adding & Editing Language Tags
  • Selecting a Tenant Language
  • Translating Missing Words After an App Update
  • Translate Missing Words
  • Configuring Translator Endpoints
  1. TUTORIALS
  2. App Settings

Language Admin

Learn how to add and edit languages for your tenant(s)

PreviousAuthentication AdminNextSMTP Setup

Last updated 2 months ago

The Reporting Hub is a multi-language application and can be configured to any language. While the application will be installed with English as its default language, you can change the language of your tenant in two easy steps:

See below for a detailed walk-through of each step.

Adding & Editing Language Tags

  1. Select your profile picture or name to access the Admin Settings menu.

  2. Select App Settings.

  3. Select the Language Editor tab.

  4. From the drop-down menu, select Add Language.

  5. The Add New Language pop-up will appear, prompting you to enter both a Language Code and a Language Name. In the first box, you will need to enter a two-letter ISO 639-1 code. (A full list of ISO 639-1 codes can be found .) For example, if you want to add Spanish as an option, your ISO 639-1 code will be es. In the second box, type the language name you want displayed on your drop-down menu. Then, select Add New Language.

  6. From the drop-down menu, select the language you’ve added. This will bring up a list of every language tag associated with the Reporting Hub interface.

  7. To change these tags to the language you’ve selected, click the Options button beside the dropdown and then Translate missing words. This may take several minutes.

  8. Once the translation is complete, look over the tags to make sure you’re satisfied with the results. Any language tag translation can be edited manually. To do so:

    1. In the row of the tag you want to edit, select the Edit icon () from the right-hand column.

    2. Enter your preferred translation, and click Save.

  9. Any language you’ve added can be deleted by: selecting it from the dropdown list, then selecting Options, and then Delete Selected Language.

Good to Know: Manually editing language tags can be useful, as the auto-translate function can be limited in its accuracy. For example: ISO 639-1 provides only one option for English, using American spelling.

If you’re setting up a new language for a regional client, you may wish to make manual changes to reflect a more natural language translation for native speakers. Rather than scrolling through every language tag, you can use the search bar to enter specific words that have discrepancies, and focus on editing those.

Selecting a Tenant Language

Note: To change the language settings for your sub-tenants, you'll need either an Enterprise or Commercial-tier subscription.

Once you’ve added a language using the Language Tags Editor, you’re ready to change the language of your Reporting Hub display.

  1. Select your profile picture or name to access the Admin Settings menu.

  2. Select App Settings.

  3. Select the Tenant Admin tab.

  4. From the list of tenants, select the ellipsis (...) next to the tenant you want to edit and then select Edit.

  5. In the Edit Tenant menu, select your preferred language from the Language dropdown.

  6. Select Save.

Good to Know: The Language menu will only display languages you’ve added using the Language Tags Editor.

Translating Missing Words After an App Update

New language tags may be added to the Reporting Hub as we update and add new features. These tags will not automatically be translated to whichever languages you have added to your Language Editor, and so you may be missing translations after an update.

For example, we added the Icelandic language to our Language Editor before several major updates. Hence, we are missing several translations for page tags; you can see where there are blanks under the Icelandic header.

Translate Missing Words

  1. Select the language you'd like to translate the missing phrases for from the Language dropdown.

  2. Select Options.

  3. Select Translate missing words. It may take several minutes to obtain the translations, depending on how many translations are missing.

  4. The missing translations have been added. Any tags you've manually edited will not be overwritten.

Configuring Translator Endpoints

By default, the Reporting Hub will use the public endpoint for calling Translator Service APIs. If your Translator uses a private endpoint, you'll have to add it to your Reporting Hub's app settings.

  1. Copy your Translator's private endpoint from the Azure portal.

    1. You can find it by navigating to your Translator service and selecting Keys and Endpoint under Resource Management.

    2. Under Web API, copy the value for Text Translation.

  2. In the Azure portal, navigate to your App Services list; you can use the search bar at the top of the page.

  3. From the list of App Services, select your Reporting Hub app service.

    1. If you deployed your Reporting Hub app to a specific slot on your app service, then expand the Deployment menu in the left menu pane; select Deployment slots; and select the desired slot.

  4. On the left menu, expand the Development Tools menu and select Advanced Tools.

  5. Select Go -> and Kudu tools will open in a new tab.

  6. On the Kudu page, in the top menu, select Tools and Zip Push Deploy.

  7. Scroll down in the file list and find appsettings.json. Select the pencil icon next to it.

  8. In the text editor on the page, find "translatorurl" and replace the text beside it with the private endpoint value from step 1. Ensure the value is inside quotation marks.

  9. Select Save.

here
Selecting Add Language from the dropdown
Add new language screen
Translate missing words
Selecting the edit icon of the first language tag
Editing a language tag
Delete selected language
Selecting a tenant language in the Edit Tenant menu
Missing translations
Translate missing words
Missing translations have been added