Set up a connector to archive O2 Network data

Use a TeleMessage connector to import and archive Short Messaging Service (SMS) messages and voice calls from the O2 mobile network. After you set up and configure a connector, it connects to your organization's O2 Network once every day, and imports SMS and voice calls to mailboxes in Microsoft 365.

After you store SMS messages and voice calls in user mailboxes, you can apply Microsoft Purview features such as Litigation Hold, Content Search, and Microsoft 365 retention policies to O2 Network data. For example, you can search O2 Network SMS messages and voice calls by using Content Search or associate the mailbox that contains O2 Network data with a custodian in an eDiscovery (Premium) case. Using an O2 Network connector to import and archive data in Microsoft 365 can help your organization stay compliant with government and regulatory policies.

Overview of archiving O2 Network data

The following overview explains the process of using a connector to archive O2 Network data in Microsoft 365.

1. Your organization works with TeleMessage and O2 to set up an O2 Network connector. For more information, see O2 Network Archiver.

2. Once every 24 hours, the TeleMessage site copies SMS messages and voice calls from your organization’s O2 Network.

3. The O2 Network connector that you create in the Microsoft Purview portal connects to the TeleMessage site every day and transfers the SMS messages and voice calls from the previous 24 hours to a secure Azure Storage location in the Microsoft cloud. The connector also converts the content of SMS messages and voice calls to an email message format.

4. The connector imports the mobile communication items to the mailbox of specific users. A new folder named O2 SMS and Voice Network Archiver is created in a specific user's mailbox and the items are imported to it. The connector does this mapping by using the value of the User’s Email address property. Every SMS message and voice call contains this property, which is populated with the email address of every participant of the message.

   In addition to automatic user mapping by using the value of the User’s Email address property, you can also define a custom mapping by uploading a CSV mapping file. This mapping file contains the mobile phone number and corresponding Microsoft 365 email address for users in your organization. If you enable both automatic user mapping and custom mapping, for every O2 item the connector first looks at custom mapping file. If it doesn't find a valid Microsoft 365 user that corresponds to a user's mobile phone number, the connector uses the values in the email address property of the item it's trying to import. If the connector doesn't find a valid Microsoft 365 user in either the custom mapping file or in the email address property of the O2 item, the item won't be imported.

Before you set up a connector

Some of the implementation steps required to archive O2 Network data are external to Microsoft 365. You must complete these steps before you can create a connector in the compliance center.

• Order the O2 Network Archiver service from TeleMessage and get a valid administration account for your organization. You need to sign in to this account when you create the connector in the compliance center.

• Get your O2 Network account and billing contact details so you can fill out the TeleMessage onboarding forms and order the message archiving service from O2.

• Register all users that require O2 SMS and Voice Network archiving in the TeleMessage account. When registering users, be sure to use the same email address that's used for their Microsoft 365 account.

• Ensure your employees have corporate-owned and corporate-liable mobile phones on the O2 mobile network. Archiving messages in Microsoft 365 isn't available for employee-owned or "Bring Your Own Devices (BYOD) devices.

• Assign the Data Connector Admin role to the user who creates an O2 Network connector. This role is required to add connectors on the Data connectors page in the Microsoft Purview portal. Microsoft adds this role by default to multiple role groups. For a list of these role groups, see Roles in Microsoft Defender for Office 365 and Microsoft Purview compliance. Alternatively, an admin in your organization can create a custom role group, assign the Data Connector Admin role, and then add the appropriate users as members. For instructions, see:

  • Permissions in the Microsoft Purview portal
  • Roles and role groups in Microsoft Defender for Office 365 and Microsoft Purview compliance

• Use this TeleMessage data connector in GCC environments in the Microsoft 365 US Government cloud. Third-party applications and services might involve storing, transmitting, and processing your organization's customer data on third-party systems that are outside of the Microsoft 365 infrastructure. Therefore, these systems aren't covered by the Microsoft Purview and data protection commitments. Microsoft makes no representation that use of this product to connect to third-party applications implies that those third-party applications are FEDRAMP compliant.

Create an O2 Network connector

After you complete the prerequisites described in the previous section, you can create an O2 Network connector in the Microsoft Purview portal. The connector uses the information you provide to connect to the TeleMessage site and transfer SMS messages and voice calls to the corresponding user mailboxes in Microsoft 365.

1. Sign in to the Microsoft Purview portal.

2. Select Settings > Data connectors.

3. Select My connectors, then select Add connector.

4. Choose O2 Network from the list.

5. On the Terms of service page, select Accept.

6. On the Login to TeleMessage page, under Step 3, enter the required information in the following boxes and then select Next.

   • Username: Your TeleMessage username.
   • Password: Your TeleMessage password.

7. After the connector is created, you can close the pop-up window and go to the next page.

8. On the User mapping page, enable automatic user mapping and select Next. If you need custom mapping, upload a CSV file, and select Next.

9. Review your settings, and then select Finish to create the connector.

Limits

Importing attachments or items supports up to 10 MB.