RealWear Cloud

Collaborate Technical Info

This article is aimed at Microsoft Admins and Tenant Administrators for enabling Collaborate in your organization

The Collaborate app is an innovative tool that facilitates seamless video communication between Microsoft Teams users and RealWear headsets. Designed with the unique needs of frontline workers in mind, this app provides a reliable and efficient means of connecting, whether for routine operations or on-the-spot troubleshooting. The app’s functionality is built around ease of use and quick accessibility, ensuring that critical connections can be made swiftly and without unnecessary complexity.

Core Feature: Quick Connect

At the heart of Collaborate is the 'Quick Connect' feature, which simplifies the process of linking RealWear headsets with Microsoft Teams users. This feature is especially valuable in environments where time is of the essence, such as in Operations Centres or when Subject Matter Experts need to provide immediate assistance. The Quick Connect function generates a unique code directly on the RealWear headset, allowing Teams users to connect effortlessly and without delay.

Core Feature: Inbound (introduced March 2025 - v2.0)

Introduced in March 2025, Collaborate now acts as a Teams extension, this means if you're logged in Teams users in your tenant can now call you direct, causing your headset to ring and flash, you can accept the call on your headset

Core Feature: Outbound User / Team Dialing (introduced March 2025 - v2.0)

You can now search for users to call or Teams to call and call them directly from the headset

From the Team menu, you can can call individual members in the team.

Collaborate Flow

The following diagram provides a detailed overview of the workflow within the Collaborate app as it operates on RealWear headsets. This workflow is divided into two distinct parts: the Android app running on the RealWear headset and the Microsoft Teams Addon app, each playing a crucial role in the overall operation.

Picture 2-1

V2.0: Updated March 2025: New features and required permissions

In version 2.0 we introduced new features such as inbound, outbound, team calling. To enable these features your administrator will be required to enable new permissions to allow the app to function correctly.
If the permissions are not granted, you are presented with this screen

How to enable the new permissions:

Permissions are granular and can be enabled by use case

All permissions requested are Delegated Style permissions: https://learn.microsoft.com/en-us/entra/identity-platform/delegated-access-primer

To enable all the new permissions (list below) please have your Azure admin visit this link:

https://login.microsoftonline.com/organizations/adminconsent?client_id=32dfa5db-1bf5-4c70-bb8b-ab2fe987bf2b

The device must be restarted after enabling the permissions

Granular permissions can be enabled by appending the permission below to the url above

For example:

https://login.microsoftonline.com/organizations/v2.0/adminconsent?client_id=32dfa5db-1bf5-4c70-bb8b-ab2fe987bf2b&scope=https://graph.microsoft.com/User.ReadBasic.All

Permission Reason Why
https://graph.microsoft.com/Calendars.Read Viewing Calendar events to show in the Calendar options
https://graph.microsoft.com/User.ReadBasic.All Read user contacts, loading user profile images
https://graph.microsoft.com/Group.Read.All Read user groups and calling groups
https://graph.microsoft.com/Presence.ReadWrite Set user status to Online / Away / Busy, depending on their status
https://auth.msft.communication.azure.com/Teams.ManageCalls Obtaining Azure Communication Token, allowing the signed in user to initiate, accept and join calls.
https://auth.msft.communication.azure.com/Teams.ManageChats Used exclusively for call functionality, the ManageChats permission is unused but a prerequisite of for call functionality.
ManageChats permission is unused but a prerequisite of for call functionality. Information from Microsoft can be found here

api://app.realwearteams.com/32dfa5db-1bf5-4c70-bb8b-ab2fe987bf2b/access_as_user

The 'user_impersonation' permission enables access to a trusted authentication service, ensuring secure communication token exchange. Learn more from Microsoft here

If the app fails due to "The app is trying to access a service '1fd5118e-2576-4263-8130-9503064c837a' (Azure Communication Services) that your organization '{GUID}' lacks a service principal for”

These steps are for Azure Admins

You must enable ACS inside your Azure Tenant using a PowerShell Scripts follow the steps below:

1. Connect to MSGraph 2. If MSGraph unavailable Install it3.  Install the ACS Service Principal

To learn more about why these permissions are needed you can visit the Microsoft guidance here: https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/manage-teams-identity?pivots=programming-language-csharp#step-5-provide-administrator-consent

Technical Requirements

ACS

What is ACS?
Azure Communication Services is the technology that underpins Microsoft Teams, every meeting and chat in Microsoft Teams runs on ACS, rather than developing code from scratch, developers can utilize what Microsoft has build for their own apps.

