Configure the name pronunciation feature in the Microsoft 365 admin center

Last December, Microsoft announced a name pronunciation feature, but administrators could not configure it via Microsoft Graph. The API returned an error or was not ready. During my tests, the default configuration was True, and the name pronunciation feature available to all my users.

Name pronunciation feature in Teams and Outlook
Name pronunciation feature in Teams and Outlook
Read:  Name pronunciation on the Microsoft 365 profile card

Now, Microsoft has added the admin toggle in the Microsoft 365 admin center, meaning admins can configure the feature without PowerShell. The admin toggle should be available since Friday, 18 April.

Administrators can decide whether to display pronunciations that users set up in their profile cards. To enable the display of user-created name pronunciations, set the isEnabledInOrganization property of the namePronunciationSettings object to true. When this property is set to true, pronunciation is displayed for everyone within the organization. When this property is set to false, pronunciation not displayed for anyone within or outside the organization. The default setting is false.

Your account must be a Global administrator for the configuration. You can find it in the Microsoft 365 admin center > Org settings > Security & privacy > Name pronunciation.

Configure the name pronunciation feature in the M365 admin center
Configure the name pronunciation feature in the M365 admin center

Also, the namePronunciationSettings Graph API is now working.
In the meantime, the name pronunciation feature is no longer available for my users compared to last December. Microsoft changed the configuration. The API confirms that the configuration state is now False.

PowerShell
Import-Module Microsoft.Graph.Authentication
Connect-MgGraph -Scopes "PeopleSettings.Read.All"

$Url = "https://graph.microsoft.com/beta/admin/people/namePronunciation"
$Result = Invoke-MgGraphRequest -Method GET -Uri $Url -ContentType "application/json"
$Result

Name pronunciation feature is now disabled by default
Name pronunciation feature is now disabled by default

Admins can simply change the value to True (Enabled for all users) or False (Disabled for all users), as described in the documentation.

PowerShell
Connect-MgGraph -Scopes "PeopleSettings.ReadWrite.All"

$Body = @"
{
  "isEnabledInOrganization": true
}
"@

$Url = "https://graph.microsoft.com/beta/admin/people/namePronunciation"
Invoke-MgGraphRequest -Method PATCH -Uri $Url -Body $Body -ContentType "application/json" 
Share
Avatar photo

Tobias Asböck

Tobias is a Senior System Engineer with around ten years of professional experience with Microsoft 365 products such as SharePoint Online, SharePoint Premium, OneDrive for Business, Teams Collaboration, Entra ID, Information Protection, Universal Print, and Microsoft 365 Licensing. He also has 15+ years of experience planning, administering, and operating SharePoint Server environments. Tobias is a PowerShell Scripter with certifications for Microsoft 365 products. In his spare time, Tobias is busy with updates in the Microsoft 365 world or on the road with his road bike and other sports activities. If you have additional questions, please contact me via LinkedIn or [email protected].

2 Responses

  1. Charlie Magne says:

    Hi! Tobias, Thank you for the information regarding this new feature of Microsoft.

    We still not seeing the admin toggle on our Microsoft admin Center in our production environment.

    In our testing environment, I enabled the feature using the script you’ve mentioned above but the microphone icon is not showing up in Teams and Outlook.

    • Hello Charlie, thanks for the feedback.
      I’m currently using Teams in Public Preview, and my tenant is configured with Targeted Release. I’ve noticed the name pronunciation feature is available in both Teams and Outlook (profile card).
      What configuration are you using in your test tenant? Are you on Public Preview or Targeted Release for selected users?

      I’m not entirely sure, but MC917748 states that the 100% production rollout should be completed by the end of June. Microsoft may be experiencing a delay, and the post may be updated soon. Also, are you using a “special tenant type,” such as Education, GCC, GCC High, or DoD?

Leave a Reply

Your email address will not be published. Required fields are marked *