Currently Office 365 Integration has only been fully tested on Web Workbench hosted on our AWS shared services platform, i.e. wbi.cloud sites. Although it can be enabled for on-premise installations, certain integration features may not function as expected. 

Prerequisites

To be eligible for this feature, each Workbench user must have an individual Office 365 account licenced for Exchange Online. Emailing in Workbench will not work correctly for users running local Exchange Servers or hybrid deployments. Each user's primary email address in Workbench must exactly match their Office 365 account name.

Implications

Note Email Sender ID setting will be ignored after Office 365 integration is enabled. This means users will not be able to email out of Workbench on behalf of another email address.  A workaround is to disable Office 365 Communication Module. However this removes one of the main benefits of the integration. Therefore it is not recommended to enable Office 365 integration at all, if emailing on behalf of someone else from Workbench is required.

Users will be automatically redirected to Microsoft Office 365 login page when navigating to Workbench base URL AlphaCode.wbi.cloud. After entering Office 365 credentials, they will be prompted to grant application permissions to their accounts. Click Accept. Depending on your Office 365 security settings, a Global Admin of your Office 365 tenant may need to navigate to above URL and grant consent on behalf of the organisation before regular users can log in.

Alternatively if users navigate to AlphaCode.wbi.cloud/Public.aspx/Login they will be presented with the old Workbench Login page. They can log in with the old Workbench credentials, but emailing will NOT work. The Microsoft Sign In button may not work consistently as Microsoft has updated their authentication process. Therefore users should always go to AlphaCode.wbi.cloud.

To prevent users from logging in with the old Workbench login codes and passwords, login method can be enforced on user maintenance in Workbench as per below. Note the only valid options are Any (default) that does not have restrictions and Azure AD (Office 365) that enforces Office 365 login. The other options Forms and Windows are for legacy compatibility and not applicable to most sites.

Enabling Integration

Only after you have communicated the above prerequisites and implications with users and have made sure they fully understand the change, should you request to have this enabled. Do NOT try to enable it by yourself within the application, as we will need to do further configuration behind the scenes for everything to work correctly. The change is not instantaneous and will take effect overnight. Please take this into consideration when you raise the request.