SharePoint multilingual sites

For multinational organisations, an intranet that works in English only — when 40% of employees don't have English as a first language — is a problem. SharePoint multilingual sites let you deliver content in multiple languages with one underlying site and per-language pages.

How multilingual works in modern SharePoint

A multilingual SharePoint site has:

• A default language — the primary site language.
• Alternative languages — additional languages enabled per site.
• Per-page translations — each page can have a translation in each alternative language.
• Per-language navigation — top navigation items translated.
• Per-language site display — users see the site in their preferred language based on browser settings or explicit selection.

Configured per site in Settings → Site information → Language settings. Once enabled, page authors can create translations of any page; users automatically see the right one.

Workflow for content authors

A typical authoring flow:

1. Author creates a page in the default language (e.g., English).
2. From the page settings, request translation — creates draft pages in the enabled alternative languages.
3. Translator (or AI translator) translates the draft.
4. Publish each language version — they go live independently.
5. Update navigation — translated nav items map to the right language's pages.

For tenants with Microsoft Translator integration, AI-translated drafts can be a starting point — translator reviews and refines rather than translating from scratch.

What's translated vs not

Translation happens at the page level — the page's title, content, and metadata. Library and list content (the actual documents and items stored in SharePoint) is not auto-translated by SharePoint — they exist in whatever language they were authored in.

For files stored in libraries, options include:

• Separate libraries per language — Documents (EN), Documents (FR), etc.
• Single library with language metadata — each file tagged with its language; views filter accordingly.
• External translation services for documents that need to be available in multiple languages.

Hub and global navigation

For hub sites, hub navigation translations are configured at the hub level — users associated to the hub see hub nav in their language. The same applies to home site navigation at the global level.

This means a multinational intranet with localised hubs delivers a coherent experience to users regardless of language.

Limitations and operational considerations

• Not all SharePoint features are fully multilingual — some settings, certain admin surfaces, web part configurations have English-only UIs even on translated sites.
• Performance — sites with many languages and many pages produce many page artefacts; not usually a problem but worth knowing.
• Authoring discipline — translations get out of sync if authors update one language without the others.
• Cultural considerations — translation isn't just literal; some content needs localisation (legal disclaimers, examples, imagery).

When to invest

Multilingual SharePoint is most valuable for:

• Multinational organisations with significant non-English-first-language populations.
• Public-sector and regulated industries with legal multilingual requirements.
• Customer-facing intranet portions where the audience expects native language.

For organisations where English is the universal corporate language and all employees speak it fluently, monolingual SharePoint is simpler and equivalent in utility.

When you do invest, plan the translation operating model alongside the technical setup. Who translates? On what cadence? What's the quality bar? Without those answers, multilingual capability becomes shelf-ware.