Auto Meeting Session timeout

Question

Auto Meeting Session timeout

Info Omniwish 35

I am building a MERN stack application where I create Microsoft Teams online meetings using Microsoft Graph API.

My use case:

Meetings are scheduled with a fixed duration (e.g., 30–60 minutes)
Participants receive the meeting link and join via Microsoft Teams
I want the meeting to automatically end after the scheduled duration, even if participants remain active

What I have tried so far:

Setting startDateTime and endDateTime while creating the meeting → This does not enforce the meeting end; it only defines the schedule
Updating meeting settings after expiry (e.g., isHostRequired = true) → This prevents new participants from joining but does not remove existing participants
Explored Graph API capabilities for ending meetings → I could not find any API that forcefully ends a meeting for all participants

Challenges:

Participants who join just before expiry can continue the meeting indefinitely
There is no apparent way to enforce a strict session timeout

Questions:

Does Microsoft Teams or Microsoft Graph API support forcibly ending a meeting for all participants?
Is there any session timeout or policy setting available for Teams meetings?
Are there any recommended approaches (e.g., bots, calling APIs, or administrative policies) to enforce meeting duration?

I would appreciate clarification on whether this is a platform limitation or if there is a supported workaround.

0 comments

2 answers

Your answer

Answer 1

Steven-N 23,700 Microsoft External Staff Moderator

Hi Info Omniwish

Based on your description, I have conducted some research, and the below information might help

1/ Does Microsoft Teams or Microsoft Graph API support forcibly ending a meeting for all participants?

Unfortunately, No, currently Microsoft Teams and the Microsoft Graph API do not provide any endpoint that forcibly terminates an active meeting session and removes all current participants simultaneously. The endDateTime property on the onlineMeeting resource is used for scheduling purposes only and carries no enforcement behavior once the meeting is in progress.

As states in: onlineMeeting resource type

2/ Is there any session timeout or policy setting available for Teams meetings?

As far as I know, there is a tenant-level or per-user meeting policy available through the Microsoft Teams PowerShell module that can be configured to automatically end a meeting after a period of inactivity. This is managed via Set-CsTeamsMeetingPolicy and requires Teams Administrator privileges. However, this policy applies uniformly and cannot be configured on a per-meeting basis through the Graph API.

You can read here for more information: Set-CsTeamsMeetingPolicy | Manage meeting policies

3/ Are there any recommended approaches to enforce meeting duration?

Yes, in my opinion, you can try deploying a Teams bot that joins the meeting as a participant using the Cloud Communications API by following below instructions:

Register a bot via Azure Bot Framework
Join the meeting programmatically using

POST /communications/calls

When the timer expires, the bot calls:

DELETE /communications/calls/{call-id}

This will ends the call from the bot's perspective (which acts as host/organizer), and terminates the session for all participants if the bot is the meeting organizer.

Note: The bot must join as the meeting organizer (using application permissions and the organizer's identity), not as a regular attendee. If the bot only joins as a guest, deleting its own leg does not end the meeting for others.

Graph API call to end the call:

DELETE https://graph.microsoft.com/v1.0/communications/calls/{call-id}

Hope my answer will help you.

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.

Sayali-MSFT 5,281 Reputation points Microsoft External Staff Moderator

2026-03-23T09:24:02.67+00:00

Hello **Info Omniwish,
**Could you please confirm if your issue has resolved with provided suggestions or still looking for any help?
Steven-N 23,700 Reputation points Microsoft External Staff Moderator

2026-03-25T07:40:27.76+00:00

Hi Info Omniwish

It has been a while and I am writing to see how things are going with this issue.

Have you had a chance to check the replies provided?

Any update would be appreciated.
Info Omniwish 35 Reputation points

2026-03-26T12:41:20.23+00:00

Hello Steven-N,

I followed your answer and now the bot has joined the meeting, but it has joined as a participant, not as an organizer.

I would like to know how to join bot as organizer?
Steven-N 23,700 Reputation points Microsoft External Staff Moderator

2026-03-27T09:30:43.3766667+00:00

Hi Info Omniwish

Technically, in Microsoft Teams, a custom app or bot cannot join a meeting with the "Organizer" or "Co-organizer" role. By design, the Organizer role is strictly reserved for the human user account (the M365 mailbox) that scheduled and created the meeting.

Link reference: Apps for Teams meetings - Teams | Microsoft Learn

Thank you for your understanding
Info Omniwish 35 Reputation points

2026-04-02T06:58:11.9533333+00:00

Hi Steven-N,

Then how to end meeting ?
Steven-N 23,700 Reputation points Microsoft External Staff Moderator

2026-04-02T10:42:19.9566667+00:00
Hi Info Omniwish

You can use this endpoint to end the meeting:

DELETE https://graph.microsoft.com/v1.0/communications/calls/{call-id}

Regards

Info Omniwish 35

Hii Steven-N,

Yes you are correct

But DELETE https://graph.microsoft.com/v1.0/communications/calls/{call-id} when I am calling this API but its ending only bot Meeting I want to ending meeting of all participant.

 Bot Joining

const response = await axios.post(
      "https://graph.microsoft.com/v1.0/communications/calls",
      {
         "@odata.type": "#microsoft.graph.call",
         direction: "outgoing",
         callbackUri: "website/api/callback",
         requestedModalities: ["audio"],
         mediaConfig: {
            "@odata.type": "#microsoft.graph.serviceHostedMediaConfig"
         },
         chatInfo: {
            "@odata.type": "#microsoft.graph.chatInfo",
            threadId: threadId,
            messageId: "0"
         },
         meetingInfo: {
            "@odata.type": "#microsoft.graph.organizerMeetingInfo",
            organizer: {
               "@odata.type": "#microsoft.graph.identitySet",
               user: {
                  "@odata.type": "#microsoft.graph.identity",
                  id: UserId, // SAME USER WHO CREATED MEETING
                  tenantId: tenantId
               }
            }
         },
         tenantId: tenantId
      },
      {
         headers: {
            Authorization: `Bearer ${token}`,
            "Content-Type": "application/json"
         }
      }
   );
   console.log("meeting join by boot",response.data);
   return response.data.id;
};

Meeting End code 

try {
    const token = await getToken();

    const url = `https://graph.microsoft.com/v1.0/communications/calls/${callId}`;

    const response = await axios.delete(url, {
      headers: {
        Authorization: `Bearer ${token}`,
      },
    });

    console.log("🔥 Meeting ended successfully", response.status);
  } catch (error) {
    console.error(
      "❌ Error ending meeting:",
      error.response?.data || error.message
    );
  }

Steven-N 23,700 Reputation points Microsoft External Staff Moderator

2026-04-07T06:05:58.7566667+00:00
Hi Info Omniwish

Since Microsoft Graph does not currently expose a single "End Meeting for All" endpoint, the recommended workaround for your scenario is to programmatically drop everyone from the meeting when the timer expires. Your bot can accomplish this by sequentially kicking every participant.

Could you please try the approach below:

Before your bot is permitted to remove other participants, a Microsoft 365 Tenant Admin must explicitly authorize your application's App ID via the Microsoft Teams PowerShell module setting application meeting configurations:

Set-CsApplicationMeetingConfiguration -AllowRemoveParticipantAppIds @{Add="<Your-Bot-App-Client-ID>"}

When your fixed meeting duration expires, execute the following steps in your MERN backend:

Fetch active participants: Use GET /communications/calls/{call-id}/participants

Remove participants: Iterate through the array and call DELETE /communications/calls/{call-id}/participants/{participant-id}

Bot leaves: Finally, call DELETE /communications/calls/{call-id} for the bot to exit the empty room.

Regards

Answer 2

Microsoft Teams and Microsoft Graph do not currently provide an API to forcibly end an online meeting for all participants on demand. The platform exposes:
- Scheduling metadata (start/end times) on the meeting object.
- Presence and meeting events (for example, start/end notifications to apps). But there is no documented Graph or Teams API that disconnects all participants or hard-stops a running meeting.
There is no configurable “session timeout” for Teams meetings that enforces a hard stop at the scheduled end time. Relevant platform limits are:
- Teams meetings, webinars, and town halls have a maximum time limit of 30 hours. After that, the meeting ends regardless of schedule.
- Meeting links and recurrence patterns have expiration rules (for example, scheduled one-time meetings expire 60 days after the scheduled time), but these govern link validity and re-use, not an in-call timeout.
From the documented limits:
- Scheduled one-time meeting: expires 60 days after the scheduled time.
- Meet now (calendar/channel): expires 60 days after link creation.
- Recurring with end date: 60 days from end date or last occurrence, whichever is longer.
- Recurring with no end date: 1 year after last access/join/update.
None of these settings force-disconnect participants at the scheduled end.
Recommended/possible approaches within current platform capabilities: There is no supported, fully enforced “hard stop” mechanism, so any solution will be advisory or UX-driven rather than technically enforced:
- Use meeting duration and expiration semantics only as guidance:
  - Set startDateTime/endDateTime to reflect the intended duration.
  - Communicate clearly in the invite that the meeting is limited to that duration.
- Use a Teams meeting app/bot to monitor and react to time:
  - A meeting app can receive real-time meeting events (start/end, participant join/leave) via a bot.
  - The bot can track elapsed time from the actual start and, when the configured duration is reached, it can:
    - Post a message in the meeting chat that the session has ended.
    - Optionally instruct the organizer to end the meeting manually.
  - This still cannot forcibly disconnect users, but it provides automated enforcement signals and UX.
- Administrative or organizational policy:
  - Use policy and training to require organizers to end meetings at the scheduled time.
  - Combine with monitoring (for example, reporting on unusually long meetings) if needed.
Given the current documentation, this is a platform limitation: there is no supported way to programmatically terminate a running Teams meeting or impose a strict per-meeting session timeout shorter than the global 30‑hour limit.

References:

Info Omniwish 35 Reputation points

2026-04-02T04:31:15.92+00:00

Then how to end meeting ?

Share via

Auto Meeting Session timeout

2 answers

Your answer