Your issue with language inconsistency in Azure/Identity/Entra invitations sent to external users is indeed a challenge but not necessarily a unique one. Azure/Identity/Entra (formerly known as Azure AD B2B) allows inviting external users to collaborate in your tenant, and the language used for these invitations can be influenced by several factors.
Here are some steps you can take to try and resolve this issue:
1. Check Azure AD Language Settings
- Ensure that the default language for your Azure Active Directory is set to English. This setting might influence the language used for invitation emails.
2. Inspect the User's Language Preference
- Azure/Identity/Entra might be picking up the language preference from the invited user’s Microsoft account settings. If the user's Microsoft account is set to Dutch, the invitation might default to this language. Unfortunately, you have limited control over the user's personal account settings.
3. Examine Your Script or Invitation Method
- If you're using a script or automated process to send out these invitations, ensure that the script isn't setting the language preference based on certain criteria.
4. Global Language Settings in Office 365
- Check the language settings in the Office 365 Admin Center. Sometimes, the language settings in Office 365, which Azure/Identity/Entra is a part of, can influence such behaviors.
5. Utilize PowerShell
- You can use PowerShell to explicitly set the language for each invitation. While this requires more effort, it gives you complete control over the language used in the invitation. The PowerShell cmdlet to send an invitation can include a parameter to specify the language.
6. Microsoft Support
- If you've tried all the above and the issue persists, it may be beneficial to contact Microsoft Support directly. This issue might be related to how Azure/Identity/Entra handles localization and language preferences, which could require a more in-depth examination by the Azure team.
PowerShell Example:
If you choose to use PowerShell, here’s a basic example of how you can send an invitation:
$Invitation = New-AzureADMSInvitation -InvitedUserEmailAddress "user@example.com" -InviteRedirectUrl "https://myapps.microsoft.com" -SendInvitationMessage $true -InvitedUserMessageInfo @{messageLanguage="en-US"}
Replace user@example.com
with the email of the user you're inviting and https://myapps.microsoft.com
with the URL to your application or resource.
Keep in mind, while these steps may address the issue, the behavior you're experiencing could be part of how Azure/Identity/Entra's localization features are designed to work, particularly concerning personal Microsoft accounts.
Accept the answer if the information helped you. This will help us and others in the community as well.