Category Archives: Microsoft Teams

Manage Microsoft Teams Room Devices Peripherals from LogiSync Portal

For Microsoft Teams Rooms Logitech is been one of the preferred solution.
And the Logitech meeting room device peripherals are widely been utilized. It’s critical to remember that the Logitech device peripherals must be updated in order for them to work properly.

Usually when we have the Microsoft Teams Premium service enrolled the best part is these device peripheral updates are delivered via their regular windows update channel. When we run the Teams Room Standard license it is very important to note that the meeting room device peripherals camera, mic and camera updates needs to be performed manually. In those cases managing them from the LogiSync app will be greatly beneficial.

Logisync Portal helps Administrators a lot to manage the Teams Logitech devices completely from the portal. With the Logitech Sync at the moment we have 2 options either to monitor the devices only or to monitor them plus Update the device’s firmware and make any necessary changes to the device settings.

Logitech Sync Setup consists of two parts Sync App and Sync Portal

With the Sync App we can update firmware of the connected device peripherals, and troubleshoot difficulties on these peripherals with the help of the Sync App installed on your meeting room PC.

With the Sync Portal we can remotely manage connected meeting room devices for the whole organization. It also allows us for remote device monitoring, scheduled firmware updates and more.

In this blog we will run through the steps that will be used to provision the LogiSync portal for Microsoft Teams Windows devices.

The first step to proceed with this is to start signing up with the sync portal from this link https://sync.logitech.com/sign-up/account

At the moment of writing this post the Logitech Sync’s core monitoring and management options which is available is totally free and no licenses and invoices are sent by Logitech.

The moment when we signup for the Logitech sync the first option is to provision Sync App provisioning package on all the meeting room devices.

It is available in the bulk provisioning section for download.

We have options to download the version macOS or Windows.

There is an option to bulk provision them via SCCM or JAMF and via Intune for huge number of bulk deployments. The SCCM bundle is available from the Logitech website here where they have provided instructions on how to deploy them via SCCM. We also have option where they show how to deploy them via JAMF.

We also need to make sure that the firewall connections are allowed so that the LogiSync devices can start communicating with the Logisync portal. They have mentioned the required ports, protocol with the destination addresses that needs to be whitelisted before provisioning as per their website

The moment after the sync app is provisioned in the meeting room devices we can see that the devices will start reporting to the LogiSync portal which is hosted in the cloud.

In my example I have 2 meeting rooms which i have attempted to install the package. They are showing in the portal. On a first look in the Dashboard they provide information on healthy rooms, rooms with issues, snoozed rooms and rooms availability.

Scrolling down further provides us more useful information on Meeting room with issues for the past 30 days, rooms with occupancy limit alerts in the last 30 days.

These above information appears to me to be extremely important information from the admin standpoint on getting a sneak peek at the overview of meeting room devices from a monitoring perspective. We do have an option for exporting this report which is of great beneficial to provide this to the required team.

When we look in a whole overview and a fully updated device peripherals we get the below screen.

And further moving into the inventory we can see all the available connected devices with the Room name, Group can be defined, connected external Peripherals, Sync version, status, health , Use state and seat count can be defined.

There is also devices section next to the rooms which provides information on the connected Logitech Peripherals. In my example have only C930e camera and that shows in the device section.

We can select the device and perform the update which is of great help for the admins. There is also an option to schedule a firmware update from Sync Portal which could be done during the off business hours.

We have option to add the seat count manually here and provide names for each meeting rooms.

Further more we have insights which can help us to better understand the utilization of the meeting rooms.

Furthermore we have option called alerts through which we can setup alerts for the enabled rooms that are provisioned before June 2022.

Firstly we have the option to setup the alerts via email

In the email notification we have option to trigger alerts when the device is in a error state, warnings, rooms going offline and if there are any occupancy limit alerts.

And for the occupancy limit we need to setup the threshold level like example below.

There is also option to mute alerts which is of great help because as we all know the meeting room devices performs a nightly reboot for windows and Teams App update. So we can set the option mute alerts only during that time.

