Customer Hosted Install and Setup

Step 1: System Requirements and Machine Prep (Up to 2 days)

For Chime to run, you will need the following:

Machine

• 1 standard physical or virtual machine
  • Can be installed on common platforms including: Microsoft HyperV, Microsoft Azure, Amazon AWS, and Google

OS and Overview

• 64-bit Windows Server®: 2008 R2, 2012, 2012 R2, 2016, and 2019
• Server 2008 R2 requires Desktop Experience feature to be installed
• Server 2012/2012 R2, and 2016 require Media Foundation feature to be installed
• Instant Chime does not require Microsoft IIS since Instant Chime includes HTTP via OWIN

Database Connectivity

• Database access and connection to Microsoft SQL Server or Microsoft SQL Express (typically SQL Express used during evaluation).
  • Account with create access to SQL server (for building and updating the Chime database)
  • Account with read\write access to Chime database
    • The application supports both SQL and Windows server authentication options.
    • Note: For optimal performance, Chime and SQL Server should be in the same physical site.

Additional Machine Setup Information

• Read Access to Windows Active Directory
• .Net Framework 4.7.1+
• Configured Azure Active Directory application registration for Graph API access (see Chime Office 365 Prerequsites.pdf)
• 1+ Bot Framework registered bots per queue
• Microsoft Teams subscription
• 1 SSL certificate Please note: see specifics of SSL cert in the documentation
• Publicly available hostname/ip address
• Review Azure Front Door documentation

Step 1.5: Microsoft Azure Resources

If you would like to host your Chime instance entierly through Azure, here are the resources you would need to provision:

VM
• POC or lower volume Standard DS1 v2 (1 vcpus, 3.5 GiB memory)
• High volume production: Standard D4s v3 (4 vcpus, 16 GiB memory)

Database
• POC or lower volume: Standard S1: 20 DTUs for POC (<250 chats per day per queue)
• High volume production: S3 100 DTU (~1000 chats per day)

Bot
• S1 Standard – 1 or 2 bots per queue


• SSL Certificate

Optional
• Azure Front Door
• Azure Language Translation
• QnA Maker

For a complete list of the system requirements, visit the Machine & System Requirements document.

Please ensure that you have all of the necessary accounts by following the Chime Accounts Checklist with the required permissions before trying to install Chime. It will drastically reduce the amount of time it takes to get everything installed and running.

Step 2: Azure and Teams Prerequisites (2 - 3 days)

Please ensure you have completed Step 1 above and Step 2 before attempting to install Chime. Many common installation issues have arisen from things such as not having all the service accounts with the required permissions.

Before installing Chime for Teams on your machine, you will need to complete a few prerequisites in your Azure Portal. This involves retrieving account information from your Azure Active directory and creating and configuring an App Registration.

At a high level, Chime for Teams will need to be configured to securely communicate with several external services as well as access the following resources:

• Microsoft Azure AD
• Microsoft Office 365 Graph APIs
• Microsoft Bot Framework

As part of this installation and configuration process, a tenant administrator for the Microsoft Office 365 tenant may need to perform several actions in order to provide the necessary authorization for the Chime server.

• Certificate requestor
• Administrator for O365 domain

Step 3: Download and Basic Installation (2 - 4 hours)

During the installation process, you will walk through a very standard Windows installation. You will provide Chime with account information, automatically create the Chime database, and provide the core configuration necessary for Chime to connect with Active Directory and the Chime Database.

If you run into a problem while installing Chime, please send us the logs so we can diagnose the issue and help get you back on track as quickly as possible.

What to do Next?

Once you have installed Chime for Teams, you will want to get it set up for chat routing and be able to customize it for your deployment. Take a look at our page here for the next steps