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.
1. Open the Reality Defender RealMeeting listing.
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 shown below:
The last item, "Sign in and read user profile," is added automatically by Microsoft Entra ID whenever an app uses delegated permissions, since it needs to confirm who's signed in before the app can act on that person's behalf. It's not a separate Reality Defender permission, it supports the Chat.ReadBasic and OnlineMeetings.Read permissions, rather than granting any separate access on its own. See the Permissions Requirement Reference below 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 cross-site (third-party) cookies, which RealMeeting needs to load inside Teams. To resolve it, use one of the following:
Use the Teams desktop app (select Open Teams desktop).
Keep cookies blocked and select Show the app anyway.
You'll see the warning twice: first in the pop-up window with the About message, and again in the right pane before the app loads.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.
Log in to your Reality Defender web application (app.realitydefender.ai) and navigate to the Team page.
Find the user you want to update, click the … menu in their row, then select Manage user.
Under Products, check RealMeeting.
Select the appropriate role from the dropdown (e.g., Admin, Contributor, or Viewer), then click Save changes.
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.
Permissions Requirement Reference
The RealMeeting app requests permissions through Microsoft Entra ID authorization models, which grant permissions to the app registration. The Access column indicates whether the permission is used by the application itself or on behalf of a signed-in user (delegated).
For Microsoft’s definitions and consent details, select a permission name or see the Microsoft Graph permissions reference.
Permission | Type | Access | Why RealMeeting needs it |
Calls.AccessMedia.All | 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. |
Consent prompt: “Join group calls and meetings as an app” | Entra ID | Application | Joins a scheduled meeting as a participant so the bot can be present to analyze media. |
Consent prompt: “Read names and members of user chat threads” | Entra ID | Delegated | Identifies the meeting chat and its members so the consent message reaches the right people. Does not include message content. |
Consent prompt: “Read user’s online meetings” | Entra ID | Delegated | Reads the details of the meeting the bot is joining so it can identify and connect to the correct session. |
Note: Delegated Entra ID permissions require a signed-in user, so they may be requested the first time the RealMeeting app is used. See the permissions approval step above for the admin approval process.
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