Table of Contents
Name Pronunciation Recordings Helps People Get Names Right
Message center notification MC917748 (last update 13 November 2024, Microsoft 365 roadmap item 420329) marks the latest update for the Microsoft 365 user profile card. This time round, users get the opportunity to add a recording of up to ten seconds to help colleagues understand how to pronounce their name correctly (Figure 1).
Microsoft says that the “new feature helps promote diversity by giving working colleagues relevant information about each other. Names are a crucial part of a person’s identity. The incorrect pronunciation of a person’s name can lead to anxiety and offense in some cases. Correctly pronouncing a person’s name helps to create an inclusive environment.” Having the proven ability to make a mess of many peoples’ names in my career, I should find this feature useful.
Once a name pronunciation is available, people can play the recording back by clicking the playback button beside the user’s name (Figure 2).
It’s worth noting that zero checking is performed when a user records their name pronunciation. If they want to call themselves “Mickey Mouse,” they can. Likewise, they can also include something more objectionable in the recording.
General availability is scheduled for mid-January 2025, so the update is currently rolling out. The roadmap item tags the feature for Teams, but MC917748 correctly notes that it’s also available in OWA and the new Outlook for Windows (but not yet in Outlook classic). Over time, I assume that name pronunciation recording will show up everywhere that the Microsoft 365 profile card is visible.
Where Name Pronunciation Recordings are Stored
MC917748 says “Pronunciation data is stored in each user’s mailbox until the user deletes the recording.” Keeping the data in user mailboxes means that pronunciation recordings are available across all clients across all workstations and avoid the kind of problems encountered with Outlook classic where settings are usually held in the system registry.
The non-IPM folders of a mailbox are not visible to normal email clients like Outlook. Applications often use folders in this section to store configuration and other data. The new Outlook for Windows and OWA store many mailbox settings in sub-folders of ApplicationDataRoot, and browsing through those folders with the MFCMAPI utility reveals a folder called ApplicationDataRoot\8c22b648-ee54-4ece-a4ca-3015b6d24f8e\source_sourcenamepronunciation.
The folder holds a single message item containing the pronunciation recording. Figure 3 shows how the item appears in MFCMAPI. In my case, the recording takes 440,728 bytes (approximately 430 KB), which seems about right for a six-second recording.
Enabling Name Pronunciation Recordings
According to MC917748, the feature is off by default, meaning that you don’t see the icons to record and play back name pronunciation recordings in the user profile card. According to an update to MC917748 posted on 29 April 2025, Microsoft announced the deployment of GUI to control the setting for the name pronunciation feature in the Security & Privacy section of Org Settings in the Microsoft 365 admin center (Figure 4).
Programmatic control over name pronunciation is via the Graph namePronunciationSettings resource type with APIs available to Get and Update the setting controlling whether users see the record and playback buttons. For instance, to get the current setting with the Microsoft Graph PowerShell SDK, run these commands:
$Uri = "https://graph.microsoft.com/beta/admin/people/namePronunciation" Invoke-MgGraphRequest -Uri $Uri -Method Get Name Value ---- ----- isEnabledInOrganization True @odata.context https://graph.microsoft.com/beta/$metadata#admin/people/namepronunciation/$entity
To update the setting to disable name pronunciation recordings, construct a hash table containing the new value and update (patch) the resource:
$Settings = @{}
$Settings.Add("isEnabledInOrganization", $false)
Invoke-MgGraphRequest -Uri $Uri -Method Patch -Body $Settings
The setting is on or off for a complete tenant. You cannot enable name pronunciation recording and playback for some mailboxes and not for others. This is very similar to the way that the setting controlling the display of personal pronouns (introduced in March 2023) is managed:
Uri = "https://graph.microsoft.com/V1.0/admin/people/pronouns" Invoke-MgGraphRequest -Uri $Uri -Method Get Name Value ---- ----- isEnabledInOrganization True @odata.context https://graph.microsoft.com/beta/$metadata#admin/people/pronouns/$entity
Unfortunately, the API requests to control the name pronunciation settings currently fail with a 404 not found error. I’m sure that this is a transient problem that Microsoft will sort out soon.
Up to Organizations to Decide
Some consider this kind of addition to the user profile to be so much woke fluff. Others consider getting pronouncing names correctly is an essential part of business discourse. Both are entitled to their opinion. It’s good to have the choice within a world where dealing with different cultures and names is a reality for most.
Learn how to exploit the data available to Microsoft 365 tenant administrators through the Office 365 for IT Pros eBook. We love figuring out how things work.
We consider to turn on pronouns. But we are afraid of lack of modification possibility. Is there any possibility to remove user pronouns from admin perspective?
Nope. Pronouns are user data and aren’t accessible to admins. Admins can turn pronouns on or off for a tenant, but that’s about all they can do.
Man, my boss needs this. His name is mispronounced in 5 different ways, but only a few correctly say his name. Especially vendors, which will not be able to use this.. I think they’ve added this to LinkedIn not so long ago.
If I get a 404 when using invoke-webrequest, does it mean the setting has not been rolled out in my tenant yet?
Do you mean Invoke-MgGraphRequest (which implies that the right permissions are in place to update the policy rather than issuing a simple web request)
sorry, yes. The cmdlets you ran in your article to check the current setting.
$Uri = “https://graph.microsoft.com/beta/admin/people/namePronunciation”
Invoke-MgGraphRequest -Uri $Uri -Method Get
Invoke-MgGraphRequest: GET https://graph.microsoft.com/beta/admin/people/namePronunciation
HTTP/2.0 404 Not Found
Vary: Accept-Encoding
Strict-Transport-Security: max-age=31536000
Link: ;rel=”deprecation”;type=”text/html”
The 404 probably means that the feature hasn’t landed yet in your tenant. Do you use targeted release?
ah. We are on standard release. I thought it probably meant that we didnt have the feature yet. Im new to running invoke-mggraphrequest. so unfamiliar with the errors
Is it possible to download or directly link to the audio files? For use in an email signature, for example.
Nope.
Hi, do you know where the data is stored in Hybrid Exchange when you don’t have migrated the mailbox yet ?
I don’t have a hybrid configuration to test here, but if name pronouncation is supported for hybrid mailboxes (easy to test), I bet the data is stored in the special ‘cloud mailbox’ maintained for on-premises mailboxes for purposes like this.
I like the idea, but from a security perspective don’t like the potential for nefarious use. I’d rather post recording, a generic voice was used, as the key here is pronunciation not personalisation. It also likely constitutes the storing of PII as this is biometric data given it identifies the individual.