This tutorial shows you how to configure a SiteKiosk Online project that launches the installed Microsoft Teams application on a Windows 11 device. This setup is ideal for shared meeting stations, employee self-service environments, and HR kiosks where users need a simple, controlled way to join Teams meetings without access to a dedicated workstation.
Before You Begin
- Confirm that SiteKiosk Online is installed and the Windows device is enrolled in your account. See the SiteKiosk Online installation tutorial if needed.
- Ensure the Microsoft Teams application is installed on the Windows 11 device.
- Verify that the device has an internet connection and any required camera, microphone, speakers, or headset hardware.
- Review self-service kiosk security considerations before deploying the configuration to public or shared devices.
See video tutorial below or scroll down for the step-by-step text version.
Create a Microsoft Teams Project
- Sign in to your SiteKiosk Online account at us.sitekiosk.online.
- Select Projects from the main navigation.
- Click Create Project.
- Select the Single App template because the project will launch one application: Microsoft Teams.
- Enter a descriptive project name, such as MS Teams Demo or Teams Meeting Station.
- Click the green Create Project button.
Configure the Teams Launch Button
- Open the newly created project.
- Select the large project button and click Edit.
- Scroll to the Action section.
- Choose the option to Start app/program.
- Enter the Microsoft Teams executable path using the local alias:
%LOCALAPPDATA%\Microsoft\WindowsApps\ms-teams.exe. - Save the button configuration.
Using %LOCALAPPDATA% is important because the Teams application folder name or physical installation path may change after Teams updates. The local alias points SiteKiosk Online to the current user’s AppData location, helping the project continue to launch Teams reliably.
Check for Conflicting Button Actions
Before publishing, review the button’s other settings and remove any pop-up action that may already be enabled. A pop-up can prevent the button from launching Teams directly or cause an unexpected screen to appear before the application starts.
- Return to the button editor.
- Locate the pop-up configuration or pop-up icon in the elements on this page view.
- Deactivate the pop-up action if it is enabled.
- Confirm that Start an application is the only required action.
- Save the project changes.
Publish to Your Devices
- Click Publish in the SiteKiosk Online project editor.
- Select the Windows devices that should receive the Teams meeting project.
- Use immediate publishing only for testing or when it is safe to interrupt the current device session.
- Leave immediate publishing unchecked in production environments so the update can wait for an appropriate idle state.
- Confirm the publish action and allow the selected devices to download the updated project content.
After the project is published, the device should enter the configured SiteKiosk Online experience. Select the project’s Start Application button to launch Microsoft Teams.
Join a Teams Meeting
- On the kiosk device, select Start Application to open Microsoft Teams.
- Select Join a meeting in Teams.
- Enter the meeting ID, passcode, or other meeting information provided by the meeting organizer.
- Enter a display name if Teams requests one.
- Select Join.
- Wait for the meeting host to admit the participant if the meeting lobby is enabled.
Once admitted, the user can participate in the Teams meeting using the hardware connected to the kiosk. For a shared-use deployment, validate camera, microphone, speaker, and headset behavior before making the station available to users.
Optional: Disable the Virtual Keyboard
SiteKiosk Online can display a virtual touch keyboard when users select text fields. If the device uses a physical keyboard, or if you do not want an on-screen keyboard shown in Teams, disable the feature in the project settings.
- Open the SiteKiosk Online project settings.
- Select User Interface.
- Clear the Enable Virtual Touch Keyboard checkbox.
- Save the settings.
- Publish the updated project to the applicable devices.
Recommended Use Cases
A locked-down Teams station is useful for employees who do not have an assigned computer, visitors who need to join a scheduled meeting, or organizations creating shared communication points in warehouses, manufacturing areas, break rooms, reception areas, and HR locations. For more ideas, review the benefits of HR kiosks for employee self-service and the Human Resources Services Kiosk template.
Frequently Asked Questions
Q: What application path should I use to launch Microsoft Teams from SiteKiosk Online?
A: Use %LOCALAPPDATA%\Microsoft\WindowsApps\ms-teams.exe. This local alias helps account for Teams installation-path changes that can occur after application updates.
Q: Why does the Teams button open a pop-up along with Microsoft Teams?
A: Check the project button properties for an enabled pop-up action. Disable the pop-up so that the Start an application action only launches Teams directly.
Q: Should I enable immediate publishing for production Teams kiosks?
A: Usually no. Immediate publishing can update a device while someone is actively using it. For production devices, allow updates to apply when the kiosk reaches an appropriate idle state.
Q: Can users join a Teams meeting without signing in?
A: This depends on the Teams meeting organizer’s policies and the meeting configuration. If guest access is allowed, users may be able to join by entering a meeting ID, passcode, and display name.
Q: How do I remove the on-screen keyboard from the Teams station?
A: Open the SiteKiosk Online project settings, select User Interface, clear Enable Virtual Touch Keyboard, save the change, and republish the project.
Q: Is this configuration appropriate for employee self-service?
A: Yes. A dedicated Teams kiosk can provide employees without assigned workstations with controlled access to virtual HR meetings, training sessions, interviews, and other scheduled communications.