Forum Discussion

slvya's avatar
slvya
Copper Contributor
Dec 04, 2023

Any help with Microsoft 365 training page language issue?

Hello everyone,

 

I have a question regarding Microsoft 365 attack simulation training. On the landing page, we choose the option "Use landing pages from the library" and add the necessary languages. However, the dropbox is not functioning; the page loads, but the language is not being translated. What could be the issue?

 

We don't have the option to "Create your own landing page," otherwise, we would do it ourselves.

 

We are using Edge as our browser. In the code, we have only added the language selection; nothing else has been modified.

 

Could anyone help? I would appreciate any feedback!

Here's the code:

 

 

<div> <select id="languages" name="languages">
<option value="zh-cn">Chinese (Simplified)</option>
<option value="zh-tw">Chinese (Traditional)</option>
<option value="cz-cz">Czech</option>
<option value="en-us" selected="">English</option>
<option value="fr-fr">French</option>
<option value="de-de">German</option>
<option value="it-it">Italian</option>
<option value="ja-jp">Japanese</option>
<option value="ko-kr">Korean</option>
<option value="pt-br">Polish</option>
<option value="pt-br">Portuguese</option>
<option value="ru-ru">Russian</option>
<option value="es-es">Spanish</option>
</select> </div>

 

 

 

In the code below, translate.js is then invoked.

microsoft defender for office 365

1 Reply

Sort By
  • ExMSW4319's avatar
    ExMSW4319
    Steel Contributor
    Dec 04, 2023

    slvya 

    When composing an attack in the simulator wizard, you should have the choice of using a landing zone from the MS library or or using a custom URL. See the attached picture.

     

    A year ago I found that landing page language selection was unreliable. I worked around that by writing a multi-lingual SharePoint site with a page for each language I needed to attack in. The attacks were sent out by region so I could choose the appropriate page for each region. The bug I experienced was notionally fixed but I must admit I am more confident using my own pages. The only drawback is that I cannot use payload indicators (which are not easy to edit in complex payloads anyway).

Resources