How to add a Teams Media Bot in an online meeting.

@NasarKhan - Thanks for bringing this issue to our attention. 

Root Causes of the issues

Issue #1 (Bot Not Visible When Joining Active Meeting):

• The bot does not properly negotiate media with current participants.
• The call establishment handshake is incomplete before the bot tries to record.
• Firewall or port restrictions on the Azure VM may be blocking media streams.

Issue #2 (External Users Redirected to New Meeting):

• The bot joins using an application identity without the necessary tenant context.
• Without a resource account, the bot cannot interact with lobby or admission policies.
• External users cannot be admitted because the bot lacks the required identity and permissions.
  
  

Solutions
1: Delayed Join

1. Separate the calling webhook from the messaging endpoint in Azure Bot Service.
2. Configure the media platform with the correct VM public IP and FQDN.
3. Ensure required ports are open on the Azure VM:
   • TCP 443, 8445
   • UDP 12332-12432 for media streams
4. Wait for the "call established" state before starting the recording process.
5. Verify the SSL certificate on the VM FQDN for secure signaling
   .

2: External User Access

1. Create a resource account using PowerShell:
   • Run New-CsOnlineApplicationInstance
   • Link it to your bot’s App ID
2. Assign an application access policy globally or to specific users.
3. Update the bot to join meetings with the resource account identity instead of app-only authentication.
4. Assign appropriate Teams meeting policies to the resource account for recording and lobby permissions.

Please let us know if you have any other query here.