Everbridge 360 - Windows Deployment

Windows Deployment

Click here for deployment troubleshooting and FAQ


MSIX Package

Everbridge 360 for Windows is distributed as an MSIX package. This format ensures reliability and security. You can deliver the MSIX package to client devices using device and application management tools like Microsoft Intune and Microsoft Endpoint Configuration Manager.


Windows Store

Everbridge 360 is also available on the Microsoft Store. You can use the store to find, acquire, distribute, and manage apps for your organization or school. If you’re managing devices, check out the information on using Microsoft Store with managed devices.


MSIX Packaging Format

The MSIX packaging format can be delivered to client devices using device and application management tools. By using AppInstaller to install an MSIX packaged app, the user can right-click and install or double-click the MSIX installer. This approach prompts the user to select the Install button to initiate the installation.


Alternatively, by using available PowerShell cmdlets the installation and uninstallation of an MSIX packaged app can be performed silently.

Add-AppxPackage -Path "...\everbridge360.msix"

Machine wide installations

Installing MSIX packages for all users, or on a VDI image uses a slightly different command, and needs to be run as an administrator.

Add-ProvisionedAppxPackage -PackagePath "...\everbridge.msix" -Online -SkipLicense

Deployment Image Servicing and Management (DISM) cmdlets can be used install, uninstall, and configure MSIX packages on a Windows image before deployment. More information can be found here.


App Installer

Everbridge 360 can be installed using an .appinstaller file. This can be dowloaded from here and comes with automatic updates.


ms-appinstaller protocol

If your organization supports it, the ms-appinstaller protocol allows the Organization Code to be set automatically when the app is opened. You can launch Everbridge 360 using the following URL:



You can also use PowerShell to install an .appinstaller file. While this method doesn’t include the Organization Code, it does come with automatic updates and can be performed silently. Here’s the PowerShell command:

Add-AppxPackage -AppInstallerFile "...\everbridge360.appinstaller"


Bypassing Organization Code

Everbridge 360 requires a user to enter their Organization Code before logging in.

Using the Windows Registry

The App can read the organisation code from prepopulated values in the Window Registry.

For more information see this page.

Using the ebenterprise protocol

This step can also be bypassed by using a custom protocol supported by the App. Running this code on a machine will automatically start the App (if required) and fill out the Organization Code.


This command can be executed by running it from a web browser or using this code from Console/PowerShell/Terminal. Please note, this will only work after the Everbridge 360 application is installed.

start ebenterprise://?companycode=YOURORGANIZATIONCODE


Uninstalling Everbridge 360

Everbridge 360 apps can be uninstalled using deployment tools, PowerShell, or by using AppInstaller.

Get-AppxPackage | where {$_.Name -match 'EverbridgeInc.Everbridge360'} | Remove-AppxPackage -AllUsers

System Requirements

  • Windows 10, version 1709, and later. Windows 11
  • Processors: 2
  • Memory: 3 GB
  • Disk Space: 200 MB


Permission Requirements

Everbridge 360 uses location to allow users to notify your organization of current location for safety purposes. This also required the Geolocation Service in Windows Services to be enabled.

Run at log-in
Everbridge 360 needs to run at log-in to ensure messages can be received by your users

Everbridge 360 uses notifications to alert users when a new message is available. Notifications and Show notification banners should both be enabled.

Domain and Port Permit Listing

The Everbridge App uses the following Domains and Ports to communicate.

  • mobilemember.everbridge.net:443
  • android.clients.google.com:443
  • fcmregistrations.googleapis.com:443
  • fcm.googleapis.com:443
  • mtalk.google.com:5228
Was this article helpful?
0 out of 0 found this helpful

Article Feedback

Article is closed for comments.