FOIAXpress TeleMessage Integration Configuration

Prev Next
  1. About TeleMessage Integration

Users must configure their application settings prior to integrating FOIAXpress with TeleMessage. This manual outlines the requirements and steps for configuring FOIAXpress for TeleMessage integration.

  1. TeleMessage Integration Prerequisites

Complete the following steps to ensure your FOIAXpress application is ready to be configured for TeleMessage integration. Once these prerequisites are met, you can set configurations within the application to enable the TeleMessage integration.

2.1 Upgrade FOIAXpress

If you are not on FOIAXpress version 11.5.0 or higher, upgrade the application first. Follow the steps in the FOIAXpress Deployment Manual to upgrade your application.

2.2 Set Up MMA in Azure

Follow the steps below to set up a Mobile Message Archive in Azure:

  1. Select Enterprise application

  1. Click + New application to create a new application

  1. Select + Create your own application:

A white background with black text  Description automatically generated

  1. Provide a name and select the Register an application to integrate with Microsoft Entra ID option (selected in the following example):

  1. Under Supported Account Types, select the Accounts in this organizational directory only (Single Tenant) option:

  1. Create the application.

  2. After creating the application, click on Properties:

  1. Click on Additional Properties:

  1. Select Overview:

  1. Record the Client ID and the Tenant ID (these are required during TeleMessage Integration Configuration):

  1. Go to API Permissions:

  1. Click Add a permission:

  1. Search for and select Microsoft Graph:

  1. Select Application permissions:

  1. Under Mail, add the Mail.Read, and Mail.ReadBasic.All permissions:

  1. Under User, select the User.Read.All and User.ReadBasic.All permissions as shown below:

  1. Click on Grant admin consent for your account:

  1. Click on Certificates & secrets:

  1. Click + New client secret to create a new secret:

  1. Add a Description and set an Expires duration:

  1. Copy the Value and store it securely.

With the information gathered from this list, go to the FOIA Application and provide the saved values.

2.3 Upgrade Application License

  1. Upgrade the application license in the Administration settings.

NOTE: The TeleMessage feature is tied to your application license, and the feature is automatically enabled with the appropriate license. Please upgrade your license to include the TeleMessage integration.

  1. Ensure that the TeleMessage integration is enabled in the Application Features menu (Administration > Features and Licenses > Application Features). It should be enabled automatically after upgrading your license. If not enabled after upgrading your license, select the TeleMessage Integration checkbox and save the configuration:

  2. 3. The TeleMessage Integration Configuration menu should be visible when accessing Administration > System Administration. If the menu is not visible, log out of the application and log back in.

3 TeleMessage Integration Configuration

Follow the steps below to configure the TeleMessage integration:

  1. Navigate to the TeleMessage Integration Configuration menu (Administration > System Configuration > TeleMessage Integration Configuration):

  1. The TeleMessage Integration Configuration screen appears as shown below. Use these fields to configure the integration. They are described in the following table.

NOTE: Please consult with casepoint support to obtain the correct values for these fields, based on your specific environment and integration.

Field

Description

Client Id

The Client Id (or Application ID) represents the application's identity in the directory. When the application interacts with Azure services or APIs, it presents this ID as part of the authentication process to prove its identity.

This value is recorded at step 10 of section 2.2, Set Up MMA in Azure.

Secret Key Value

A credential, often a string value, is generated for an application to authenticate itself against Azure services. This key is paired with the Client ID to authenticate the application. It's like a password and is used as part of the authentication flow to ensure that only the application with the correct credentials can access protected resources.

This value is recorded at step 21 of section 2.2, Set Up MMA in Azure.

Email

Represents a Microsoft Entra user account used for this integration.

Tenant Id

The identifier of the Azure AD tenant where the application and its related resources (like users, groups, and applications) are registered. Azure AD tenants are unique environments created by organizations to manage and secure access to their resources. The Tenant Id is used to specify which Azure AD tenant the application is associated with.

This value is recorded at step 10 of section 2.2, Set Up MMA in Azure.

MailBox

The location where your emails, contacts, calendar events, tasks, and other personal information are stored.

  1. After configuring these fields, click Save to save the settings.

  2. Once your integration is configured, your users will be able to search the TeleMessage Mobile Message Archive using the Add Documents drop-down and selecting Mobile Message Archive.