Video meetings

Send an AI agent into a Microsoft Teams meeting

To send an AI agent into a Microsoft Teams meeting, paste the Teams join link into the Video Calls page of Fleece AI Team and choose the agent that should attend. The agent joins as an anonymous external participant with its 3D portrait on camera and its cloned voice active. On Teams the lobby is governed by tenant-wide policy rather than by each host, so whether the agent waits — or is refused outright — is decided by your Microsoft 365 administrator.

At a glance

Meeting link format: https://teams.microsoft.com/l/meetup-join/…
Admission: Lobby, governed by tenant policy rather than per-meeting settings
Teams app required: None — no app to publish to your tenant catalogue
Most common blocker: Anonymous join disabled tenant-wide
What the room hears: The agent's cloned voice, answering in real time
Billing: Per minute from join to leave; 200 min/agent/month on Team

Why Teams is the platform most likely to need one change first

On Google Meet and Zoom, whoever runs the meeting can usually let a guest in. Microsoft Teams pushes that decision up a level: meeting policies live in the Teams admin centre and apply across the tenant, so the person hosting your call may have no ability to admit the agent at all.

The setting that matters most is whether anonymous users can join meetings. If your administrator has turned that off tenant-wide, the agent does not sit in the lobby waiting — it is refused, and no amount of clicking in the meeting will change that.

The second setting decides who bypasses the lobby. Left at its default, external participants wait to be admitted, which is the behaviour you want: somebody in the meeting consciously lets the agent in. What you cannot do is admit something the tenant has already refused.

Getting the agent in without loosening the tenant

The instinct on hitting a lobby problem is to relax the policy for everyone. That is the wrong trade, and administrators are right to resist it — anonymous join is a tenant-wide door.

Teams policies can be assigned per user rather than globally. Applying a meeting policy that permits anonymous join to the handful of people who actually host calls the agent attends keeps the default closed for everybody else. It is more work than flipping the tenant switch, and it is the version a security team will accept.

If your organisation will not allow anonymous participants under any circumstances, that is a legitimate answer, and the agent's other six channels do not depend on it. Teams meetings are one channel out of seven; Slack, email, WhatsApp, SMS, phone and web chat carry the same agent with the same voice.

Copilot summarises. Your agent contributes.

Microsoft 365 Copilot works over the meeting from inside the platform — recap, transcript, follow-ups, all tied to the tenant's own data and permissions. It is very good at telling you what happened.

An agent from Fleece AI Team is doing something different enough that the two do not compete. It has no tenant access and no privileged view of the transcript; it is a guest that speaks. What it knows comes from its own profile: the system prompt you wrote, the documents and URLs you attached, the personality traits you picked.

In practice teams run both. Copilot keeps producing the recap for the organisation, and the agent answers the question that would otherwise have become an action item.

What the agent looks like to the room

The agent shows up as an external participant under its own name, with its generated portrait on camera rather than a set of initials. Teams marks external participants clearly, which is the correct treatment — everyone can see that a guest is present.

Its voice is the one you cloned from a 30-second sample, or a preset if you chose not to clone. The same voice answers your phone line and records WhatsApp voice notes, so an agent your team already talks to elsewhere sounds like itself in the meeting.

When the session ends from the dashboard, the agent leaves and metering stops. As on every platform, minutes are counted from join to leave, so ending the session is worth doing deliberately rather than leaving an agent in a room everyone else has left.

How to send an AI agent into a Microsoft Teams meeting

01
Confirm anonymous join is permitted
Check with your Microsoft 365 administrator that meeting policy allows anonymous users to join. If it is off tenant-wide, the agent is refused rather than queued in the lobby.
02
Prepare the agent's face and voice
Generate the 3D portrait and clone a voice on the agent's profile, or pick a preset voice.
03
Copy the Teams join link
Take the meetup-join URL from the calendar invitation. Nothing is published to your tenant app catalogue.
04
Start the session from Video Calls
Select the agent, paste the link and start. Your remaining balance is shown before the session opens.
05
Admit the agent from the lobby
Unless lobby bypass is configured for external participants, somebody in the meeting admits the agent — the same step as for any outside guest.

Questions, answered

Do I need to publish an app to my Teams tenant?

No. The agent joins from the meeting link as an external participant, so there is nothing to submit to your tenant app catalogue. What you may need is permission for anonymous participants to join meetings at all.

My agent is refused instead of waiting in the lobby. Why?

Almost always because anonymous join is disabled tenant-wide in the Teams admin centre. That is a policy decision above the meeting host, so no one in the call can override it. A per-user meeting policy for the people who host these calls is the narrower fix.

Can we allow the agent without opening anonymous join to everyone?

Yes. Teams meeting policies can be assigned to individual users, so a policy permitting anonymous join can be applied only to the people who host calls the agent attends, leaving the tenant default closed.

Does this work with Teams meetings created from Outlook?

Yes. The join link in an Outlook calendar invitation is the same meetup-join URL, and that is what the agent uses.

Will the agent appear as an external participant?

Yes, and Teams labels it as such. That is the honest outcome: everyone in the meeting can see a guest is present, under the agent's own name and portrait.

What if our organisation will never allow anonymous participants?

Then Teams meetings are not a channel you can use, and the rest of the product is unaffected. The same agent still answers on Slack, email, WhatsApp, SMS, the phone and web chat with the same voice and knowledge.

Send your first agent into a call

Create an agent, generate its portrait, clone a voice, then paste a meeting link. It joins as a participant and answers out loud — and stays reachable on six other channels afterwards.

Start free See pricing