Teams Add In App

Desktop PC running Windows or Mac with the latest version of MS Teams

iOS or Android Device running latest OS.

Microsoft Teams for Web

RealWear Headset

Any Navigator or HMT series headset running Android 10 or later.

Overview

RealWear Collaborate is a aR friendly frontend application for conducting Microsoft Teams calls on RealWear Headsets, It offers two way communication and screen sharing. You can see the expert you're talking to and they can see the frontline worker view.

Network Quality and Bandwidth

The quality of a Collaborate / Teams call depends on the bandwidth provided by your ISP. Certain elements need to be taken into consideration when holding a call using this network, such as Latency, Packet loss and Inter-packet arrival jitter (also known as jitter).

Collaborate supports the same bandwidth as Microsoft Teams

Bandwidth

Scenarios

500 Kbps

Peer-to-peer quality video calling 360 pixels at 15 FPS

1.2 Mbps

Peer-to-peer HD-quality video calling with resolution of HD 720 pixels at 15 FPS

1.5 Mbps

Peer-to-peer HD-quality video calling with resolution of HD 720 pixels at 15 FPS

500 Kbps/1 Mbps

Group video calling

1 Mbps/2 Mbps

HD group video calling, 540-pixel videos on a 1080-pixel screen

 Firewall Configuration

Collaborate uses the same Firewall rules as Microsoft Teams

 

Category

IP ranges or FQDN

Ports

Media traffic

Range of Azure public cloud IP addresses 20.202.0.0/16 The range provided above is the range of IP addresses on either Media processor or Azure Communication Services TURN service.

UDP 3478 through 3481, TCP ports 443

Signaling, telemetry, registration

*.skype.com, *.microsoft.com, *.azure.net, *.azure.com, *.office.com

TCP 443, 80

RealWear Teams UI

https://app.realwearteams.com

TCP 443

Authenticated User Communication Token

htps://realwear-teams-token.azurewebsites.net/api/Function

TCP 443

Firebase Analytics (optional)

https://app-measurement

TCP 443

Sentry.io (optional)

https://04504485976014848.ingest.sentry.io

TCP 443

Localize (for up to date translations)

https://api.lokalise.com/

https://ota.lokalise.com/

TCP 443

 

FAQ

What is Collaborate?

Collaborate is a Teams Frontend Application built by RealWear to enable simple voice-controlled access to Microsoft Teams meetings from RealWear Headsets

Does Collaborate collect any of my data?

Collaborate does not collect any personally identifiable information, we do collect IP address and locale in line with our privacy policy for troubleshooting purposes. Collaborate leverages Microsoft SSO Device Code Login to Authenticate, these credentials are never stored by RealWear. https://www.realwear.com/legal/collaborate-privacy-policy.

The Collaborate app stores contact names, the Azure Entra Id and call start time in an on device database for the purpose of 'recent calls' and phone book searching, this is local to the headset.

Does the MS Teams Add In app collect any of my data?

The RealWear MS Teams app doesn't collect any data of calls etc.

What permissions does Collaborate need?

For all the features of Collaborate v2 needs:

User.Read

Calendars.ReadWrite

Group.Read.All

offline_access

OnlineMeetings.ReadWrite

openid

Presence.ReadWrite

profile

User.ReadBasic.All

Teams.ManageCalls

Teams.ManageChat

access_as_user

All permissions requested are Delegated Style permissions: https://learn.microsoft.com/en-us/entra/identity-platform/delegated-access-primer

You can find detailed explanations about granting permissions from Microsoft here: https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/manage-teams-identity?pivots=programming-language-java#administrator-actions

For the Microsoft Add in app. These permissions will be requested when the user/admin installs the RealWear app in Microsoft Teams, an admin may need to grant permission.

What technology does Collaborate use?

Collaborate and the accompanying Teams app uses Azure Communication Services under the hood, ACS is the backbone to Microsoft Teams, if Teams is already allowed in your organisation, Collaborate should work the same way.

Can I use Collaborate without logging into Microsoft Teams?

Yes, Collaborate offers a guest mode that allows you to join meetings without the need to log in to your Microsoft Teams account on the headset

Does Collaborate support other collaboration platforms besides Microsoft Teams?

Currently, Collaborate is designed to work specifically with Microsoft Teams using Azure Communication Services.

Can I schedule and manage meetings through Collaborate?

Collaborate allows access to your Microsoft Teams meetings and your calendar, but for detailed meeting management, you may need to use the Teams interface on another device.