“We already have Pro Portal. What does AVM-360 do that it can’t?”
MSPs and AV integrators ask us this in almost every conversation, and it’s a fair question. The Microsoft Teams Rooms Pro Management portal is a good tool, and AVM-360 uses its data. The gap lies in what it was built to watch.
Short answer: the Pro Portal manages the Teams device and what is plugged into it. An AV space has a lot more in it than that.
For an estate of all-in-one video bars in small rooms, that may be most of what you need.
A boardroom or town hall has a DSP, amplifiers, ceiling microphones, a control processor, video switching, encoders and often a projector. Most of these are on the network, not on a USB port, and they have no link to Teams. The portal has no view of them.
Microsoft’s documentation says that if the configured audio device isn’t available, the next available microphone or speaker is used, and the signal only shows Unhealthy when none is available.
In a DSP room, the Teams device sees one USB audio connection. A ceiling microphone can drop off, a DSP channel can be muted or an amplifier can fault, and the room still shows green.
The portal’s call-quality result is based mainly on network measures such as packet loss, jitter and delay. It can’t tell you whether the room sounded clear, whether there was echo, or which microphone was at fault. Results also arrive after the call, usually around 30 minutes later and sometimes longer.
The portal reports on signals and on calls that have already happened. It doesn’t place a test call into the room.
The portal covers Microsoft Teams Rooms with a Pro licence. Zoom and Cisco rooms need their own tools, and Microsoft notes that Android rooms currently have more limited management in the portal.
Microsoft has retired its Graph API for Teams devices, so actions such as a restart can’t be triggered from another tool. For an MSP running several clients from one service desk, that means one more portal per client.
AVM-360 talks to AV devices over their native protocols, typically without changes to your existing AV programming.
| What you need to know | Pro Portal | AVM-360 |
| Teams device and app health | Yes | Yes, using Pro Portal and Graph data |
| USB peripherals on the Teams device | Yes | Yes, through the same data |
| DSP status, mute state and audio levels | No | Yes |
| Networked microphones, amplifiers and speakers | No | Yes |
| Control processors, switchers, encoders | No | Yes |
| Projector and display power, input and lamp hours | Connection to the Teams device only | Yes, on networked devices |
| Zoom and Cisco rooms | No | Yes |
| Scheduled automated room tests | No | Yes, premium |
| Remote commands to AV devices | Teams device only | Yes, device-specific |
| One view across brands and platforms | No | Yes |
Your customer doesn’t care which device failed. They care that the meeting didn’t start, and the contract says it’s your problem. If your monitoring ends at the Teams device, you carry an SLA for equipment you can’t see.
This isn’t a choice between the two. The Pro Portal is the right tool for Teams Rooms software, updates and peripherals. AVM-360 adds the rest of the room and brings both into one view.
Does AVM-360 replace the Teams Rooms Pro Portal?
No. It works alongside it and uses its data.
Do simple huddle rooms need more than the Pro Portal?
Often not. The gap grows with room complexity and with the number of brands and platforms.
What does AVM-360 need on site?
A small client-supplied collector, a PC or VM on the same network as the AV devices.
Does the automated room test work on every room?
For Microsoft Teams Rooms it currently runs on Windows-based rooms. It is a premium feature.
Ask for a free 2-room Readiness Test at avm-360.com. We’ll show one room side by side: what the Pro Portal reports, and what AVM-360 adds.
Telemetry and control are not guaranteed and vary by device, firmware, set-up and access. Some features are paid add-ons.