Custom mapping mobile archiving users into Microsoft 365 users

Companies that require a special user mapping where the emails of your employees in Microsoft 365 are not the main mapping field, can use the mobile archiver connector custom field mapping 

• The default mapping is based on the TeleMessage email address of the employee matching the Microsoft 365 email address of the employee (Tenant’s email).
• When there is no custom mapping the User’s Email (User.Email) must match one of the tenant’s emails, which will allow the mobile message to get pushed to the proper employee mailbox.
• Custom mapping is a way to map different fields between the TeleMessage User.Id and the Tenant’s mailbox for archiving.
• When the custom mapping is turned ON the User.UserID field is being mapped to the tenant’s email address. It will override the default delivery to the User.Email inbox.
• Custom mapping is always done from User.UserID to Tenant’s Active Directory email. In such case, TeleMessage must register the users by login name = mobile number.
• A Tenant will need custom mapping only in case some users do not have an email address filled, meaning there is no value to populate in User.Email.
  On some occasions, TeleMessage supports registering archive users without populating an email address (that will map to Active Directory emails).
  If this is the case in your firm, you are advised to use custom mapping to map every single mobile number to the relevant Active Directory address.
  
• CSV format

• Example: Microsoft 365 User Mailbox – must be email

• Sample User Mapping File