# Troubleshooting Teams Phone voicemail that is not reached or not delivered Canonical: https://warmtransfer.net/knowledge/teams-voicemail-troubleshooting Last verified: 2026-10-02 Teams Cloud Voicemail is set up and provisioned automatically for Teams users[^18]. Messages are delivered over SMTP to the user's Exchange mailbox (Exchange Online or Exchange Server), with no separate voicemail store[^18][^46][^47]. Several things can stop a voicemail from arriving: calling policy or per-user settings can keep calls away from voicemail, Exchange mail flow rules can filter messages, and header or access-policy problems can hide messages from Teams[^1][^56][^13][^10][^5]. ## How delivery works Cloud Voicemail messages are delivered to and stored in the user's Exchange mailbox, and Outlook and Teams read them through the mailbox APIs[^46]. Teams Cloud Voicemail does not support third-party email systems, and it deposits voicemail only in an Exchange mailbox[^19]. A Microsoft Teams Phone license is not required for Cloud Voicemail[^18]. - Cloud Voicemail email is sent from noreply@skype.voicemail.microsoft.com[^43]. - Voicemail messages generated by Cloud Voicemail are not DKIM-signed[^21]. - For PSTN calls, the voicemail FROM address is not RFC-compliant, so Microsoft advises third-party mail filters to evaluate the P1 sender address instead[^49]. WarmTransfer's reading of the sources is that a Teams user with no Exchange mailbox (neither an Exchange Online mailbox nor a correctly connected Exchange Server mailbox) cannot receive Cloud Voicemail messages, because SMTP delivery to the mailbox is the only deposit path[^16]. ## When the caller never reaches voicemail ### Per-user settings If a user's per-user voicemail setting (VoicemailEnabled) is false, Cloud Voicemail is unavailable for that user and no voicemail is recorded[^56]. By default, a user's call answering rule is Regular Voicemail and voicemail is enabled[^8]. The voicemail CallAnswerRule accepts these values: DeclineCall, PromptOnly, PromptOnlyWithTransfer, RegularVoicemail and VoicemailWithTransferOption[^4]. Two call answering modes stop the caller from leaving a message[^35]: - With "Play an outgoing message to the caller", only the greeting plays and the caller cannot leave a voicemail[^35]. - With "Service declines the call with no message", the caller is disconnected[^35]. The voicemail TransferTarget applies to PromptOnlyWithTransfer and VoicemailWithTransferOption[^52]. It must be the SIP URI of another user in the organisation, and it accepts a phone number only for Enterprise Voice-enabled users[^52]. ### Calling policy In the Teams admin center calling policy, "Voicemail for inbound calls" offers On, Off and Let users decide, and Let users decide is the default[^48]. - **AllowVoicemail set to AlwaysDisabled**: calls are never routed to voicemail, and voicemail is not offered as a forwarding or unanswered target in Teams[^1]. - **AllowVoicemail set to AlwaysEnabled**: unanswered calls always go to voicemail after ringing 30 seconds, and the Teams client hides the option to manage unanswered calls[^2]. - **InboundPstnCallRoutingTreatment set to Voicemail**: inbound PSTN calls go straight to voicemail without being presented. This setting overrides other forwarding settings, and it disconnects the call if voicemail is not enabled[^11]. - **BusyOnBusyEnabledType set to Unanswered**: the user's unanswered settings, such as voicemail, apply to new calls while the user is already on a call[^3]. ### Unanswered-call timing and admin visibility If neither the user nor an admin changes call answering rules, unanswered calls go to voicemail after 30 seconds[^7]. In that default state, Teams admin center and PowerShell nonetheless show the unanswered target as none with a 20-second delay[^7]. Admin configuration of a user's call forwarding and unanswered settings requires a Teams Phone license[^57]. Without that license, the Voice tab does not appear on the user page in the Teams admin center[^57]. ### Very short recordings Cloud Voicemail does not deliver voicemails whose recorded duration is under 1 second[^47]. ## When voicemail is not delivered to the mailbox Mail rules that block noreply@skype.voicemail.microsoft.com stop users receiving voicemail[^43]. Exchange mail flow (transport) rules can also filter voicemails out before they reach the mailbox, so the messages appear in no client[^13]. One example is a rule that marks messages with MP3 attachments as spam[^13]. Voicemail notifications that fail SPF are still delivered to Exchange[^44]. However, mail flow rules that act on SPF failure can prevent them from reaching the user's mailbox[^44]. Microsoft's workaround for filtered voicemail is to add the Teams cloud service IP addresses to an SPF record, or to create a transport rule that bypasses spam filtering for Cloud Voicemail from those addresses[^45]. ## When voicemail reaches Outlook but not Teams When voicemails reach Outlook but not the Teams client, Microsoft directs admins to run the Teams Voicemail test in Microsoft Remote Connectivity Analyzer[^40]. - **Blocked mailbox access**: Exchange Client Access Rules or EWS access policies that block access can prevent Teams from retrieving voicemails[^5]. - **OpenDomainRoutingEnabled**: if this Exchange Online setting is True, the voicemail Content-Class header changes from Voice-CA to unauthenticatedVoice-CA, and Teams cannot identify the messages as voicemail[^28]. Changing OpenDomainRoutingEnabled to False requires a support request to Microsoft Support, and the article gives no admin-side cmdlet to change it[^22]. - **Modified headers**: mail flow rules, or third-party spam and antivirus filters, that modify voicemail headers stop messages from landing in the voicemail search folder Teams uses[^10]. MFCMAPI can inspect that folder under Root Container\Finder[^10]. - **Protected voicemail**: protected voicemail (Purview sensitivity-label encryption of voicemail) is supported for users with Exchange Online mailboxes[^36]. Protected (encrypted) voicemail messages cannot be opened in Microsoft Teams[^37]. ## Exchange Server mailbox users For Teams users with Exchange Server mailboxes, voicemail is delivered by SMTP routed through Exchange Online[^25]. For that reason, the connectors between Exchange Server and Exchange Online must be configured correctly[^25]. Teams shows a voicemail only if its message class is IPM.Note.Microsoft.Voicemail.UM[^15]. SMTP delivery to Exchange on-premises strips that item class unless the connector is set up correctly[^15]. - **Partner application**: Cloud Voicemail integration requires an Exchange partner application named CloudVoicemail, with application identifier db7de2b5-2149-435e-8043-e080dd50afae, linked to the TeamsIntegration mail user[^6]. - **Legacy application**: Microsoft has been progressively disabling the legacy Skype for Business Online first-party application (00000004-0000-0ff1-ce00-000000000000) since 13 October 2025[^12]. It is being replaced by dedicated Teams Calendar Scheduler and Cloud Voicemail applications[^12]. - **OAuth certificates**: Exchange Server OAuth certificates no longer need to be uploaded to the Microsoft-managed Teams Calendar Scheduler or Cloud Voicemail service principals[^17]. An expiring certificate is renewed only in Exchange Server[^17]. Microsoft's check for Cloud Voicemail integration with an on-premises mailbox is the out-of-office greeting[^27]. The out-of-office greeting and its Outlook automatic-replies trigger are disabled by default, so enable them for the test user first[^26]. If the CloudVoicemail partner application is not working, the regular greeting plays instead of the Outlook automatic-replies greeting[^27]. ## Voicemail policy, greetings and transcription ### Policy defaults and limits By default, the voicemail policy enables transcription and transcription translation, leaves profanity masking off, and caps recording at 5 minutes[^30]. The voicemail policy MaximumRecordingLength must be between 30 seconds and 10 minutes[^14]. The voicemail service caches voicemail policies and refreshes every 5 minutes, so policy changes can take up to 5 minutes to apply[^29]. AI-powered voicemail triage (EnableVoicemailTriage) works only for customers in the Voice Applications private preview, and it enriches voicemail only for users with an eligible Microsoft 365 Copilot license[^54]. ### Transcription and translation When voicemail transcription is turned off by policy, the voicemail email says the audio quality was not good enough for transcription[^51]. Cloud Voicemail transcribes in the language it detects in the recorded message, not in the recipient's configured language[^50]. When transcription translation is enabled, Cloud Voicemail translates from the detected language into the user's preferred language[^53]. If no preferred language is set, it translates into the tenant default[^53]. Microsoft's voicemail language table lists several languages with no transcription, including Bulgarian, Croatian, Estonian, Romanian, Slovak, Vietnamese and Welsh[^20]. ### Greetings System greeting language is chosen in priority order from the voicemail policy's primary and secondary prompt languages, then the user's preferred language, then the tenant default language[^34]. Setting PrimarySystemPromptLanguage in a voicemail policy also requires setting a different SecondarySystemPromptLanguage[^33]. The pair overrides the user's language choice for system prompts[^33]. A custom text-to-speech greeting (DefaultGreetingPromptOverwrite) plays only when the user has no recorded custom greeting[^55]. By default, the out-of-office voicemail greeting is disabled, including the triggers for Outlook automatic replies and out-of-office calendar events[^26]. ## Diagnosing it - Run the Voicemail self-help diagnostic against the user's email to validate tenant and policy configuration for receiving voicemail[^42]. The path is Teams admin center > Dashboard > Self-help diagnostics > Voicemail[^42]. - Confirm that the user's VoicemailEnabled setting is true[^56]. - Confirm that the calling policy does not set AllowVoicemail to AlwaysDisabled[^1]. - Confirm that InboundPstnCallRoutingTreatment is not sending calls to voicemail while voicemail is disabled[^11]. - Check that the call answering mode allows the caller to leave a message[^35]. - Review mail rules for blocks on noreply@skype.voicemail.microsoft.com[^43]. - Review mail flow rules that act on MP3 attachments or SPF failure[^13][^44]. - If messages reach Outlook but not Teams, run the Teams Voicemail test in Microsoft Remote Connectivity Analyzer[^40]. Remote Connectivity Analyzer is not available for the GCC and GCC High Microsoft 365 Government environments[^39]. - Use MFCMAPI to check whether messages are present in the voicemail search folder under Root Container\Finder[^10]. - For Exchange Server mailboxes, with the out-of-office greeting and its automatic-replies trigger enabled for the test user[^26], set an Outlook automatic reply and confirm that the out-of-office greeting plays[^27]. - After a voicemail policy change, allow up to 5 minutes before retesting[^29]. ## See also - [Microsoft Teams Cloud Voicemail](https://warmtransfer.net/knowledge/teams-cloud-voicemail) - [Calls going straight to voicemail](https://warmtransfer.net/knowledge/calls-straight-to-voicemail) - [Troubleshooting Teams Phone call forwarding and simultaneous ring](https://warmtransfer.net/knowledge/teams-call-forwarding-troubleshooting) - [Teams voice administration with PowerShell](https://warmtransfer.net/knowledge/teams-powershell-voice-admin) - [Microsoft Teams Phone architecture and licensing](https://warmtransfer.net/knowledge/teams-phone-architecture) ## Applicability Applies to: Microsoft Teams Phone, Microsoft Remote Connectivity Analyzer, MicrosoftTeams PowerShell module, and Microsoft Teams. Deployments: hybrid, multi-tenant, gcc, and gcc-high. Sources checked 2026-10-02. Microsoft Remote Connectivity Analyzer is not available for the GCC and GCC High Microsoft 365 Government environments[^39]. AI-powered voicemail triage is limited to the Voice Applications private preview, with no general availability date set[^54]. The legacy Skype for Business Online first-party application has been progressively disabled since 13 October 2025[^12]. ## What remains uncertain ### Teams client playback for Exchange Server mailboxes Sources disagree on whether Exchange Server mailbox users can use voicemail in the Teams client: the Cloud Voicemail setup article says Exchange OAuth (or the Hybrid Wizard) plus Teams-Exchange Server integration must be configured to enable features such as visual voicemail in Teams clients for those users[^24]. This is disputed by another Microsoft source, which says users with Exchange on-premises mailboxes receive messages in Outlook but cannot view or play them in the Teams client[^23]. ### Protected voicemail playback Sources disagree on where protected voicemail can be played: the Cloud Voicemail setup article says users can listen to protected voicemail in Outlook, Outlook on the web, and Outlook for Android or iOS[^38]. This is disputed by the voicemail troubleshooting article, which says RMS-protected voicemail is viewable in Outlook but can be played only in Outlook on the web[^41]. ### The ShareData setting Sources disagree on whether the data-sharing setting is active: the Manage Voicemail Policies article lists "Users can share data for service improvement" as an active setting that, when false, prevents sharing regardless of user choice[^32]. This is disputed by the Set-CsOnlineVoicemailPolicy reference, which says ShareData is deprecated, ignored by the service, and kept only for backward compatibility[^31]. ### Inferences and gaps WarmTransfer's reading of the sources is that a user with no Exchange mailbox cannot receive Cloud Voicemail at all, and readers should verify this against their own tenant[^16]. Whether the Voicemail self-help diagnostic is available in GCC and GCC High is not covered by the sources below. Whether the PSTN connectivity method used for a user's number changes any of the routing behaviour described here is not covered by the sources below. ## Sources [^1]: With calling policy AllowVoicemail set to AlwaysDisabled, calls are never routed to voicemail and voicemail is not offered as a forwarding or unanswered target in Teams. Source: [Set-CsTeamsCallingPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csteamscallingpolicy), Parameters > -AllowVoicemail, AlwaysDisabled. Checked 2026-10-02. [^2]: With calling policy AllowVoicemail set to AlwaysEnabled, unanswered calls always go to voicemail after ringing 30 seconds and the Teams client hides the option to manage unanswered calls. Source: [Set-CsTeamsCallingPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csteamscallingpolicy), Parameters > -AllowVoicemail, AlwaysEnabled. Checked 2026-10-02. [^3]: BusyOnBusyEnabledType set to Unanswered applies the user's unanswered settings, such as voicemail, to new calls while the user is already on a call. Source: [Set-CsTeamsCallingPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csteamscallingpolicy), Parameters > -BusyOnBusyEnabledType. Checked 2026-10-02. [^4]: The voicemail CallAnswerRule accepts DeclineCall, PromptOnly, PromptOnlyWithTransfer, RegularVoicemail and VoicemailWithTransferOption. Source: [Set-CsOnlineVoicemailUserSettings (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csonlinevoicemailusersettings), Parameters > -CallAnswerRule. Checked 2026-10-02. [^5]: If voicemails reach Outlook but not Teams, Exchange Client Access Rules or EWS access policies that block access can prevent Teams from retrieving them. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Resolution For Symptom 2 > Exchange Client Access Rules; Exchange Web Access Rules. Checked 2026-10-02. [^6]: For Exchange Server mailboxes, Cloud Voicemail integration requires an Exchange partner application named CloudVoicemail with application identifier db7de2b5-2149-435e-8043-e080dd50afae, linked to the TeamsIntegration mail user. Source: [Integration between Microsoft Teams services and Exchange Server](https://learn.microsoft.com/en-us/skypeforbusiness/deploy/integrate-with-exchange-server/oauth-with-online-and-on-premises), Step 4: Create and enable a Partner Application for Cloud Voicemail integration. Checked 2026-10-02. [^7]: If neither user nor admin changes call answering rules, unanswered calls go to voicemail after 30 seconds, although Teams admin center and PowerShell show the unanswered target as none and a 20-second delay. Source: [Configure call forwarding and delegation settings](https://learn.microsoft.com/en-us/microsoftteams/user-call-settings), Additional notes. Checked 2026-10-02. [^8]: By default a user's call answering rule is Regular Voicemail and voicemail is enabled. Source: [Manage Cloud Voicemail settings - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-voicemail-settings), Default settings list. Checked 2026-10-02. [^9]: Admins in community forums report voicemails that appear in Outlook but not Teams only for external (PSTN) callers, a pattern Microsoft's article ties to mail flow rules (field report). Source: [Getting voicemail email but no voicemail to view in teams](https://techcommunity.microsoft.com/discussions/microsoftteams/getting-voicemail-email-but-no-voicemail-to-view-in-teams/3844139), Reply by ChrisF512, 2024-01-11; reply by Bhanu07, 2024-01-11. Checked 2026-10-02. [^10]: Mail flow rules or third-party spam and antivirus filters that modify voicemail headers stop messages landing in the voicemail search folder Teams uses; MFCMAPI can inspect that folder under Root Container\Finder. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Resolution For Symptom 2 > Exchange mail flow rules and following Note. Checked 2026-10-02. [^11]: Calling policy InboundPstnCallRoutingTreatment set to Voicemail sends inbound PSTN calls straight to voicemail without presenting them, overrides other forwarding settings, and disconnects the call if voicemail is not enabled. Source: [Set-CsTeamsCallingPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csteamscallingpolicy), Parameters > -InboundPstnCallRoutingTreatment. Checked 2026-10-02. [^12]: Microsoft has been progressively disabling the legacy Skype for Business Online first-party application (00000004-0000-0ff1-ce00-000000000000) since 13 October 2025, replacing it with dedicated Teams Calendar Scheduler and Cloud Voicemail applications. Source: [Integration between Microsoft Teams services and Exchange Server](https://learn.microsoft.com/en-us/skypeforbusiness/deploy/integrate-with-exchange-server/oauth-with-online-and-on-premises), Step 7: Disable or remove the legacy Skype for Business Online application. Checked 2026-10-02. [^13]: Exchange mail flow (transport) rules, for example rules marking messages with MP3 attachments as spam, can filter voicemails out before they reach the mailbox so they appear in no client. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Resolution for Symptom 1 > Exchange mail flow rules. Checked 2026-10-02. [^14]: The voicemail policy MaximumRecordingLength must be between 30 seconds and 10 minutes. Source: [Set-CsOnlineVoicemailPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csonlinevoicemailpolicy), Parameters > -MaximumRecordingLength. Checked 2026-10-02. [^15]: Teams shows a voicemail only if its message class is IPM.Note.Microsoft.Voicemail.UM, and SMTP delivery to Exchange on-premises strips the item class unless the connector is set up correctly. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Resolution For Symptom 2 > Exchange Email Connector. Checked 2026-10-02. [^16]: A Teams user with no Exchange mailbox (Exchange Online or a correctly connected Exchange Server) cannot receive Cloud Voicemail messages, because SMTP delivery to that mailbox is the only deposit path (inferred). Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Cloud Voicemail storage; Cloud Voicemail delivery. Checked 2026-10-02. [^17]: Exchange Server OAuth certificates no longer need to be uploaded to the Microsoft-managed Teams Calendar Scheduler or Cloud Voicemail service principals; an expiring certificate is renewed only in Exchange Server. Source: [Integration between Microsoft Teams services and Exchange Server](https://learn.microsoft.com/en-us/skypeforbusiness/deploy/integrate-with-exchange-server/oauth-with-online-and-on-premises), Opening Note; Step 5: Certificate management guidance. Checked 2026-10-02. [^18]: Cloud Voicemail is set up and provisioned automatically for Teams users, and a Microsoft Teams Phone license is not required for Cloud Voicemail. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Cloud Voicemail provisioning. Checked 2026-10-02. [^19]: Teams Cloud Voicemail does not support third-party email systems; voicemail is deposited only in an Exchange mailbox. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Introduction (paragraph after the opening description). Checked 2026-10-02. [^20]: Microsoft's voicemail language table lists several languages with no transcription, including Bulgarian, Croatian, Estonian, Romanian, Slovak, Vietnamese and Welsh. Source: [Teams languages for voicemail greetings and messages - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/languages-for-voicemail-greetings-and-messages), Language table, Transcription available? column, rows bg-BG hr-HR et-EE ro-RO sk-SK vi-VN cy-GB. Checked 2026-10-02. [^21]: Voicemail messages generated by Cloud Voicemail are not DKIM-signed. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Cloud Voicemail delivery > Important callout. Checked 2026-10-02. [^22]: Changing OpenDomainRoutingEnabled to False requires a support request to Microsoft Support; the article gives no admin-side cmdlet to change it. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Resolution for Symptom 1, sentence after the OpenDomainRoutingEnabled explanation. Checked 2026-10-02. [^23]: Teams users whose mailbox is on Exchange on-premises can use Cloud Voicemail and receive messages in Outlook, but the messages cannot be viewed or played in the Teams client (disputed). Source: [How Exchange and Microsoft Teams interact](https://learn.microsoft.com/en-us/microsoftteams/exchange-teams-interact), Actions supported table, Exchange On-premises row, Voicemail column, footnote 4. Checked 2026-10-02. [^24]: The Cloud Voicemail setup article says Exchange OAuth (or the Hybrid Wizard) plus Teams-Exchange Server integration must be configured to enable voicemail features such as visual voicemail in Teams clients for Exchange Server mailbox users (disputed). Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Set up Cloud Voicemail for Exchange Server mailbox users, item 2. Checked 2026-10-02. [^25]: For Teams users with Exchange Server mailboxes, voicemail is delivered by SMTP routed through Exchange Online, so connectors between Exchange Server and Exchange Online must be configured correctly. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Set up Cloud Voicemail for Exchange Server mailbox users, item 1. Checked 2026-10-02. [^26]: By default the out-of-office voicemail greeting is disabled, including the triggers for Outlook automatic replies and out-of-office calendar events. Source: [Manage Cloud Voicemail settings - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-voicemail-settings), Default settings list. Checked 2026-10-02. [^27]: Microsoft's check for Cloud Voicemail integration with an on-premises mailbox is the out-of-office greeting: if the CloudVoicemail partner application is not working, the regular greeting plays instead of the Outlook automatic-replies greeting. Source: [Integration between Microsoft Teams services and Exchange Server](https://learn.microsoft.com/en-us/skypeforbusiness/deploy/integrate-with-exchange-server/oauth-with-online-and-on-premises), Step 6: Verify your success, item 2. Checked 2026-10-02. [^28]: If Exchange Online OpenDomainRoutingEnabled is True, the voicemail Content-Class header changes from Voice-CA to unauthenticatedVoice-CA and Teams cannot identify the messages as voicemail. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Resolution for Symptom 1, Get-TransportConfig paragraph. Checked 2026-10-02. [^29]: The voicemail service caches voicemail policies and refreshes every 5 minutes, so policy changes can take up to 5 minutes to apply. Source: [Manage Voicemail Policies - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-voicemail-policies), Important callout after the default policies list. Checked 2026-10-02. [^30]: By default the voicemail policy enables transcription and transcription translation, leaves profanity masking off, and caps recording at five minutes. Source: [Manage Voicemail Policies - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-voicemail-policies), Default policies list. Checked 2026-10-02. [^31]: The Set-CsOnlineVoicemailPolicy reference says the policy ShareData parameter is deprecated, ignored by the service, and kept only for backward compatibility (disputed). Source: [Set-CsOnlineVoicemailPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csonlinevoicemailpolicy), Parameters > -ShareData > Important. Checked 2026-10-02. [^32]: The Manage Voicemail Policies article lists 'Users can share data for service improvement' as an active policy setting that, when false, prevents sharing voicemail and transcription data regardless of user choice (disputed). Source: [Manage Voicemail Policies - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-voicemail-policies), Voicemail policy settings > Users can share data for service improvement. Checked 2026-10-02. [^33]: Setting PrimarySystemPromptLanguage in a voicemail policy requires setting a different SecondarySystemPromptLanguage too, and the pair overrides the user's language choice for system prompts. Source: [Set-CsOnlineVoicemailPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csonlinevoicemailpolicy), Parameters > -PrimarySystemPromptLanguage; -SecondarySystemPromptLanguage. Checked 2026-10-02. [^34]: System greeting language is chosen in priority order from the voicemail policy's primary and secondary prompt languages, then the user's preferred language, then the tenant default language. Source: [Change the default language for greetings and emails - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/change-the-default-language-for-greetings-and-emails), Greetings, third paragraph. Checked 2026-10-02. [^35]: With call answering mode 'Play an outgoing message to the caller' only the greeting plays and the caller cannot leave a voicemail; 'Service declines the call with no message' disconnects the caller. Source: [Manage Cloud Voicemail settings - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-voicemail-settings), Voicemail settings > Call answering mode. Checked 2026-10-02. [^36]: Protected voicemail (Purview sensitivity-label encryption of voicemail) is supported for users with Exchange Online mailboxes. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Enable protected voicemail in your organization, second paragraph. Checked 2026-10-02. [^37]: Protected (encrypted) voicemail messages cannot be opened in Microsoft Teams. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Enable protected voicemail in your organization, fifth paragraph. Checked 2026-10-02. [^38]: The Cloud Voicemail setup article says users can listen to protected voicemail in Outlook, Outlook on the web, and Outlook for Android or iOS (disputed). Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Enable protected voicemail in your organization, fifth paragraph. Checked 2026-10-02. [^39]: Microsoft Remote Connectivity Analyzer is not available for the GCC and GCC High Microsoft 365 Government environments. Source: [Resolve interaction issues between Teams and Exchange Server](https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/known-issues/teams-exchange-interaction-issue), Common troubleshooting steps > Run the Teams Exchange Integration connectivity test > Note. Checked 2026-10-02. [^40]: When voicemails reach Outlook but not the Teams client, Microsoft directs admins to run the Teams Voicemail test in Microsoft Remote Connectivity Analyzer. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Symptom 2 > Use Microsoft Remote Connectivity Analyzer to diagnose. Checked 2026-10-02. [^41]: The voicemail troubleshooting article says RMS-protected voicemail is viewable in Outlook but can be played only in Outlook on the web, with transcriptions readable in Outlook or OWA (disputed). Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Resolution For Symptom 2 > Exchange Email Connector > Note, second bullet. Checked 2026-10-02. [^42]: Admins can run a Voicemail self-help diagnostic (Teams admin center > Dashboard > Self-help diagnostics > Voicemail) against a user's email to validate tenant and policy configuration for receiving voicemail. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Diagnosing issues with Voicemail, steps 1-3. Checked 2026-10-02. [^43]: Cloud Voicemail email is sent from noreply@skype.voicemail.microsoft.com, and mail rules that block this address stop users receiving voicemail. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Cloud Voicemail processing > Important callout; Cloud Voicemail delivery. Checked 2026-10-02. [^44]: Voicemail notifications that fail SPF are still delivered to Exchange, but mail flow rules that act on SPF failure can prevent them reaching the user's mailbox. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Resolution for Symptom 1 > Exchange mail flow rules, last sentences. Checked 2026-10-02. [^45]: Microsoft's workaround for filtered voicemail is to add the Teams cloud service IP addresses to an SPF record, or create a transport rule that bypasses spam filtering for Cloud Voicemail from those addresses. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Workaround for Symptom 1. Checked 2026-10-02. [^46]: Cloud Voicemail messages are delivered to and stored in the user's Exchange mailbox (Exchange Online or Exchange Server) with no separate voicemail store; Outlook and Teams read them through the mailbox APIs. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Cloud Voicemail storage, first paragraph. Checked 2026-10-02. [^47]: Cloud Voicemail delivers messages over SMTP and does not deliver voicemails whose recorded duration is under one second. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Cloud Voicemail delivery, first paragraph. Checked 2026-10-02. [^48]: In the Teams admin center calling policy, 'Voicemail for inbound calls' offers On, Off and Let users decide, and Let users decide is the default. Source: [Set up Cloud Voicemail](https://learn.microsoft.com/en-us/microsoftteams/set-up-phone-system-voicemail), Control routing of calls to Cloud Voicemail > Using Teams admin center, step 3. Checked 2026-10-02. [^49]: For PSTN calls the voicemail FROM address is not RFC-compliant, and Microsoft advises third-party mail filters to evaluate the P1 sender address instead. Source: [Voicemail Messages Aren't Delivered in Teams or Skype for Business Client](https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/phone-system/voicemails-not-delivered), Resolution for Symptom 1 > Third-party email systems. Checked 2026-10-02. [^50]: Cloud Voicemail transcribes in the language it detects in the recorded message, not in the recipient's configured language. Source: [Change the default language for greetings and emails - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/change-the-default-language-for-greetings-and-emails), Transcription. Checked 2026-10-02. [^51]: When voicemail transcription is turned off by policy, the voicemail email says the audio quality was not good enough for transcription. Source: [Manage Voicemail Policies - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-voicemail-policies), Voicemail policy settings > final Note. Checked 2026-10-02. [^52]: The voicemail TransferTarget applies to PromptOnlyWithTransfer and VoicemailWithTransferOption, must be the SIP URI of another user in the organisation, and accepts a phone number only for Enterprise Voice-enabled users. Source: [Set-CsOnlineVoicemailUserSettings (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csonlinevoicemailusersettings), Parameters > -TransferTarget. Checked 2026-10-02. [^53]: When transcription translation is enabled, Cloud Voicemail translates from the detected language into the user's preferred language, or the tenant default if none is set. Source: [Change the default language for greetings and emails - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/change-the-default-language-for-greetings-and-emails), Transcription translation. Checked 2026-10-02. [^54]: AI-powered voicemail triage (EnableVoicemailTriage) works only for customers in the Voice Applications private preview, with no general availability date set, and enriches voicemail only for users with an eligible Microsoft 365 Copilot license. Source: [Set-CsOnlineVoicemailPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csonlinevoicemailpolicy), Description > Important; Parameters > -EnableVoicemailTriage. Checked 2026-10-02. [^55]: A custom text-to-speech greeting (DefaultGreetingPromptOverwrite) plays only when the user has no recorded custom greeting. Source: [Set-CsOnlineVoicemailUserSettings (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/set-csonlinevoicemailusersettings), Parameters > -DefaultGreetingPromptOverwrite. Checked 2026-10-02. [^56]: If a user's per-user voicemail setting (VoicemailEnabled) is false, Cloud Voicemail is unavailable for that user and no voicemail is recorded. Source: [Manage Cloud Voicemail settings - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-voicemail-settings), Voicemail settings > Voicemail. Checked 2026-10-02. [^57]: Admin configuration of a user's call forwarding and unanswered settings requires a Teams Phone license, and the Voice tab in the Teams admin center user page does not appear without one. Source: [Configure call forwarding and delegation settings](https://learn.microsoft.com/en-us/microsoftteams/user-call-settings), License required; Use the Teams admin center, step 6. Checked 2026-10-02.