And at last we have an option to set grace period during when if the issue occurs the alerts are not triggered. There is also an option to send email case by case or send them in batches.

On a successful setup of an email alert notification we can see the screen like below.

We also have option to trigger an incident via service now ticketing system when the devices goes into malfunctioning state.

There is also an option to enable single sign on for the logisync portal which eases the management part of this administration portal.

There is also personal devices section which is in beta release that can help admins to manage the Logitech device peripherals of the end user devices.

And there is role based access which can be delegated to administrators for managing this portal.

At this time Logitech currently only supports Rally, Rally Camera, and MeetUp devices that are connected to a Windows or macOS computer.

Overall Logisync setup  can help us a lot in managing Microsoft Teams connected conference room devices peripherals all in one place. This will really help organizations where they have ecosystem combination of Teams Standard Licensing and Teams Premium Licensing model where the devices with Teams Standard Licensing model can greatly benefit from this portal for performing the device peripheral updates from the Logisync portal that comes free of cost.

For more information on the Logisync you can take a look here on their website.

Logitech TAP Scheduler for Microsoft Teams

Meeting room scheduler makes it simple to locate and reserve the appropriate room. There are lot of meeting room schedulers available in the market which fetches the room availability from Exchange Online or Exchange OnPremise Accounts. These TAP meeting room schedulers usually helps us to see the meeting details at a glance and reserve the room for adhoc or future meetings. This helps the business a lot because most of the time people find it hard to schedule adhoc meeting in a meeting room to check for the free/busy availability in the Calendar.

Having said the benefits of the meeting room panels We’ll look at the Logitech TAP scheduling and how it works with Microsoft Teams.

At first appearance, from the hardware perspective it appears to have a clean and convenient setup, with features such as Easy Installation with Included Mounts, Hide Cabling for a Clean Setup, 10.1″ touchscreen, Anti-fingerprint, robust build, and meeting availability lighting indicators.

The device is powered by the POE cable which makes the cabling and mounting this device on the wall in a very easier manner. When turning on the device we get the below screen which is evident that the device is powered by the Logitech Collab OS.

Continue reading

Create a QnA maker with no code experience and publish them in Microsoft Teams

QnA maker helps us in building a basic bot that can handle first level of recurring tasks. This benefits the end user in providing the faster response and answer to their question. This benefits the end user in getting a quicker response and answer to their inquiry. We can reduce a lot of repeating chores at the operational level with QnA maker. For example, we may use QnA maker to provide first-level NOC monitoring help, which will benefit both the requestor and the first-line support team significantly.

We had a look through a similar article 2.8 years back how to create a azure web app bot here

Microsoft’s investment in cognitive services has been fantastic, as they have simplified the automation process and integration with Microsoft Teams while requiring little or no coding knowledge. This greatly aids us in building QnA makers and bringing them live in a matter of days providing we keep all of our knowledge bases up to date and accessible.

In this article we will go through the steps that is required to integrate the QnA Maker with Microsoft Teams.

Below are the main requirements to build QnA Maker and integrating them with Teams :

  1. QnA Maker needs to be created.
  2. Bot Framework Composer
  3. A basic bot that is required to handle the interaction
  4. App Package that needs to be created

The first and the foremost thing is to create the QnA maker from the Azure portal. We can create them easily by navigating to https://QnAMaker.ai

Choose the appropriate Subscription, Resource Group and the Pricing Tier.

Continue reading

Microsoft Teams – Enable end to end encryption for Teams Calls

Teams encrypts all communication by default with industry-standard technologies including Transport Layer Security (TLS) and Secure Real-Time Transport Protocol (SRTP). By default TLS authenticates all traffic and encrypts them. SRTP is used for media traffic and also encrypted. And by default they are definitely Trustworthy and this end to end encryption is definitely not required unless there is a specific business case.

Last month Microsoft announced the public preview of the end to end encryption as per this blog

