Teams Recording Bots in HR Meetings: A Review Checklist

An interview is about to begin when a participant with a note-taking service's name appears in the Teams lobby. The hiring manager recognizes the candidate's name inside the bot's label and admits it. Only afterward does someone ask where the recording will be stored.

This fictional situation is a useful reason to review meeting procedures now. Microsoft's September 23, 2026 Teams admin release notes say administrators can automatically block identified external bots through meeting policies. For HR teams, the practical question is who may approve an automated attendee before an employee or candidate conversation begins.

Confirm what your organization actually uses

The September 23 entry is a dated product announcement, not confirmation that a particular organizer has a particular policy. Ask your Microsoft 365 administrator what is available and applied to the people arranging HR meetings.

There is also a documentation wrinkle. Microsoft's external-bot administration guide, last updated June 11, describes detection and explicit lobby approval but does not list the newer blocking option in its policy table. Use the release note to start a review, then confirm the current implementation with IT.

Keep the resulting instruction short: who organizes sensitive meetings, which meeting tools are approved, who handles an exception, and what the host should do while a decision is pending. Check existing recurring meetings as well as newly created invitations.

Decide whether a meeting assistant belongs in the conversation

Agree on the purpose before anyone connects a service. An interview, an onboarding discussion and a confidential employee conversation can involve different information and different recordkeeping decisions.

Ask the responsible HR, privacy and IT owners to settle four points:

• Which service and account may be used for this type of meeting?
• What information would the service receive or retain?
• Who may access the resulting notes, transcript or recording?
• What notice, permission and retention steps apply to this conversation?

If an attendee needs an accessibility arrangement, work through the appropriate accommodation process before deciding how the meeting will proceed. A general rule about bots should include a clear route for reviewing those needs. These are organizational decisions; admitting a participant through a software prompt does not answer them.

Give one person responsibility for the lobby

Choose the organizer or co-organizer who will check unexpected attendees. Tell other hosts who owns that decision so a second person does not admit an unfamiliar service while the first person is still reviewing it.

Microsoft's lobby guidance describes extra information and confirmation prompts for identified external bots. A bulk-admission action can also display a warning when identified bots are waiting. Read the prompt and compare the participant with the approved meeting plan.

Do not treat a familiar label as an approval record. In the fictional interview, the organizer could pause admission, ask the candidate whether they requested the assistant, and follow the organization's review route. If the tool has not been approved, arrange the authorized way to continue rather than making a hurried decision in the lobby.

Account for detection limits

Microsoft says its detection can miss external bots and can occasionally identify a person incorrectly. A clean-looking participant list therefore does not establish that no recording is taking place.

Explain the organization's meeting expectations directly to participants. Give the host a short, approved statement about recordings and outside assistants, and identify whom to contact with questions. Avoid asking a manager to improvise legal wording at the start of an interview.

If an unexpected bot has already joined, pause the sensitive discussion and follow the organization's incident and meeting-management procedure. Give the responsible owner the meeting details and what was observed. Removing an attendee does not establish what the service already received or what copies exist.

Practice the decision using fictional material

A short workplace compliance video can show the approved sequence: notice the unexpected attendee, check the meeting plan, contact the decision-maker, and continue through the approved route. Have HR and IT approve the scenario before recording it.

Use a staged meeting with fictional names and no candidate or employee records. Ask the viewer to explain what they would do if the tool were requested by a senior manager, if the reviewer were unavailable, or if an accessibility need required a different arrangement.

Record the procedure version, assignment and completion, then note any unresolved questions. A completion entry documents the activity; it does not establish that every future meeting will follow the procedure.

Keep the approved process easy to find

OdyHR's product overview describes training assignments, completion records, due dates and follow-up connected to employees. Use a workflow conversation to confirm how your team would organize those records and responsibilities.

For custom workplace compliance videos built around your approved meeting steps, talk with OdyHR. Bring a fictional scenario, the decision owners and the completion-tracking requirements so the scope can be reviewed before work begins.