{"id":16684,"date":"2026-06-04T08:01:49","date_gmt":"2026-06-03T23:01:49","guid":{"rendered":"https:\/\/m365jp.net\/?p=16684"},"modified":"2026-06-04T08:04:11","modified_gmt":"2026-06-03T23:04:11","slug":"mc1338827-microsoft-teams-voicemail-transcription-service-migration-and-new-languages","status":"publish","type":"post","link":"https:\/\/m365jp.net\/index.php\/2026-06-04-mc1338827-microsoft-teams-voicemail-transcription-service-migration-and-new-languages","title":{"rendered":"MC1338827 | Microsoft Teams: Voicemail transcription service migration and new languages"},"content":{"rendered":"<div class=\"postie-post\">\n<div>\n<hr>\n<table id=\"section\">\n<tbody>\n<tr>\n<th width=\"95%\">MC1338827 | Microsoft Teams: Voicemail transcription service migration and new languages<\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n<hr>\n<table id=\"data\">\n<tbody>\n<tr>\n<th>Classification<\/th>\n<td>planForChange<\/td>\n<\/tr>\n<tr>\n<th>Last Updated<\/th>\n<td>06\/03\/2026 22:55:08<\/td>\n<\/tr>\n<tr>\n<th>Start Time<\/th>\n<td>06\/03\/2026 22:55:01<\/td>\n<\/tr>\n<tr>\n<th>End Time<\/th>\n<td>07\/25\/2026 07:00:00<\/td>\n<\/tr>\n<tr>\n<th>Message Content<\/th>\n<td>\n<p><b>[What and Why]<\/b><\/p>\n<p>Starting in June 2026, <b>Microsoft Teams voicemail transcription<\/b> will transition to  <b>Azure LLM Speech <\/b>using the <b>Fast Transcription API<\/b>. This update improves transcription accuracy, processing speed, and reliability, while introducing  <b>automatic language detection<\/b> and<b> support for 14 additional languages<\/b>. We expect new languages to be available for in all Azure regions by the end of July.<\/p>\n<p>This enhancement helps organizations better support multilingual users and increases the value of  <b>Microsoft 365 Copilot <\/b>by enabling richer processing of voicemail content through transcripts. In the coming three months, M365 Copilot is also expected to recognize voicemail as a distinct message type, making it easier to identify and work with these   messages.<\/p>\n<p><b>[Rollout Schedule]<\/b><\/p>\n<p style=\"margin-left: 25px\"><b>General Availability (Worldwide): <\/b>We will begin rolling out in<b> mid-June 2026  <\/b>and expect to complete by <b>late July 2026.<\/b><\/p>\n<p><b>[Impact on Your Organization]<\/b><\/p>\n<p><i>Who is affected<\/i><\/p>\n<ul>\n<li>Organizations using <b>Microsoft Teams voicemail transcription<\/b><\/li>\n<li>All users with voicemail transcription enabled via policy<\/li>\n<\/ul>\n<p><i>Platforms\/Services<\/i><\/p>\n<ul>\n<li><b>Microsoft Teams<\/b><\/li>\n<li><b>Exchange Online voicemail<\/b><\/li>\n<li><b>Microsoft 365 Copilot <\/b>(indirectly enhanced)<\/li>\n<\/ul>\n<p><i>What will happen<\/i><\/p>\n<ul>\n<li>Voicemail transcription will migrate to <b>Fast&nbsp;Transcription API Azure LLM Speech<\/b>&nbsp;automatically.<\/li>\n<li><b>Automatic language detection<\/b> will be <b>enabled for voicemail messages<\/b>.<\/li>\n<li>Transcription accuracy and processing speed will improve.<\/li>\n<li><b>Support for 14 additional languages<\/b> will be added.<\/li>\n<li><b>New languages are enabled by default <\/b>for tenants with transcription turned<b> ON<\/b>.<\/li>\n<li>Existing voicemail policies remain unchanged.<\/li>\n<li>No change to the secure and compliant voicemail experience.<\/li>\n<\/ul>\n<p><u>Language support<\/u><\/p>\n<ul>\n<li><b>Currently supported (9):<\/b>\n<ul>\n<li>English (en-US)<\/li>\n<li>Spanish (es-ES)<\/li>\n<li>Portuguese (pt-BR)<\/li>\n<li>French (fr-FR)<\/li>\n<li>German (de-DE)<\/li>\n<li>Italian (it-IT)<\/li>\n<li>Dutch (nl-NL)<\/li>\n<li>Chinese (zh-CN)<\/li>\n<li>Japanese (ja-JP)<\/li>\n<\/ul>\n<\/li>\n<li><b>New languages (14):<\/b>\n<ul>\n<li>Arabic (ar-SA)<\/li>\n<li>Czech (cs-CZ)<\/li>\n<li>Danish (da-DK)<\/li>\n<li>Finnish (fi-FI)<\/li>\n<li>Hebrew (he-IL)<\/li>\n<li>Hindi (hi-IN)<\/li>\n<li>Hungarian (hu-HU)<\/li>\n<li>Korean (ko-KR)<\/li>\n<li>Norwegian Bokm\u00e5l (nb-NO)<\/li>\n<li>Polish (pl-PL)<\/li>\n<li>Russian (ru-RU)<\/li>\n<li>Swedish (sv-SE)<\/li>\n<li>Thai (th-TH)<\/li>\n<li>Turkish (tr-TR)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><b>[Action Required \/ Recommendations]<\/b><\/p>\n<p>No action required.&nbsp; We do not expect any issues during the transition of voicemail transcription to Fast Transcription API.&nbsp;<\/p>\n<p>Recommended actions:<\/p>\n<ul>\n<li>Review voicemail transcription is enabled in <i>your organization via Teams Admin Center Voicemail Policies<\/i>.<\/li>\n<li>Inform helpdesk and users about improved transcription quality and expanded language support.<\/li>\n<li>Update internal documentation if you reference supported voicemail languages.<\/li>\n<li>Monitor user feedback after rollout, especially in <i>multilingual environments<\/i>.<\/li>\n<\/ul>\n<p>Admin control:<\/p>\n<ul>\n<li>Voicemail transcription can be managed via Teams Voicemail Policies.<\/li>\n<\/ul>\n<p><b>Learn more:&nbsp;<\/b><\/p>\n<ul>\n<li><a href=\"https:\/\/learn.microsoft.com\/azure\/ai-services\/speech-service\/llm-speech?tabs=new-foundry%2Cwindows&amp;pivots=ai-foundry\" target=\"_blank\">LLM Speech for speech transcription and translation |Speech Service | Microsoft Foundry | Microsoft Learn<\/a><\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/microsoftteams\/manage-voicemail-policies\" target=\"_blank\">Manage Cloud Voicemail policies for your users | Microsoft Teams | Microsoft Learn<\/a><\/li>\n<\/ul>\n<p><b>[Compliance considerations]<\/b><\/p>\n<table class=\"table table-bordered\">\n<tbody>\n<tr>\n<td><b>Question<\/b><\/td>\n<td><b>Answer<\/b><\/td>\n<\/tr>\n<tr>\n<td>Does the change alter how existing customer data is processed, stored, or accessed (such as documents, emails, chats, etc.), and if so, how and to what extent?<\/td>\n<td>Yes. Voicemail audio data will be processed using Azure LLM Speech via the Fast Transcription API, replacing the older transcription LLM model that is being deprecated.  <\/p>\n<p>  There are no changes to voicemail storage or compliance controls. The underlying processing flow remains unchanged; only the transcription LLM model is being upgraded.<\/td>\n<\/tr>\n<tr>\n<td>Does the change introduce or significantly modify AI\/ML or agent capabilities that interact with or provide access to customer data, and if so, summarize the changes?<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Does the change provide users any new way of interacting with generative AI, and if so, how?<\/td>\n<td>No<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>MC1338827 | Microsoft Teams: Voicemail transcription service migration and new languages Classification planFo [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-16684","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/16684","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/comments?post=16684"}],"version-history":[{"count":0,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/16684\/revisions"}],"wp:attachment":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/media?parent=16684"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/categories?post=16684"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/tags?post=16684"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}