Automatic Page Translator - FAQ
Here you will find the most frequently asked questions about automated translation in SharePoint Online.
Automated translation
Why should I use the automated translation solution?
Manually translating intranet content is very time-consuming. This is where our solution helps to save time and therefore costs.
For example, automated translation is worthwhile if you need to translate into many different languages for which translators may or may not be available. It can be said that the more national languages are supported, the more worthwhile machine translation is.
The solution can also be worthwhile for a small number of languages because it relieves the manual translator of work and makes him more of a reviewer.
What does automatic translation of an article mean?
Automated machine translation of articles created in SharePoint Online. Their content is sent to a translator service in the Microsoft cloud, where it is analysed and processed. These translated articles can then be reviewed and published on the intranet.
Can specific words be excluded from the automated translation?
The translator service used must offer this function. In the case of Microsoft Translator, a so-called custom translator can be used for this purpose. However, additional training is required for its use.
What is the difference to browser plugins for translation?
Some browsers have functions or installable plug-ins for machine translation of displayed content for the reader.
Here, the content of the currently displayed article is sent to a translator service in the cloud by the reader manually calling up the function and is then machine-translated and displayed in the browser.
This does not change or add anything to the original article on the intranet!
Which translator service is used?
The solution uses Microsoft Translator. This is also used by Microsoft itself for automated translation in the services. More information on this can be found here on the Microsoft website. In particular, more details on the compliance of this service can be found here.
Can alternative machine translation services be used?
The solution is architecturally designed in such a way that it can work relatively easily with alternative machine translators if they offer an interface (API). One example is DeepL.
Are there any costs for machine translation?
Yes, good quality automated translation services are chargeable! The costs incurred are significantly lower than labour costs for manual translation.
Microsoft Translator charges per character based on the amount of text translated. This means that for the word „OTTO“ with 4 letters in 2 foreign languages, 8 characters are charged.
Microsoft Translator currently offers a free entry-level version with a monthly free quota of 2 million characters. Assuming a text length of 800 words per intranet article, this amounts to 8480 characters in the German language (according to Duden, an average of 10.6 letters per word). If we add the punctuation marks here, as these are also processed, and round up to 8,600 characters per article, the free quota is sufficient for approx. 116 articles in two foreign languages.
What is important here in relation to data protection?
Names of employees are usually published on the intranet. These are personal data within the meaning of the GDPR. Therefore, the intranet must be included in the record of processing activities (Article 30) even without automated translation.
A semi- or fully automated translation of these articles on the intranet in an external translation service in the cloud also constitutes so-called order processing (Article 28).
Therefore, please consult your data protection officer!
Multilingual content
How does multilingual content work in SharePoint Online?
As a matter of principle, SharePoint Online physically stores separate pages in the CMS for each language when using multilingual content.
This physical separation between, for example, a German article and its English counterpart results in the following disadvantages:
- The access statistics are shown separately.
- The number of likes is shown separately.
- Comments on articles by readers are displayed separately.
How is multilingual content delivered to readers?
Support for multilingualism in relation to content on the intranet in SharePoint Online works on the basis of the language set in the user's browser. SharePoint Online reads the favoured language from the browser settings at the time of loading. An additional language setting in the M365 tenant for the readers is not necessary for this!
If the content is published in this language, it is displayed to the reader in this language accordingly. If the content is not available in the user's language, the content is displayed in the configured default language of the respective website.
Which languages are supported?
The supported languages result from two technical framework conditions:
- SharePoint Online must support the language -> see official article from Microsoft
- Microsoft Translator must be able to translate the languages -> see official article from Microsoft
This means that if the requested language is listed in both articles linked above, it is supported.
How is it determined for which languages the automated translation should be carried out?
The automated translation takes place in every language for which a translation is ordered by the respective editor. The languages are configured once in the SharePoint Online website.
Editorial workflow
How does the editor start the translation process?
The process is started by creating a translation of a news item. This is done via the „Translation“ button in the ribbon of the news item. The same applies to pages that are not news items.
The „Translation“ page column then opens, in which the target language is selected. After the editor clicks on „Create“ in the desired target languages, the automatic translation process begins.
See the official article on the translation of Site Pages in SharePoint Online (source: Microsoft).
In addition, the editor receives a confirmation email when the automatic translation process has been started.
How quickly does the automatic translation mechanism work - when are the articles translated?
This depends on the length of the article. Normally, however, the automatic translation does not take longer than one minute.
Will the translated articles be published immediately?
No, the translated articles are in draft mode at the end of the translation process so that they can be checked again by a translator/editor.
How does the editor find out that his article has been translated?
By an e-mail that the author receives after the translation. They receive a confirmation email when the automatic translation process has been started and an email notification when the translation is complete.
What happens if an already published article is updated again by an editor?
The workflow is started as soon as a new translation file of the page is generated by SharePoint Online. After an already published article has been adapted, the adaptation must be made manually in the translated article. Microsoft does not provide for automatic synchronisation or notification of the translation file if an article that has already been published is subsequently changed.
Will the original layout of the article be retained?
Yes, without restriction.
Are article comments translated by readers?
No, once the article has been published, no further automatic actions are carried out.
Are texts translated into tables?
If the editors have created a table using the standard text web part and the cells contain texts, these are translated.
Technical framework conditions
What are the basic requirements in a website in SharePoint Online for automated translation to work?
The additionally supported languages for the content must be configured in the respective SharePoint Online website with on-board tools (further information in the Microsoft help article) - no additional configuration is required in the solution.
Note: Assigning translators to each target language is not necessary for the use of automated translation - but it is not harmful either.
How is the source language recognised for automated translation?
The translation service automatically recognises the source language of the text to be translated.
How is the target language for the automated translation recognised?
The solution automatically recognises the required target language based on technical parameters in the metadata of the intranet article. This metadata is created automatically by SharePoint Online. It is not necessary/possible to specify the target language manually.
What are the limitations of automated translation in SharePoint Online?
Elements (so-called web parts) within pages and news items are not automatically translated by the solution. Texts configured by editors in web parts are also not translated.
Does the translation solution change anything in the intranet sites in SharePoint Online?
No, no adjustments/changes will be made to the websites.
What technology is the solution based on?
The solution was developed on the basis of the Microsoft Power Platform and consists of a solution for PowerAutomate.
We would like to use the solution on several websites. What needs to be considered?
A separate cloud flow (with trigger) must be created for each website in SharePoint Online. This then listens for the creation of new translation files within the specified website. This is a technical framework requirement by Microsoft PowerAutomate.
How do I install the solution in my tenant?
Log in to PowerAutomate and switch to the „Solutions“ tab. There you can import the solution provided by JASP using the „Import Solution“ button.
When importing, environment variables are created in addition to the cloud flows, which you fill with the appropriate values for your environment:
- Email address of the developer/IT administrator responsible for maintaining your flows. In the event of an error, reports and debug information will be sent to this e-mail address
- The URL of your regional data centre
- The name of your tenant
Is the solution compatible with Viva Amplify?
Yes: Viva Amplify creates the news articles in a specifically selected website in SharePoint Online when publishing. Viva Amplify currently (May 2024) has no support for multilingual news articles. This means that manual work by the editors in the website is necessary again. The APT is installed there and works in the same way as usual.