The goal of end-to-end encryption is to prevent data from being read or secretly manipulated by anybody other than the sender and recipient. The sender encrypts the calls, chats & files, but the third party or even the service provider has no way of decrypting them and stores them encrypted. The recipients obtain and decrypt the encrypted data on their own.

There may be a situation when a few participants are dealing with business-critical data or sensitive information, and they want more increased security to meet their compliance and regulatory obligations. In some circumstances, end-to-end encryption can be used to accommodate those scenarios, and it can be enabled exclusively for those users who are specifically targeted.

Continue reading

Microsoft Teams – Setup Dynamic Emergency Calling

Dynamic emergency calling assists in routing calls and notifying security personnel during an emergency scenario based on the location of the Teams Client. Earlier this setup was working on Microsoft Calling plan and Direct Routing. Now with Operator connect being public GA setting up a emergency calling is a mandatory prerequisite before enabling the operator connect on the Teams Admin Center.

The dynamic emergency calling works completely with the help of the Location information service. The Location Information Service (LIS) delivers geodetic (latitude/longitude) or civic address location information. The LIS is used by emergency services to make location-based call routing decisions and to properly locate callers for dispatch. LIS addresses the intermediate solution for providing e911 service for users of VoIP telephony.

Microsoft Teams uses this same LIS based on the Network Topology Information. This is collected from the Teams Client location data which works based upon two information

  1. Network Settings
  2. Location Information Service Configuration
Continue reading

Microsoft Teams – Provide telephony numbers in Teams with Operator Connect

With Operator connect we will be able to manage partnerships with our local telephony providers and provide telephony features to end users in Microsoft Teams. We can evict the need of managing & maintenance of SBC locally in the datacenter unless we have some specific requirements for routing calls to another ip-pbx environment within the organization .This is a big advantage for customers who want to go completely to the cloud and eliminate their on-premise dependency.

Microsoft recently announced Operator Connect to be General and it can be a good start for organizations which has less dependency on legacy PBX integrations in their environment. For instance when a customer having only Skype for business, SBC and a SIP Trunk with their local telephony provider in their current configuration can easily think of moving this enterprise voice service to cloud easily by benefiting the operator connect service.

At the moment of writing this post there are 22 operators present in this program which supports upto 60 regions all over the world with Microsoft and the list can definitely grow in future. In this blog we will run through the steps to enable operator connect and the steps to enable them with the provider NTT.

Below prerequisites are required from Office 365 tenant to evaluate the operator connect service:

  1. Users must have minimum E1+Phone System, E3+Phone System or E5 License.
  2. All these users leveraging the operator connect service must be in Teams Only mode.
  3. Emergency Address must be created and assigned to these users.

In our case we are testing from the location Netherlands and hence we have only Netherlands defined as Emergency address.

Continue reading

Microsoft Teams – Enable content camera for your meeting rooms whiteboard

A content camera can be used with a Microsoft Teams Room system. A content camera collaborates with image-processing software and a whiteboard to enable a presenter to draw on an analog whiteboard and share the content with remote participants.

In this blog we will run through the steps to enable content camera on Teams Room Systems.

There are few prerequisites that needs to be prepared before trying this setup:

  1. This content camera should be pointed at the room’s whiteboard. Please keep in mind that content camera has physical infrastructure requirements that must be considered. It’s usually a piece of equipment (a supported content camera) that hangs from the ceiling and faces the whiteboard.
  2. The writing board must be mandatorily white in color. Other colors are not supported.
  3. A supported content camera as per Microsoft Recommendation on this link needs to be used mandatorily for this functionality.

The camera’s positioning is influenced by the size of the whiteboard used for sharing. The following are some suggestions for board size from Microsoft:

  • 3–6 ft. (0.9–1.8 m) wide — Supported best suited for medium sized rooms.
  • 6–9 ft. (1.8–2.7 m) wide — Recommended best recommended for medium-large rooms.
  • 9–12 ft. (2.7–3.6 m) wide — Supported suitable for board rooms.
  • Above 12 ft. (3.6 m) wide — camera covers 9–12 ft. (2.7–3.6 m) and crops the rest.

