AT&T Network Archiver
Integrated with the AT&T mobile network. Get a copy of employee SMS/MMS text messages in 365.
Use a TeleMessage connector in the Microsoft 365 compliance center to import and archive SMS and MMS data from AT&T Mobile Network. After you set up and configure a connector, it connects to your organization's AT&T Network once every day, and imports SMS and MMS data to mailboxes in Microsoft 365.
After SMS and MMS messages are stored in user mailboxes, you can apply Microsoft 365 compliance features such as Litigation Hold, Content Search, and Microsoft 365 retention policies to AT&T Network data. For example, you can search AT&T Network data using Content Search or associate the mailbox that contains the AT&T Network connector data with a custodian in an Advanced eDiscovery case. Using a AT&T Network connector to import and archive data in Microsoft 365 can help your organization stay compliant with government and regulatory policies.
Your organization works with TeleMessage and Verizon to set up a Verizon Network connector. For more information, see Verizon Network Archiver.
Once every 24 hours, SMS and MMS messages from your organization’s Verizon Network are copied to the TeleMessage site.
The Verizon Network connector that you create in the Microsoft 365 compliance center connects to the TeleMessage site every day and transfers the SMS and MMS messages from the previous 24 hours to a secure Azure Storage location in the Microsoft Cloud. The connector also converts the content of SMS and MMS messages to an email message format.
The connector imports the mobile communication items to the mailbox of a specific user. A new folder named Verizon SMS/MMS Network Archiver is created in the 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 and MMS message contains this property, which is populated with the email address of every participant of the message.
In addition to automatic user mapping using the value of the User’s Email address property, you can also implement 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 Verizon 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 will use the values in the email address property of the item it's trying to import.