Skip to main content

RealMeeting Installation Guide

This guide provides step-by-step instructions for installing and configuring the Reality Defender RealMeeting app in Microsoft Teams.

Written by Wen Huang

Prerequisites

Before you begin, confirm the following:

  • Microsoft Teams is installed and running on your computer.

  • You have received an invitation to Reality Defender's web application at your Microsoft Teams email address.

  • You have access to a Microsoft Entra Global Administrator who can approve the permissions requested by RealMeeting.

Install RealMeeting from the Microsoft Marketplace

RealMeeting is available in the Microsoft Marketplace.

2. Select Get it now and follow the prompts to add RealMeeting to Microsoft Teams, sign in if prompted.
3. In Microsoft Teams, click Add.
​


4. After the app is added successfully, you can start inviting it to meetings. For instructions, see How to use RealMeeting in a meeting.


If you're asked to grant permissions

If RealMeeting doesn't have the permissions it needs, you'll see this message in the RealMeeting panel:
​
"Your app does not have the required permissions. If you have already authorized the app, please contact your Teams admin to grant organization-level consent."
​
Ask your Microsoft Entra Global Administrator to approve the permissions. See the Permissions Requirement Reference for what each permission does.
​

Once your admin selects Accept, this is approved for your whole organization, other users shouldn't need to repeat this step.

If you see "This app may have issues in the web version of Teams"

If you open RealMeeting in the web version of Microsoft Teams, you may see "This app may have issues in the web version of Teams. However, it should work just fine from Teams Desktop."

This usually means your browser is blocking third-party cookies, which RealMeeting needs to load inside Teams. To resolve it, use one of the following:

  1. Use the Teams desktop app (select Open Teams desktop).

  2. Allow cross-site cookies in your browser, then reload Teams and reopen RealMeeting:
    ​
    In Chrome, go to Settings > Privacy and security > Third-party cookies, and select Allow third-party cookies.
    ​
    If you're in an Incognito or Private window, open Teams in a regular window instead. These windows block third-party cookies by default, so the warning can appear even if you allowed cookies in your regular settings.
    ​

Enable RealMeeting Access for Your Users

In the Reality Defender web application, provide your users with access to RealMeeting and assign the appropriate roles. For more detailed information on RealMeeting roles and permissions, please consult the RealMeeting User Guide.

  1. Log in to your Reality Defender web application (app.realitydefender.ai) and navigate to the Team page.

  2. Find the user you want to update, click the … menu in their row, then select Manage user.

  3. Under Products, check RealMeeting.

  4. Select the appropriate role from the dropdown (e.g., Admin, Contributor, or Viewer), then click Save changes.

  5. If the intended user isn't currently a member of your Reality Defender org, click the Invite team button to invite them. Enter their email address, then select RealMeeting and the appropriate role.

Important: Users must have the same email address for both their Microsoft Teams account and their Reality Defender account to ensure the provisioning process works correctly.

Next Steps

Installation is complete. To confirm the app is working, start a meeting and add RealMeeting from the meeting Apps menu. For detailed instructions, refer to using RealMeeting in a meeting in the user guide, which also explains how to run scans, interpret participant results, and review scan outcomes in the Reality Defender web application.
​


Update RealMeeting

When a new version of RealMeeting is released in the Microsoft Teams store, Teams updates the app automatically. If your Teams admin installed RealMeeting for users in your organization, the update applies without any action from you.
​

If you installed RealMeeting yourself and the update changes the permissions it requests, Teams may ask for your consent first. In that case, you may see an Update option for RealMeeting in Teams. Select it and accept the requested permissions. Until then, you continue to use the previous version.
​

If you see “Your app does not have the required permissions” after an update, ask your Microsoft Entra Global Administrator to approve the updated permissions. Once they approve, other users in your organization shouldn’t need to repeat this step. The current permissions are listed below.
​

Permissions Requirement Reference

The RealMeeting app requests permissions through two Microsoft authorization models. In the table below, Type identifies the authorization model: Entra ID permissions are granted to the app registration, while resource-specific consent (RSC) permissions are limited to a specific Teams team, chat, meeting, or user where the app is installed. Access indicates whether the permission is used by the application itself or on behalf of a signed-in user.
​

Note: This permission set is still evolving as RealMeeting moves to its new architecture, so it may change in a future release. Permission changes may require administrators or users to grant consent again.

Permission

Type

Access

Why RealMeeting needs it

Entra ID

Application

Accesses the real-time audio and video of the meeting. This is the core permission that lets the detector receive the stream it analyzes for deepfake detection.

Entra ID

Application

Joins a scheduled meeting as a participant so the bot can be present to analyze media.

Entra ID

Delegated

Reads the signed-in user’s email address, when available, to identify their account.

Entra ID

Delegated

Allows access tokens to be renewed using refresh tokens so RealMeeting can maintain authorized access without requiring sign-in each time a token expires. This does not grant additional data permissions.

Entra ID

Delegated

Enables Microsoft account sign-in and identifies the authenticated user.

Entra ID

Delegated

Reads basic profile information, such as the signed-in user’s name and user ID, to identify them in RealMeeting.

RSC

Application

Reads participant names, roles, IDs, and join or leave times without requiring a signed-in user.

RSC

Application

Reads basic meeting properties, including the organizer, schedule, join link, and start or end notifications, to identify and monitor the correct meeting.

​

Support

For troubleshooting issues or for flagging questions for the Reality Defender team, please reach out directly to support@realitydefender.com or visit our Help Center

Did this answer your question?