Forum Discussion
Enable per‑user language selection for phishing simulation emails and landing pages
We use Attack Simulation Training to deliver phishing simulations to a global, multilingual user base. While Microsoft Defender supports multi‑language content, phishing simulation emails and landing pages are currently delivered in a single selected language per campaign.
We are requesting a feature that allows phishing simulation emails and associated landing pages (including credential‑harvest pages) to automatically render in each user’s preferred language, based on:
- Outlook mailbox language settings, and/or
- Microsoft Entra ID user language preferences
This capability would:
- Improve realism and accuracy of phishing simulations
- Ensure users experience simulations in the same language they normally work in
- Improve behavioral measurement in global organizations
- Reduce the need to create and manage multiple parallel simulations by language
Providing consistent, per‑user language alignment across simulation emails, landing pages, and follow‑up training would significantly enhance the effectiveness of Attack Simulation Training for large, multilingual enterprises.
1 Reply
Hi
While I agree that localization is a nice‑to‑have feature, it’s important to look at the overall use case and objectives of phishing attack simulations.
Localizing phishing simulation emails and landing pages based on users geographic locations is certainly a good practice. However, the value of simulations lies not just in localization, but in how effectively they are targeted, executed, and analyzed.
Phishing simulation emails and landing pages are fully controlled by the administrator, who defines the scope and selects the targeted user groups. In large enterprises, simulations are rarely run across the entire user population simultaneously; instead, they are typically scoped to specific regions or geographic boundaries.
This approach enables better control giving more accurate analysis of user behavior by region than setting it to broad users which results in generic results.
I would definitely welcome Microsoft introducing this feature, as there are multiple use cases that could benefit from it once implemented.
If you find the answer useful and you appreciate my time, please do not forget to like and mark it as a solution 🙂
