Telegram Archiver
di TeleMessage
Regular Telegram capturing all calls, chats, attachments and deleted messages in Microsoft 365
Use the TeleMessage connector in the Microsoft 365 compliance center to import and archive Telegram calls, chats, attachments, files, and deleted messages. 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 Telegram Archiver to mailboxes in Microsoft 365.
After Telegram data is stored in user mailboxes, you can apply Microsoft 365 compliance features such as Litigation Hold, Content Search, and Microsoft 365 retention policies to Telegram data. For example, you can search Telegram messages using Content Search or associate the mailbox that contains Telegram messages with a custodian in an Advanced eDiscovery case. Using a Telegram 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 to set up a Telegram Archiver connector. For more information, see Telegram Archiver.
Once every 24 hours, your organization’s Telegram data is copied to the TeleMessage site.
The Telegram connector that you create in the Microsoft 365 compliance center connects to the TeleMessage site every day and transfers Telegram data from the previous 24 hours to a secure Azure Storage location in the Microsoft Cloud. The connector also converts the content Telegram data to an email message format.
The connector imports Telegram data to the mailbox of a specific user. A new folder named Telegram 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 Telegram 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 Telegram 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. 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 Telegram item, the item won't be imported.
