Share via

My MS Teams video recording failed to upload to MS Streams

Anonymous
2019-05-10T17:56:49+00:00

I recorded a meeting yesterday using MS Teams. 

After ending the meeting, I confirmed this message in the corresponding chat:

Unfortunately, this morning I saw this message in the corresponding chat:

I checked on MS Streams, and the video is not there.

What can I do to recover this recording? Is it possible that it is cached locally on my system?

Microsoft Teams | Microsoft Teams for business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2019-05-10T21:11:48+00:00

    Hi BenjaminCase,

    May I know whether this issue happen to every recording meeting or specific video recording meeting?

    Does this issue happen to any other users in your organization? Is it your admin has set a company policy for saving to Microsoft Stream?

    However, the recording happens in the cloud and is saved to Microsoft Stream. It’s not cached locally on the system.

    Make sure that you have upload video permissions in Microsoft Stream. You may contact Microsoft Stream administrator to see whether they restricted for creating content in Stream. If the users who are in this restricted list will not be able to record meetings.

    You may also try turn off and then Turn on cloud recording/transcription to check this issue.

    Note: User has sufficient storage in Microsoft Stream for recordings to be saved

    For your reference: Teams cloud meeting recording

    Best regards,

    Shyamal

    2 people found this answer helpful.
    0 comments

6 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-05-16T10:32:34+00:00

    Hi JayAntoney,

    Welcome to post in community.

    To resolve your and your customers problem, I suggest you to post a new thread so that our engineers can find root reasons and provide more precise solution on your condition. Thanks for your understanding.

    Sincerely,

    Shawn

    0 comments
  2. Anonymous
    2019-05-16T10:27:39+00:00

    Hi Ben Case,

    Welcome to post in community, but are you the same the person as the thread owner Benjamin Case? 

    If so, according to the pictures provided, meeting recording was uploading in the first picture, but failed in the second one. The truth is that no cache will be stored in the local and recording only happens in the cloud. You can try  to use compliance and eDiscovery for retrievalling meeting recordings. However, if this method fails in the end, it seems unfeasible to recover your recording. Contact your admins and let them follow steps as below:

    1. Go to https://protection.office.com and sign in using  Office 365 admin email address and password.
    2. Click Search > Content search.
    3. On the Search page, click the arrow next to + New search

    1. Click New search in the drop-down list.
    2. Under Search query, specify the following things and look for the keyword "recording" in the subject line of the item.

    1. Click Save & Run

    Feel free to contact me if you have any other question on it. We'll keep on eye on this issue if that happen again. Thanks for your understanding.

    Regards,

    Shawn

    0 comments
  3. Anonymous
    2019-05-14T04:40:25+00:00

    Just to but in here, but I've seen the same behavior the last few days across a few of my customers tenants including my own and a meeting I was trying to record the other day.

    I used to be able to record my meetings, but 2 days ago it failed to upload with the same error above.

    My customers then logged a ticket with me for the same fault yesterday in their tenant.

    Seems like a Microsoft issue...

    0 comments
  4. Anonymous
    2019-05-13T13:02:16+00:00

    Thanks Shyamal,

    This has never happened before. I have saved numerous recordings using Teams and they all upload just fine to Streams.

    I asked other members of my team, as well as our internal o365 admins and they confirmed this has never happened before to other team members, and that we all are configured with the proper permissions to record.

    Thanks,

    Ben

    0 comments