Auto-Recording works in Teams Web/Browser but fails in New Teams Desktop App

Question

Auto-Recording works in Teams Web/Browser but fails in New Teams Desktop App

Angelo Agra 0

I am experiencing an issue where the "Record and transcribe automatically" feature is not triggering in the New Microsoft Teams desktop application, despite working perfectly when joining the same meetings via a web browser (Edge/Chrome).

Issue Details:

App Version: 26032.605.4378.6183
Environment: macOS/Windows
Behavior: When "Record automatically" is toggled ON in Meeting Options, the recording starts as expected in the browser. However, in the desktop app, the meeting begins without recording or transcribing. No error message is displayed; it simply stays "Off."

0 comments

2 answers

Your answer

Answer 1

Demi-N 15,140 Microsoft External Staff Moderator

Hello @Angelo Agra,

Thank you for sharing the version details with us.

The version you mentioned, 26032.605.4378.6183, corresponds to the New Teams app on macOS. Since you also referenced Windows in your post, may I ask whether you are experiencing the same behavior when using Teams on Windows as well?

From my side, I tested the latest Windows build (26032.208.4399.5) and everything worked normally, the meeting automatically recorded as expected with no issues. Because of this, it would be very helpful if you could confirm the exact environment where the problem occurs on your end.

User's image

In addition, I would like to understand whether this issue affects only your device/account or if any of your colleagues are encountering the same behavior. This will help us determine whether the issue is user‑specific, device‑specific, or environment‑related.

As a first troubleshooting step, please try clearing the Teams cache and then test again. This often resolves unexpected behaviors in the New Teams client. You can follow the instructions here: Clear the Teams client cache - Microsoft Teams | Microsoft Learn

Whenever you have a moment, please confirm the operating system where the issue occurs, whether others in your organization see the same, and the results after clearing the cache. Once I have these details, I’ll be happy to continue assisting you further.

Warm regards,

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.

Angelo Agra 0 Reputation points

2026-03-12T13:43:31.9433333+00:00
Hello @Demi-N ,

Meeting Attributes:

Auto-recording is on

Bypass lobby set to anyone

Here are the replication steps:

Invite was created by a microsoft account and was sent to a non-microsoft email account (gmail)

The invite was opened from a Google account in the browser, and the user chose to join the meeting using the Teams app. I believe that the account signed into Teams—despite having a gmail.com domain—is actually a Microsoft account rather than a Google account. Can you confirm this?

The google account user was able to start the meeting but was put in the lobby (even though the bypass lobby is set to everyone).

I tried "Join call without signing in", and the auto recording and transcription works (windows).

To answer your question:

In addition, I would like to understand whether this issue affects only your device/account or if any of your colleagues are encountering the same behavior. This will help us determine whether the issue is user‑specific, device‑specific, or environment‑related.
Ans: Yes, they experienced it as well. They are using windows env for their testing.
Demi-N 15,140 Reputation points Microsoft External Staff Moderator

2026-03-12T14:29:05.2766667+00:00

Hi @Angelo Agra,

Thank you so much for providing these detailed updates, they are very helpful for understanding the situation more clearly. I will need a little time to set up the same scenario on my side and run a few tests in my own environment so I can give you the most accurate guidance.

I will review everything thoroughly and reach back out to you within the next 24 hours with an update.

Thank you again for your patience and cooperation.

Warm regards,
Demi-N 15,140 Reputation points Microsoft External Staff Moderator

2026-03-13T14:22:25.3066667+00:00

Hi @Angelo Agra,

Thank you for your patience while I reviewed your latest update.

I tested the scenario on my side as well, and I can confirm that a user with a Gmail address can indeed create a personal Microsoft account, and in that case they are signing in using Teams Free.

When joining the meeting using the desktop app, whether choosing “Join without signing in” or using the Gmail‑based Microsoft account, the auto‑recording still starts normally in my testing environment, so the feature itself is working as expected.

