Introduction

This guide provides a comprehensive overview of the key enhancements and features introduced in the TeamConnect O365 Add-In 4.2, task management. It covers various scenarios for managing the Add-in based on different Admin settings configurations. Designed as a resource for TeamConnect Admins, it outlines essential administrative tasks to optimize the operation of the Add-in, including the migration of tasks from the Outlook Plugin to the Outlook Add-in. 

If you're new to the process, we recommend familiarizing yourself with the O365 Add-In 4.0 released with TeamConnect 7.1 (November 2023).

• To learn more about the reasons behind the transition from the Office Suite Plugin to the Outlook Add-in, refer to O365 Outlook Plugin Vs Add-in.

What's New in TeamConnect O365 Add-In Releases

TeamConnect O365 Add-In 4.0: This release in November 2023, introduced TeamConnect O365 Add-In 4.0 using the latest Microsoft Graph API technology.  This integration is designed to streamline access to TeamConnect features(matter management, appointments, and document management) directly through the O365 Add-in interface. 

TeamConnect O365 Add-In 4.1: This release in May 2024, was only applicable to clients who used appointments within our legacy Outlook Plugin, and provided a way to migrate appointments ensuring a smooth transition and preventing data issues like duplicate appointments.

THIS RELEASE TeamConnect O365 Add-In 4.2: Introduces Task/To-Do integration and the ability to select the sub-features, Appointments, Documents, and Tasks on/off, and where applicable the migration of tasks from the Outlook Plugin to the new O365 Add-in 4.2. 

Disclaimer: Please avoid concurrent usage of the  Office Suite Plugin and Add-in.  It is vital users stop using and uninstall the Office Suite Plugin (for Outlook) after the datastore file has been uploaded and before the end users start using the Add-in. Concurrent usage will cause data issues such as duplicate tasks, deletion of data within tasks, etc.

Prerequisites

1. Each user must have an active Outlook 365 license.
2. For authentication purposes, users must have a valid TeamConnect account.
3. TeamConnect Enterprise version 7.2 or higher is required to install the TeamConnect O365 Add-In 4.2.
4. The new TeamConnect O365 Add-In 4.2 seamlessly integrates with both cloud-based and desktop versions of Outlook on Windows and Mac, ensuring accessibility for a wide range of users.

Note: The TeamConnect O365 Add-In is not supported on Outlook 2019 or earlier versions on the desktop.

5. Browser Compatibility: 

• Supported browsers include Google Chrome, Microsoft Edge, and Mozilla Firefox.
• Due to browser issues beyond our control, the Add-in only works with Safari 17.2.1 version and above. 

6. Server Requirements:

• Make sure your server meets the system requirements to install and integrate the TeamConnect O365 Add-In 4.2 into your setup smoothly. For additional guidance on system requirements and installing the TeamConnect O365 Add-In, refer to the Installation Guide.

Note: File check-In/check-Out is supported in the Outlook Add-In, rather than in Word, PowerPoint, and Excel. Users can efficiently manage files through Outlook Add-In or directly through TeamConnect for seamless file handling.

Configuring Microsoft Graph WebHook Notifications

1. The Add-in architecture requires Microsoft Graph's webhook notifications to connect to your TeamConnect instance. This means you need to open the port that TeamConnect uses in your firewall.
2. If you want to restrict access to specific IP addresses, you can whitelist the relevant IPs from Microsoft’s network. These IPs are listed in the Microsoft Graph Change Notifications section of Microsoft’s documentation.

Please refer to the flow chart below for a better understanding of the flow of requests.

Add-In Installation

1. Installation of TeamConnect O365 4.2 module via “Available Updates” in Admin Settings → About.
2. Installation Process in Microsoft 365 Admin Center:
   1. Install TeamConnect O365 Add-In 4.2 through the Microsoft 365 Admin Center. Please refer to the Installation Guide.
   2. To install on Windows desktops, ensure that Modern Authentication is enabled in the Microsoft 365 Admin Center under Settings. In the Microsoft 365 admin center, go to Settings > Org Settings > Modern Authentication. Select the checkbox to enable Modern Authentication.
3. Manifest File Provision:  

A manifest file is an XML-based configuration file used to define the structure, behavior, and permissions of an Office Add-in. It is essential for integrating an Add-in with Office 365, allowing it to interact with the host application and perform tasks within the Office environment. The manifest specifies critical details like the Add-in's capabilities, launch points, and user interface elements, making it a key component for deploying the Add-in.

To generate the manifest file required for TeamConnect O365 Add-In 4.2, use the TeamConnect application. For detailed instructions on installing the manifest file, please refer to the Installation Guide. 

Key enhancements include:

1. O365 Sub-Features Enable/Disable Options: Admins can select which objects (Appointments, Documents, Tasks) to enable in TeamConnect Admin Settings, based on your organization's needs for the O365 Add-in. 
2. Task Management Integration: Users can now view, create, edit, complete, and delete tasks directly from the Add-in, with bi-directional synchronization between TeamConnect and Microsoft To-Do. This ensures all tasks associated with a matter are efficiently tracked. 

Important Note: Task migration applies only to users who use tasks within the plugin.

Deployment Guidelines

• Instance switching, which allows seamless toggling between different Add-in versions (e.g., production and test), is typically restricted in O365 Add-ins, as Microsoft requires distinct manifest files for each environment to ensure better control and security. To enable instance switching or a similar feature, clients should deploy distinct manifests, especially for their test, development, and production environments. 
• Client IT Admins will manage Add-in deployment, applicable to both On-Premise and Hosted setups, as they have exclusive access to their respective Microsoft 365 Admin Centers. End users do not need to take any action during the installation process. After successful deployment through the Microsoft 365 Admin Center, the Add-in will be accessible on both Web and Desktop Outlook clients.
• Generate the manifest file required for TeamConnect O365 Add-In 4.2 using the TeamConnect application. Only an IT administrator who has access to the Microsoft 365 Admin Center can deploy the manifest file. 
• Outlook Add-in deployment requires Microsoft 365, and Exchange Online.

Add-In Deployment and Object Management

The manifest is generated after selecting the required objects, and once deployed, it determines what users can access. Follow the steps below to configure and manage the visibility of objects (Appointments, Documents, or Tasks) in the TeamConnect O365 Add-In. This ensures that users can only access the features you've enabled based on your organization's needs.

1. Navigate to Admin Settings in TeamConnect.
2. Open the Office Suite Admin Settings section.
3. In the admin settings, you'll see options for Appointments, Documents, and Tasks.
4. Check or uncheck the boxes to enable or disable these features as needed. This will determine which features will be accessible to users in the Add-in.
5. After selecting the desired features, click the Update button to save the changes.
6. Click the Generate Manifest button to deploy the changes. 
7. Once the manifest is deployed, the changes made in TeamConnect will now be applied in the Add-in. If Documents are disabled, the Add-in won’t load for emails; if Appointments or Tasks are disabled, it won’t load for the calendar.
8. Users will have access to only the features you enabled—Appointments, Documents, or Tasks—based on your settings.

Task Migration

If your organization is currently using tasks via the plugin, please refer to the Task Migration Admin Guide. Note that task migration is only applicable to users who manage tasks within the plugin.