The camera can be placed up to 6 in. (152 mm) above the whiteboard’s top and centered on the whiteboard.

Continue reading

Configure your Teams Room Systems to join WebEx and Zoom Meetings

In the current scenario most of the Organizations are running Teams Room systems as their meeting room solution from their Offices. Few of their customers, vendors and partners host their meetings from Zoom ,WebEx or other meeting solutions. In these unique circumstances, we will be hitting in a scenario where there are people attending the meetings from Teams Room from our organization and the meeting sent by vendor or a customer might be Web-Ex or Zoom.

Knowing this requirement Microsoft released a supported Teams App version in the mid of last year for the Room Systems to join Cisco WebEx Meetings from a Teams enabled room system with the direct guest join. Later this option was extended to attend a Zoom Meetings as well from the Teams App version 4.6.20.0. We’ll walk through the procedures to enable Teams Room Devices to join the 3rd party meetings Cisco WebEx and Zoom Meetings.

There are few prerequisites to be met in order to join WebEx and Zoom Meetings from a Teams Room System

  1. Make sure the WebEx and the Zoom Meeting URLs are fully whitelisted in your proxy and in your network to fully support this scenario.
  2. Configure Office 365 Threat Protection and Link Rewrite exclusion list for WebEx and Zoom Meeting URLs.
  3. Configure your Room Mailbox to automatically accept and process the invitation from Zoom and WebEx.
  4. Configure this settings in your Room Systems devices , so that they are ready for this functionality.

To make this work for the Room Mailbox Connect to your Office 365 Exchange Online Tenant and check for the current setup for accepting the meeting room from a 3rd party meeting invites by running the below command.

Get-CalendarProcesing -Identity UserPrincipalNameOfRoomMailbox | Fl Identity,ProcessExternalMeetingMessages

In our case the value is set to false which is by default. The ProcessExternalMeetingMessages parameter specifies whether to process meeting requests that originate outside the Exchange organization.

Run this command on the Room Mailbox of the Room System to accept meeting requests from Zoom and WebEx

Set-CalendarProcessing roomnl@ezcloudinfo.com -ProcessExternalMeetingMessages $True -DeleteComments $False -DeleteSubject $False

Now we could see that the value ProcessExternalMeetingMessages is set to True

Continue reading

Microsoft Teams Rooms – Start casting content directly from your Mobile Device without setting up a Meeting

One of the new feature that was announced in last week for Teams Rooms update was an option to directly cast your content from the mobile device without setting up a formal meeting. This is really beneficial when we need to share some thing directly from our mobile device to the participants in the meeting where we have a meeting room involved as a participant.

To start with utilizing this feature the Microsoft Teams App must be installed on your mobile , Bluetooth must be turned on , both the mobile device and the Teams Room system must be connected to the same network. At this moment the Teams Room must be running on Windows and must be within 10 meters range from the mobile device.

Its very easy to utilize all we need to to is open Teams App on the device – Go to the more option and click on Cast your screen

Once after we do that we are prompted with the below screen and all we need to do is just click on get started.

Continue reading

Enable Modern Authentication on Microsoft Teams Room Devices

As we all know the basic authentication will be retired for Office 365 sooner and its high time for us to enforce Modern Authentication on all clients. When most of the organizations have already enabled Modern Authentication which is a good sign. However there are cases where the modern authentication cannot be interactive for the 2nd factor authentication ,needs some planning on those special cases and they have exceptions. For instance Room Systems they are having resource accounts with Teams Enabled and Exchange Online where these resource accounts cannot have modern authentication enabled with MFA like normal user accounts to approve for the 2nd factor authentication.

Post Microsoft Teams Room App version 4.4.25.0 we have the option to enable Modern Authentication on the devices capable of hosting Microsoft Teams Meeting. The account management of the Teams Room devices is set at the application level.

Continue reading
%d bloggers like this: