Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Enabling Multi-Language Support in the Work 365 Self-Service Portal

Applies to: Work 365 Self-Service Portal (Power Pages)
Audience: Admins, System Customizers

Overview

You can run the Work 365 Self-Service Portal in multiple languages. Enabling a new language is a two-platform task: first in Dataverse/Power Platform, then in Power Pages.
Important change: Initialization is no longer used to apply translations. To add a new language, you must manually re-import the Work 365 Portal solution so the language resources (labels, strings, metadata) are installed.

References:

  • Portal/solution concepts & supported languages in Work 365 (Work 365)

  • Enabling languages in your environment (Microsoft Learn)

  • Enabling multi-language in Power Pages (Microsoft Learn)

  • Work 365 – manual portal solution import (Work 365)

Key Concepts

  • Dataverse languages: Control which languages are available to model-driven apps and data. A language must be enabled here first.

  • Power Pages site languages: Control which languages the website can render. Enable the same languages you enabled in Dataverse.

  • Work 365 Portal solution resources: Work 365 ships managed translation resources. Re-importing the Work 365 Portal solution adds resource files for newly enabled languages.

  • Fallback behavior: If a label isn’t translated, the portal falls back to the site default (typically English).

How It Works

  1. Enable a language in Dataverse → the language becomes available to the platform.

  2. Enable the same language in Power Pages → the site can serve pages in that language.

  3. Re-import the Work 365 Portal solution → Work 365’s translated labels/resources for that language are layered into the site.

The portal resolves UI text using: User UI language → Site default → English fallback.

Prerequisites

  • System Administrator (environment) and Maker permissions to import solutions.

  • Target language is enabled in Dataverse (per Microsoft Learn).

How To Enable a New Language (Updated Sequence)

  1. Enable the language in Dataverse
    Power Platform Admin Center → Environments → your environment → Settings → Languages → enable the target language → Save.

  2. Enable the language in Power Pages
    Power Pages → select your portal → Set up → Languages → enable the same language for the website.

  3. Apply Work 365 translations by re-importing the portal solution
    Power Apps / Dynamics → Solutions → Import → select the Work 365 Portal solution package (current package from Work 365) → run import → wait for Success.

  4. Publish / refresh the portal
    In Power Pages, Sync configuration, then Restart the site (or recycle from the admin blade).
    Clear browser cache and test with a user whose UI language is set to the new language.

  5. Verify translations
    Browse key pages (Home, Subscriptions, Invoices). Confirm labels, lists, and forms render in the selected language. Untranslated items will fall back to English.

Use Cases

  • Launch a Spanish or French customer experience without duplicating sites.

  • Regional portals requiring localized invoice/subscription wording.

  • Gradual rollout: enable language, test thoroughly, then make it the site default later.

Troubleshooting

  • Symptom: Language doesn’t appear in the site Likely Cause: Not enabled in Dataverse Fix: Enable in Dataverse first, then in Power Pages; re-import solution.
  • Symptom: Some labels remain in English Likely Cause: No resource present in Work 365 layer Fix: Confirm the language is supported in your Work 365 portal package; keep package current and re-import.
  • Symptom: Custom content not translated Likely Cause: Web Pages/Web Link Sets/Content Snippets lack localized variants Fix: Create language variants for these records in Portal Management.
  • Symptom: Changes not visible Likely Cause: Cache Fix: Sync + Restart site; clear browser cache / hard refresh.
  • Symptom: Solution import blocked Likely Cause: Dependencies/permissions Fix: Import as System Administrator in the correct environment; ensure all Work 365 base solutions are present.

Best Practices

  • Order matters: Dataverse → Power Pages → Re-import Work 365 Portal solution → Sync/Restart.

  • Keep your Work 365 portal package current to receive updated translation files.

  • For custom UI text, store strings in Content Snippets and create localized entries.

  • Test in a sandbox and validate page-by-page before switching any site defaults.

  • Document which languages are enabled and the solution version that delivered translations.

Additional Resources

  • Work 365: Portal & language support (Work 365)

  • Microsoft Learn: Enable/disable languages in Dataverse

  • Microsoft Learn: Configure languages for Power Pages

  • Work 365: Manual portal solution install/import (Work 365)

FAQs

Do I have to re-import the Work 365 Portal solution every time I toggle a language?
Only when adding a new language. Toggling site default or disabling doesn’t require re-import.

Will re-importing overwrite my customizations?
No for managed components. Re-import adds/updates managed translation layers. Your unmanaged customizations remain, but always back up before imports.

How do I localize email templates for the portal?
Use Email Templates (Dynamics) and create language-specific variants; reference them in your portal flows.

Can I set a different default language per account or user?
Users can set their personal UI language; the site also has a default language. Content resolves per the user → site fallback model.

Summary

To enable a new portal language: turn it on in Dataverse, enable it in Power Pages, then re-import the Work 365 Portal solution to apply translations. Finally, sync/restart the site and verify pages. Follow the sequence precisely for reliable, localized experiences.