System Requirements - Nebula Synchronizer

Last update:
Created :
Written by Support InfoBridge

Product Page / More Information:

Nebula Synchronizer

To use the Nebula Synchronizer the following requirements must be met:
Note: You can use our Checksite to automatically validate your environment, see this article 

 

SuperOffice Versions:

Other versions will be supported in a later stage.

 

Microsoft Exchange:

  • Microsoft Exchange 2010 (SP2 or higher)
  • Microsoft Exchange 2013
  • Microsoft Exchange 2016
  • Microsoft Office 365 (Business Premium / Business Essentials / Enterprise / Government plan)

Please note: Office 365 Home, Personal and regular Business are not supported, as these plans do not have the Exchange Online component. Compare the Office365 Business plans here.

Please note: IMAP & POP3 accounts are not supported. The IMAP/POP3 protocols do not have support for calendaring and only cover email synchronization.

Please note: Authentication using a solution like Citrix Netscaler is not supported.

 

2-factor authentication for Exchange & Hosted Exchange

2-factor authentication is not supported. However, it is now possible to create an app password when using 2-factor authentication for Exchange on-premise & Hosted Exchange.
An app password is a code that gives an app (like Nebula Synchronizer) or device permission to access your Exchange account.

If your admin has turned on multi-factor authentication for your organization, and you're using apps that connect to your Exchange account, you'll need to generate an app password so the app can connect to Exchange. More info

 

2-factor authentication for O365

When connecting to Office 365 the Nebula Synchronizer uses OAuth. The SuperOffice Application Administrator can setup synchronization for each user. Each user will receive an email and can initiate the OAuth process to give access to its mailbox.

No changes or actions are needed in the Nebula Synchronizer when using multifactor authentication or conditional access in Office 365 / Azure AD because this only affects the OAuth process on the Microsoft side and not the application side.

The Nebula Synchronizer application ID is 32f1d4ba-7de3-40c3-bf1c-7ddf725eab8c

It requires the following permissions:

  • Read all users’ basic profiles
  • Sign in and read user profile
  • Access mailboxes as the sign-in user via Exchange Web Services

 

Autodiscover:

The Exchange Autodiscover must function for correct configuration (KB article). Please make sure before signing up for an account!
When Autodiscover cannot be used due to technical or security reasons we have an advanced option where you can manually add the EWS (Exchange Web Service) and the OAB (Offline Address Book) URL's. More Info

 

Google:

  • Gmail account (Free)
  • G Suite (Basic, Business and Enterprise, more info)

Please note: The Google Administrator needs to enable Administrative API Access and he/she needs to have the role Help Desk Admin or higher (only for G Suite).

 

Supported Clients:
The following clients are successfully tested in combination with the Nebula Synchronizer:

Windows

  • Microsoft Outlook 2007 and higher
  • Outlook Web Access
  • Various other contact/calendar systems either connected to Exchange or Google

Apple Mac OSX

  • OSX 10.11 El Capitan and higher
  • Calendar for Mac (connected to Exchange or Google)
  • Contacts for Mac (connected to Exchange or Google)
  • Various other contact/calendar systems either connected to Exchange or Google

Mobile Devices

  • Basically all mobile devices like mobile phones, tablets etc are supported as long the installed applications connect to a Exchange or Google environment.

Note for Windows: All the used clients are connected to a supported Microsoft Exchange environment
Note for Mac OSX: All the used clients are connected to a supported Microsoft Exchange or Google environment. iCloud is not supported!

 

The Nebula Portal

Once a customer has an account the administrator can login to my.nebulasynchronizer.com and create a Profile. Within the Profile all settings can be administered and user can be added here.
Users can login to their own Nebula portal. For this SuperOffice credentials are needed. An Administer can also login with a username and password. 
Please note: AD authentication is not supported