Set up a connector to archive Android mobile data
Microsoft 365 compliance is now called Microsoft Purview and the solutions within the compliance area have been rebranded. For more information about Microsoft Purview, see the blog announcement and the What is Microsoft Purview? article.
Use a TeleMessage connector in the Microsoft Purview compliance portal to import and archive SMS, MMS, voice calls, and call logs from Android mobile phones. After you set up and configure a connector, it connects to your organization's TeleMessage account once every day, and imports the mobile communication of employees using the TeleMessage Android Archiver to mailboxes in Microsoft 365.
After data from Android mobile phones is stored in user mailboxes, you can apply Microsoft Purview features such as Litigation Hold, Content Search, and Microsoft 365 retention policies to Android Archiver data. For example, you can search Android Archiver mobile communication using Content Search or associate the mailbox that contains the Android Archiver connector data with a custodian in an eDiscovery (Premium) case. Using an Android Archiver connector to import and archive data in Microsoft 365 can help your organization stay compliant with government and regulatory policies.
Overview of archiving Android mobile data
The following overview explains the process of using a connector to archive Android mobile data in Microsoft 365.
Your organization works with TeleMessage to set up an Android Archiver connector. For more information, see Android Archiver.
In real time, SMS, MMS, voice calls, and call logs from your organization's Android mobile phones are copied to the TeleMessage site.
The Android Archiver connector that you create in the compliance portal connects to the TeleMessage site every day and transfers the Android data from the previous 24 hours to a secure Azure Storage location in the Microsoft cloud. The connector also converts the Android data to an email message format.
The connector imports the mobile communication items to the mailbox of a specific user. A new folder named Android Archiver is created in the specific user's mailbox and the items are imported to it. The connector does mapping by using the value of the User's Email address property. Every email message contains this property, which is populated with the email address of every participant of the email message. In addition to automatic user mapping 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 should contain the mobile number and corresponding Microsoft 365 mailbox address for each user. If you enable automatic user mapping and provide a custom mapping, for every email item the connector will first look at custom mapping file. If it doesn't find a valid Microsoft 365 user that corresponds to a user's mobile number, the connector will use the user's email address property of the email item. If the connector doesn't find a valid Microsoft 365 user in either the custom mapping file or the User's email address property of the email item, the item won't be imported.
Before you set up a connector
Some of the implementation steps required to archive Android communication data are external to Microsoft 365 and must be completed before you can create the connector in the compliance center.
Order the Android Archiver service from TeleMessage and get a valid administration account for your organization. You'll need to sign into this account when you create the connector.
Register all users that require the Android Archiver service in the TeleMessage account. When registering users, be sure to use the same email address that's used for their Microsoft 365 account.
Install and activate the TeleMessage Android Archiver app on the mobile phones of your employees.
The user who creates a Android Archiver connector must be assigned the Data Connector Admin role. This role is required to add connectors on the Data connectors page in the compliance portal. This role is added by default to multiple role groups. For a list of these role groups, see the "Roles in the security and compliance centers" section in Permissions in the Security & Compliance Center. 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 the "Create a custom role group" section in Permissions in the Microsoft Purview compliance portal.
This TeleMessage data connector is available 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 and therefore are not 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 Android Archiver connector
The last step is to create an Android Archiver connector in the compliance portal. The connector uses the information you provide to connect to the TeleMessage site and transfer Android communication to the corresponding user mailbox boxes in Microsoft 365.
Go to https://compliance.microsoft.com and click Data connectors > Android Archiver.
On the Android Archiver product description page, click Add connector.
On the Terms of service page, click Accept.
On the Login to TeleMessage page, under Step 3, enter the required information in the following boxes and then click Next.
Username: Your TeleMessage username.
Password: Your TeleMessage password.
After the connector is created, close the pop-up window and click Next.
On the User mapping page, enable automatic user mapping and click Next. In case you need custom mapping upload a CSV file, and click Next.
Review your settings, and then click Finish to create the connector.
Go to the Connectors tab in Data connectors page to see the progress of the import process for the new connector.
- At this time, we don't support importing attachments or items that are larger than 10 MB. Support for larger items will be available at a later date.
Submit and view feedback for