This document serves as a comprehensive guide that outlines the steps required to integrate a Microsoft Teams tenant with the NetSpeek platform.

---

Prerequisites

Before beginning, confirm the following:

• Microsoft Teams Room (MTR) systems are already enrolled in Microsoft Teams / Intune and connected to your organization.
• You have administrative access to your Microsoft environment, or have an administrator available to assist with the relevant steps.
• You have access to your NetSpeek tenant with permission to manage Connections.

---

Step 1: Configure Microsoft Teams in NetSpeek (Tenant Connector)

1. Ensure you have selected the desired tenant/sub-tenant with the selector in the upper left of the portal interface, and click “Connectors” in the Platform configuration list at the lower left.
2. Click “+ Add Connector”
3. Enter a Connector Name (as an example format, Microsoft Teams – YourOrgName - YourTenantID).
4. Set Connector Type = Microsoft Teams
5. (Optional) Enter a description, with details other NetSpeek users may need to know.
6. Set Connector State = Active.
7. Enter the configurations for:
   • Tenant ID (your Microsoft Entra tenant ID)
     • Relevant Microsoft documentation: Finding your Microsoft Entra tenant ID
   • Admin User Email (the Microsoft 365 Global Admin who will approve the permission request shown in the next step)
8. Click Create new Connector / Update Connector.

---

Step 2: Approve Permissions (Admin Consent)

• After you complete Step 1, NetSpeek will email your configured Microsoft Administrator a secure link.
• This link leads to a Microsoft-operated permissions management page where the permissions the NetSpeek Connector app is requesting are enumerated.
• Review the requested permissions and click Accept.
• Relevant Microsoft documentation: Grant admin consent

Actions Performed → Permissions Required

The table below describes the technical detail related to the permissions request shown in the image above.

Action Name	Description	API used	Required Permissions
REBOOT_DEVICE	Restarts a Windows device remotely for maintenance and update application	Intune	DeviceManagementManagedDevices.Read.All DeviceManagementManagedDevices.PrivilegedOperations.All
GET_STATUS	Retrieves comprehensive device health information including power status, network status, system resources, updates, peripheral health, and Teams sign-in information	Intune/Teamwork Communications	DeviceManagementManagedDevices.Read.All Presence.Read.All
GET_TEAMS_DEVICE_OPERATIONS	Retrieves device compliance policy states and operation history to monitor device compliance status	Intune	DeviceManagementManagedDevices.Read.All DeviceManagementConfiguration.Read.All

---

Step 3: Confirm Enterprise Application Settings

After granting consent:

1. Log in to the Microsoft Entra Admin Center.
2. Navigate to: Enterprise Applications → All applications.
3. Verify that NetSpeek Teams Integration appears in the list.
4. Ensure User assignment required? is set correctly (disabled or assigned to specific resource accounts as needed).

Relevant Microsoft documentation: Manage enterprise app settings

---

Step 4: Apply Teams Application Access Policy

Your Teams environment requires a policy to allow the NetSpeek Connector app to manage room calendars.

1. Open PowerShell as Administrator.
2. Run the following commands (replace placeholders where necessary):

Install-Module MicrosoftTeams

Connect-MicrosoftTeams

New-CsApplicationAccessPolicy `

-Identity "NetSpeekTeamsIntegration" `

-AppIds "{NETSPEEK-APP-ID}" `

-Description "Allow NetSpeek integration app"

# Option 1: Apply globally (all users/rooms)

Grant-CsApplicationAccessPolicy -PolicyName "NetSpeekTeamsIntegration" -Global

# Option 2: Apply per room mailbox (recommended)

Grant-CsApplicationAccessPolicy -Identity "ROOM_OBJECT_ID" -PolicyName "NetSpeekTeamsIntegration"

Relevant Microsoft documentation: Configure app access to Teams resources

---

Step 5: Add Device to NetSpeek Room Canvas

1. From a new WorkSpace, select Locations and search for or navigate to the Room the device will reside in.
2. Select the room you wish to add your Microsoft Teams Room system to
3. The Room Canvas opens by default.
4. Click “Add Devices” and then “Create new“
5. Choose your desired device from the manufacturer → device model list.
   • Note that, as Microsoft does not manufacture hardware, the device to be selected will be equipment manufactured by a hardware vendor, which is registered to your Microsoft environment as a Microsoft Teams Room (MTR) system.
   • It is common for a device to be orchestrated by both hardware-level Connectors (via the hardware manufacturer’s cloud, and/or device APIs via the NetSpeek Edge VM) and a UC platform connector like Microsoft Teams. Ensure the device is not already on the Room Canvas – if it is, add the Microsoft Teams Connector to the existing device’s list of Connectors rather than creating a duplicate device.
6. Configure the appropriate values, and in the “Connectors” section, select the previously created Microsoft Teams Connector.
   • The example below shows multiple Connectors configured for the same device – first, a hardware-level Connector communicating with the device manufacturer, and second, the Microsoft Teams Connector communicating with the Microsoft Teams Room identity in the Microsoft Teams UC platform.
7. In the configuration panel, enter the following fields:
   • The email address of the Room/User identity associated with this space (not the administrator from the prior consent step)

---

Verification

Once the relevant settings described above are configured, to validate the Connector:

• Select a Microsoft Teams Room device in the NetSpeek console, open the Device Actions Tab, and select an available device action. It is generally advisable to test by dispatching a non-intrusive command such as a Get Status.
• On the device, observe the selected action occurring.

---

Permissions Requested → Business Outcome Justification

The table below describes operational value and outcomes related to the permissions requested by the NetSpeek Connector app.

Permission	Business Justification
DeviceManagementManagedDevices.Read.All	Essential for device monitoring and health reporting – Required to retrieve device status, health metrics, diagnostic information, and compliance data from Intune-managed Windows devices. This enables proactive device monitoring and troubleshooting capabilities.
DeviceManagementManagedDevices.ReadWrite.All	Required for device synchronization and update management – Necessary to trigger device sync operations and manage software updates. This ensures devices stay current with security patches and software updates.
DeviceManagementManagedDevices.PrivilegedOperations.All	Critical for device maintenance operations – Required to perform essential device management tasks such as device restarts, which are necessary for applying updates and resolving device issues. This permission enables remote device maintenance without physical access.
DeviceManagementConfiguration.Read.All	Necessary for compliance monitoring – Required to read device compliance policy states and configuration information. This enables monitoring of device compliance status and identification of devices that may require attention or remediation.
Presence.Read.All	Required for Teams integration status reporting – Used to retrieve user presence information for Teams devices, enabling accurate reporting of device sign-in status and user activity for comprehensive device management dashboards.
User.Read (Delegated)	Standard authentication requirement – Basic permission required for user authentication and accessing user profile information. This is a standard Microsoft Graph permission used for secure API access.

---

Support

If you run into any issues during onboarding or have questions, contact NetSpeek Support at support@netspeek.com.