Welcome to the Evoko Naso! This article will give an overview of the necessary steps needed to get M365 connected to the Evoko Workplace. Once your Organizations M365 has been connected to the Evoko Workplace you can then begin to add your buildings/rooms and install/connect your devices.
The Installation Process
- Step 1: Configure M365
- Step 2: Register New Workplace Account
- Step 3: Create Organization
- Step 4: Sign up for Room Booking
- During this step the request is made to the Biamp Registration Team to connect Evoko Workplace to M365 on behalf of the end user.
- Step 5: Grant Permissions to M365 and Add Buildings/Floors/Rooms to Workplace
- Step 6: Claim Naso Device using Naso Device Setup App.
To successfully setup Naso devices in your organization you will need the following:
- Booking System - Microsoft 365 100% Cloud Environment (Along with Admin Privileges)
- Naso Devices - The Room Manager Hardware.
- Network Connection - Wired Ethernet or WiFi (each devices needs internet access)
- iOS or Android Device - Used for claiming the Naso devices via Bluetooth.
Before jumping on to the next step it may be beneficial to familiarize yourself with the various touch points of the Naso ecosystem. We've listed them below with a brief description.
- Naso Devices - Wall mounted touch screen devices used by employees outside of meeting rooms.
- Evoko Workplace Admin - Web Interface used by admins for administering the Naso installation.
- Naso Device Setup - iOS and Android app used by Admins to claim Naso devices via Bluetooth.
- Evoko Workplace - iOS and Android app used by Users for booking meetings.
Microsoft 365 End Points
- To connect all the touchpoints together and integrate with your booking system (Microsoft 365) we manage a back end for you that is hosted on Microsoft Azure. THe back only supports a connection to 100% Cloud M365, and does not support any type of Hybrid or Custom Exchange Environment.
- Naso is designed to be 100% cloud based solution, so the infrastructure will be based in fully cloud based Azure.
- Active Directory Federation Services is not support by the Evoko Naso.
- Network communication between the various touch-points use https/443 with the exception of Naso deices also using http/80 during boot to syncronize time and date - nothing unusual.
- HTTP URLS:
- HTTPS URLs
- Internal Connectivity URLs