Share via

Teams launch bot

JulioCumbaIII 0 Reputation points
2026-05-22T15:41:59.9666667+00:00

We are looking to create a bot or integration or service app that will auto create Channels within a Team and that can auto launch a new Teams meeting in an emergency. This automation should be accessible only to a specific AD group.

Microsoft Teams | Microsoft Teams for business | Teams and channels | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Hin-V 15,325 Reputation points Microsoft External Staff Moderator
    2026-05-22T17:23:20.5466667+00:00

    Hi @JulioCumbaIII

    Thank you for sharing your concerns. 

    First, I’d like to clarify that this is a user‑to‑user support forum. Moderators participating here do not have access to backend systems, nor can we directly intervene in Microsoft product functionality. Our role is limited to providing technical guidance and sharing best‑practice recommendations based on reported issues, requests, and scenarios.      

    Based on my research, your request might typically involve building a Teams app (such as a bot or service app) combined with a backend service that integrates with Microsoft Graph APIs. 

    The app can automatically create new channels within a Team by using the Microsoft Graph Create Channel API. It can also create a Teams meeting using the onlineMeeting API and return a join URL, which can then be posted to a channel or shared with users.  

    For access control, you would generally implement two layers, such as: 

    Teams app permission policy 

    You can configure a policy in the Teams admin center to allow only a specific group of users to access the app.  

    Backend authorization 

    The application should also validate that the user is a member of the required Azure AD group before executing any actions, ensuring proper security enforcement. 

    Additionally, please note that meetings created via the Graph onlineMeeting API are standalone and are not added to a user’s calendar, and users still need to manually join using the provided meeting link.   Therefore, this requirement can be achieved by combining a Teams app with Microsoft Graph integration and proper policy-based and application-level access control. 

    References: 

    Create channel - Microsoft Graph v1.0 | Microsoft Learn 

    Manage app permission policies in Microsoft Teams - Microsoft Teams | Microsoft Learn 

    Create onlineMeeting - Microsoft Graph v1.0 | Microsoft Learn 

    Please note that this summary is based on my own findings and may not fully address your concerns. To help you reach your goal more effectively, I recommend engaging with [GitHub Community Forum] for a deeper technical dive or to connect with individuals who have relevant experience and expertise. Some approaches may behave differently or be restricted depending on your specific environment and configuration. These forums include many experienced developers and Microsoft specialists who can assist with troubleshooting and guidance.     

    I hope this helps. 

    Please feel free to correct me if I misunderstood your request. If you have any additional concerns, feel free to comment below. I would be more than happy to assist. 

    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. 

    Was this answer helpful?

  2. AI answer

    2026-05-22T15:42:15.29+00:00

    A suitable solution is a Microsoft Teams app with a bot plus Microsoft Graph automation, secured via Azure AD (Entra ID) group membership.

    High-level architecture

    1. Teams app with bot:
      • Build a Teams bot using the Bot Framework and enable the Microsoft Teams channel so it can be used in Teams chats and channels.
      • Package the bot as a Teams app via a Teams app manifest and deploy it to the tenant.
    2. Automation via Microsoft Graph:
      • Use Microsoft Graph to create channels and schedule/start meetings in the target team.
      • The bot (or a backend web service the bot calls) uses application permissions to call Microsoft Graph and automate:
        • Creating channels in a specific team.
        • Creating online meetings and posting the meeting link into a channel or chat.
    3. Security via AD group:
      • Restrict who can invoke the emergency automation by checking the caller’s group membership.
      • The bot receives the user’s Teams identity in each activity; the backend can query Microsoft Graph (or use group claims in tokens) to verify that the user is in the designated AD group before performing any action.

    Key implementation pieces

    1. Bot and Teams integration
      • Create the bot using the Bot Framework and add Microsoft Teams as a channel in Azure Bot Service so the bot can receive and send messages in Teams.
      • Implement commands such as:
        • emergency create-channel <name>
        • emergency start-meeting
      • The bot’s logic:
        1. Validate the user is in the allowed AD group.
        2. If allowed, call backend services/Graph to create the channel and/or meeting.
    2. Automating channels and meetings with Microsoft Graph
      • Use Microsoft Graph to:
        • Create channels in a team: call the channels API for the specific team.
        • Create meetings: call the online meetings or events API and then post the join URL into the relevant channel or chat.
      • These calls are typically done with application permissions so the automation can run without user interaction and can operate even in emergencies.
    3. Tenant-level automation and lifecycle
      • For broader automation (for example, creating multiple teams or channels as part of a larger emergency workflow), use Microsoft Graph to:
        • Create and configure teams, channels, tabs, and apps.
        • Optionally archive or delete emergency teams when the incident is over.
    4. Access control with AD group
      • Configure the Azure AD app registration for the bot/backend with the necessary Microsoft Graph application permissions.
      • Use one of these patterns to enforce the AD group restriction:
        • Group-based conditional logic in the bot: on each command, call Microsoft Graph to check if the user is a member of the emergency group; if not, return a denial message.
        • Group-based app assignment: restrict the Teams app (or the underlying enterprise app) to only the emergency AD group so only those users can install/use it.
    5. Deployment and testing
      • Register the bot and configure the Microsoft Teams channel.
      • Build and test the bot using the Bot Framework Emulator, then install the Teams app in a test team.
      • Verify:
        • Only users in the designated AD group can trigger the emergency commands.
        • Channels are created correctly and meetings are launched and posted into Teams as expected.

    This approach uses standard Teams app patterns (bots) plus Microsoft Graph automation to create channels and launch meetings, with access restricted to a specific AD group.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.