Everbridge 360 - Windows Pre-deployment Checklist

Before getting started with deploying the Everbridge 360 Windows App to your organization, there are some important checks that should be done.

Know your Organization Code

An Organization Code is a unique code belonging to your Organization that allows your employees to log in to the correct region and Everbridge instance.

This is set up in the Everbridge Suite by an Organization Administrator.

Check you can receive messages

The Everbridge 360 Windows App uses Google's Firebase Cloud Messaging (FCM) to receive notifications. To connect to FCM it uses specific URLs and ports that may be blocked by your organization's firewall. The required domains and ports are listed here.

Once a notification is received it is displayed using Windows Notifications. This will need to be enabled to be able to see any notification pop up. The setting for this can be found be searching for app notifications in the start menu.

Notification connectivity should be tested initially by installing the App from the Microsoft Store (alternatively from https://download.everbridge.net/), and logging in to the App.

Once logged in, you can check the notification connectivity status in the App. Failure to connect will show up with a red notification bell on the Settings page. Successful connections will show a grey icon.

Failure to connect	Successful connection

Once you have a grey icon you can try sending a test normal priority Notification to your Contact. A normal priority Notification will display a Windows notification similar to this.

Log in with SSO

Most organizations will want their contacts to log in with their SSO provider. This should be setup in Everbridge Suite by an Organization Administrator. More information here.

Identify your deployment type

Different organization setups and restrictions will mean a deployment process. Read through the documentation here for MSI or here for MSIX to help identify and prepare what steps will be required.