Virtual games to play on Teams work best when the game runs outside the call. For a Bomb Appétit round, the organiser starts a normal Microsoft Teams meeting, creates a bomb room in a browser and posts its five-letter code in the meeting chat. Each player joins in their own tab, and nobody shares a screen.
What virtual games to play on Teams need from the call
A bomb round needs only voices from a Teams call. The game does not run inside Teams and has no voice chat of its own, so Teams carries the talking while each player's browser carries the game. Microphones that work, a chat for the code and a meeting long enough for a few rounds are all it asks.
That makes setup refreshingly light for a work tool. Nobody installs an app into Teams or asks IT to approve anything inside the meeting. The game is a website: Bomb Appétit runs in any recent Chrome, Firefox, Safari or Edge, on a computer, tablet or phone, and it is free with no account needed.
Each player's browser shows a different part. The Defuser's tab shows the bomb, with its modules and the edgework details printed on the sides of the case. The Experts' tabs show the manual and a status line with the time left, the strikes, the modules solved and whether a needy module is awake. The Experts never receive the bomb, and that split is the whole game: the Defuser describes, the Experts look things up, and everyone talks.
Group size fits a small team call. One bomb takes one Defuser and one to four Experts, so two to five people. A larger team can rotate between rounds or split into groups with a room each.
Time is the last thing to plan. A round lasts from four to fifteen minutes on its clock, depending on the mission, plus a minute or two of setup. A thirty-minute slot fits two or three short rounds. A full session plan for a work group, with timings, is in running a virtual team building round in thirty minutes.
Starting a Teams meeting and opening the bomb in a browser
Start the Teams meeting first, check that every voice comes through, then open the game in a separate browser window. On one screen, put Teams in a narrow window and give the browser the rest. The Defuser needs the most space for the bomb, and Experts need enough width to read a full manual page.
Step list from the invite to the armed bomb
The names are invented: Rosa organises, Kim will defuse, and Lee and Omar are Experts.
- Send the invite. Rosa schedules a Teams meeting as usual and adds a line to the invite: "Bring headphones. We'll play a browser game; no install needed." Guests accept the invite as they would any other.
- Join and check audio. Everyone joins the meeting. Rosa asks each person to say a sentence, and the group confirms each voice is clear. Kim, Lee and Omar plug in headphones.
- Create the bomb room. Rosa opens the Play page in her browser, outside Teams, and creates a room. The page shows a five-letter code. The guests wait on the call.
- Post the code in the meeting chat. Rosa types the code into the Teams meeting chat. Kim, Lee and Omar open the game in their own browsers and join with the code.
- Agree the Defuser out loud. Rosa asks who will defuse. Kim volunteers. Kim picks Defuser in the room; Lee, Omar and Rosa pick Expert.
- Split the manual. The Experts open the manual from the room, which matches the room's rule seed. Lee takes Wires and the Big Button; Omar takes the symbol modules; Rosa watches the status line.
- Arrange windows. Kim makes the bomb tab nearly full screen with Teams in a corner. The Experts put the manual beside a small Teams window.
- Arm the bomb. Rosa, as the room's host, picks a mission, such as First bite with its single module, and starts it. Kim's tab shows the bomb, and the talking begins.
Rosa as organiser and Rosa as room host are two separate jobs that happen to belong to the same person here. The Teams organiser controls the meeting. The room host is whoever created the bomb room, and only they can change the mission and start the bomb.
How do guests get the room code in a Teams meeting?
Guests get the room code from the Teams meeting chat. The room's host types the five letters there once the meeting is running, and each guest copies them into the game's join box. Writing the code beats reading it aloud, because letters spoken over a work call are easily misheard.
The meeting chat is the natural place for three reasons. Everyone in the meeting can see it. It stays visible for the whole meeting, so a latecomer can scroll up and find the code. And it keeps the code inside the meeting, among the people you meant to invite.
Do not post the code in a wide team channel or a company-wide chat unless you want the whole company to be able to join. A room has no password beyond its code. Anyone with the five letters can take a seat while there is one free.
Do not put the code in the meeting invite either, if the invite goes out the day before. The room should be created on the call, just before play. Rooms are temporary, so a code made too early may no longer be open by meeting time, and one created on the spot is certainly fresh.
Between rounds, the same code keeps working. The host resets the room, picks another mission, and everyone stays in place. Only a new evening or a separate group needs a new code.
Can guests without a Teams account join the game?
Yes, on both sides, with a caveat about the call. The game needs no account at all: guests type a display name and play every mission. Teams lets people join many meetings without an account through a browser, though the organiser's admin settings can require a passcode or an account. Check that before inviting outside friends.
Microsoft's guide on how to join a meeting without a Teams account sets out the details. A guest opens the meeting link, chooses to continue in the browser rather than the app, and selects Join now. Teams for web works in Microsoft Edge or Google Chrome. For some meetings, admin settings stop unverified people from joining, so a guest may need a one-time passcode sent to their email or a Teams account. Signed-in people also get more meeting features than guests.
The same guide notes a lobby. A guest who lands in it waits for someone in the meeting to admit them, and is removed if nobody does within 30 minutes. The organiser should keep an eye out for waiting guests, especially at the start.
On the game's side, nothing stands in the way. Bomb Appétit is free, guests can play everything, and signing in with GitHub only adds leaderboards and saved progress. A colleague from another company, a friend or a contractor can all take a seat with nothing more than the code.
A guest joining Teams in the browser now has two browser tabs: the meeting and the game. That works, but it is fiddly on a small laptop. A guest who has a phone handy can join the Teams call on the phone with earbuds and keep the laptop for the game.
The Teams mistake: sharing the screen out of meeting habit
The Teams mistake is the Defuser sharing their screen because that is what people do in meetings. Sharing shows the bomb to every Expert and ends the game's whole point: the Experts must work from the Defuser's words. Keep the bomb unshared. The Experts already see the time and strikes on their own status lines.
The habit is strong in work calls. Someone starts talking about something on their screen, and the reflex is to press share. In a bomb round, the person talking about their screen is always the Defuser, so the reflex fires at the worst possible moment.
Say the rule out loud before the first round: nobody shares a screen during a bomb. The organiser can repeat it when arming each bomb. If someone does share by accident, stop the share at once and carry on; the Experts saw something they should not have, and the round is worth replaying.
The same applies to the manual. An Expert sharing a manual page is less harmful, since it gives nothing away, but it fills everyone's view with a page they may not need and pushes the Defuser's call window around. Experts should read on their own screens.
After a round, sharing is fine. The Defuser can show the case that was just defused, and the group can see what they talked through. Just stop sharing before the host arms the next bomb.
Work groups that play regularly will want a rota so the bomb does not always go to the same confident voice; rotating roles so quiet people get the bomb sets one up. Two colleagues on their own can try the pair setup in 2 player games online with friends. For a call app built around the browser, see games to play on Google Meet. The full set of team activities is in virtual team building games that make everyone talk.