Issue with Deleting Voicemails in Microsoft Teams

Kris Jensen 0 Reputation points
2026-01-08T17:16:24.74+00:00

A staff member submitted a help desk ticket reporting an issue with deleting listened-to voicemails in Microsoft Teams. The voicemail remains visible after deletion until the user switches to another application and then returns to Teams.

This is occurring on an individual account (not a shared account), so the staff member should have full ability to delete their own voicemails.

Steps Taken:

I tested this behavior using my own account by leaving and deleting a voicemail. The same issue occurred.

I reviewed our group policies and could not find any setting that would prevent staff from deleting voicemails.

Request:

  • Is this a known (new?) issue with Teams?

Has anyone else experienced this behavior?

If so, do you have a workaround or fix?

Microsoft Teams | Microsoft Teams for business | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Ryan-N 9,855 Reputation points Microsoft External Staff Moderator
    2026-01-08T18:24:39.2833333+00:00

    Hi @Kris Jensen,

    Welcome to the Microsoft Q&A forum.

    Thank you for contacting us. I would like to provide you with the following information:

    Based on the test environment for the Teams application and Teams Web:

    When you delete a voicemail, after clicking Delete, the voicemail will not immediately show as deleted. Instead, you need to switch to another tab on the Teams toolbar and then return. At that point, Teams will display that the voicemail has been deleted.

    This is normal behavior in Microsoft Teams. Although you may see that the voicemail is not deleted right after pressing Delete, in reality, it has already been removed.

    If this behavior affects your experience, you can share feedback through Microsoft’s official feedback page at the following link: Feedback Portal.

    User's image

    Note: As part of the support community, we kindly ask for your understanding since our access to internal development details is limited. Our main responsibility is to guide users to appropriate resources and support channels. We do not have influence over product design decisions and have restricted access to internal development details, but we will always try to assist you within our scope of responsibility.

    I  hope you find this information helpful.

    Thank you very much for your patience and understanding throughout this process. If you have any questions or need further assistance, please don’t hesitate to reach out at any time.

    I look forward to hearing back from you soon.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.