Regarding the lobby behavior you mentioned, this is also expected. Even if the meeting option says “Bypass lobby: Anyone,” the meeting organizer still needs to actually start the meeting before other participants can fully bypass the lobby. Until the organizer has joined, other attendees may still be placed in the lobby.

To understand the situation more accurately, may I ask for your help with one more detail? Could you please share a screenshot of the meeting window from the organizer’s side and another screenshot from the attendee’s side when joining the meeting? This will help me see exactly how Teams is interpreting the join state and apply the correct troubleshooting path.

Thank you again for your cooperation!
Angelo Agra 0 Reputation points

2026-03-16T02:51:32.47+00:00

Hello @Demi-N , I wanted to share a recording of the test steps our test team did. How can i share it to you?
Demi-N 15,140 Reputation points Microsoft External Staff Moderator

2026-03-16T09:08:53.3+00:00

Hi@Angelo Agra,

Please upload the file to OneDrive and share the link with me, setting the access permission to “Everyone” so that I can access it.

I will open a Private Message so that you can send the link securely. Please click “View message” to check my message.

Thank you very much for your cooperation.

Kind regards,

Answer 2

The behavior is explained by how auto-recording is controlled and surfaced in Teams, not by a browser vs. desktop bug.

Key points from the product behavior:

Auto-recording is governed by organizer options and policies
- The setting Record and transcribe automatically is a per-meeting option that causes recording and transcription to start when the meeting begins.
- Whether organizers can even see or use this option is controlled by the Auto recording policy in Teams meeting policies. This is configured by admins using the -AutoRecording parameter on Set-CsTeamsMeetingPolicy or via meeting templates.
- For organizers where auto recording is enabled at policy level, the Record and transcribe automatically toggle appears in Meeting options and is Off by default for standard meetings; organizers must turn it on per meeting.
Policy can hide the auto-record toggle in the client
- If the admin turns off the auto recording policy for an organizer, that organizer does not see the Record and transcribe automatically setting in Meeting options and cannot configure meetings to auto-record.
- The documentation explicitly notes: “If you turn off auto recording, organizers don't see the setting and can’t set meetings to record automatically.”
What the meeting options actually do
- When Record and transcribe automatically is on, recording and transcription start automatically at meeting start.
- The Who can record and transcribe option controls who can manually start recording/transcription if auto-record is not in effect. This option has interactions with Copilot settings (for example, it cannot be set to No one if Allow Copilot is set to During and after the meeting).
Why browser vs. desktop may differ
The context does not describe a client-specific bug, but it does show that:
- Auto-record is a policy- and template-driven feature, and
- The presence and behavior of the Record and transcribe automatically toggle depend on those settings.
In practice, differences between web and desktop behavior usually indicate:
- Different meeting templates being applied (for example, webinar/town hall vs. standard meeting). Webinars and town halls have auto-record On by default, whereas standard meetings have it Off by default even when allowed by policy.
- Different organizer policies or templates being picked up, or a delay in policy propagation to the desktop client.
Admin and organizer checks to resolve For an admin:
1. Verify the organizer’s Teams meeting policy using Set-CsTeamsMeetingPolicy and ensure -AutoRecording is configured so that the organizer is allowed to use the Record and transcribe automatically setting. If auto recording is turned off at policy level, the organizer cannot configure auto-record in any client.
2. If using meeting templates (especially for webinars or town halls), confirm that the template’s recording settings are consistent and that the same template is being used regardless of client.
For the meeting organizer:
1. Open the meeting from the Teams calendar and go to Meeting options.
2. Confirm that Record and transcribe automatically is visible and toggled On for that specific meeting.
3. Confirm Who can record and transcribe is not set in a way that conflicts with Copilot settings (for example, it cannot be No one if Allow Copilot is During and after the meeting).

If the policy and meeting options are correctly configured and the same meeting auto-records in the browser but not in the new desktop client, this falls outside what is described in the documentation and should be treated as a client defect. In that case, collect client logs and raise a support ticket with Microsoft, referencing the meeting policy and template configuration.

References:

Share via

Auto-Recording works in Teams Web/Browser but fails in New Teams Desktop App

2 answers

Your answer