harmon.ie Classic and New: Admin Best Practices for Hybrid Use
Many organizations operate in a mixed environment where some users utilize harmon.ie Classic, and others have transitioned to New harmon.ie. Both versions are designed to work side-by-side. This article explains about the differences and how to configure the products appropriately to ensure a better experience for all users.
Deployment Differences: harmon.ie Classic vs. New
1. Comparison Table
Feature | harmon.ie Classic | New harmon.ie |
---|---|---|
Works in | Outlook for Windows (classic) |
|
How to get it | harmon.ie Customer Portal | Microsoft AppSource – New harmon.ie |
Configuration | Using registry keys. Read Centrally Configure harmon.ie Classic for All Users via Registry | Using a configuration file or the Admin settings tab. Read Centrally Configure New harmon.ie for All Users |
Central deployment | Using deployment tools such as Intune, SCCM, Altirix, or Active Directory. Read How to Deploy harmon.ie Classic | Deployed via the Microsoft 365 Admin Center. Read How to Deploy New harmon.ie |
Automatic updates | Not available. New releases should be manually deployed. Read How to Upgrade harmon.ie Classic to the Latest Version | Available |
2. App Consent
App consent is granted once for both products. Read Understanding harmon.ie App Consent and Required Permissions.
3. Sharing Sites & Favorites
To ensure a smooth transition, it’s recommended that harmon.ie Classic version 10.6 or later will be installed for all users switching to New harmon.ie. This version saves user’s sites and favorites in a common location accessible to New harmon.ie, reducing setup time.
4. Email File Formats and Versioning
The two products save emails in different formats:
- harmon.ie Classic saves emails as
.msg
files. - New harmon.ie saves emails as
.eml
files, offering better compatibility across platforms.
Both applications can open and read emails saved by the other. However, when the same email is saved using both products, SharePoint treats it as a new file due to the differing formats, potentially leading to duplicates.
5. Email Header Mapping and Email Views
harmon.ie’s email header mapping ensures that key information from your emails – like subject, sender, recipients, and sent date – is automatically extracted and saved as metadata when you save an email into SharePoint, Teams, or OneDrive.
Both products suggest two methods to configure email header mapping – automatic mapping, and custom mapping (with advanced features).
- If using automatic mapping in harmon.ie Classic, enabling automatic mapping in New harmon.ie ensures out-of-the-box functionality.
- If using custom mappings in Classic, apply the same configuration in New harmon.ie as explained in Configure Custom Email View and Email Header Mapping in New harmon.ie.
Email Views: If your existing Email views filter content to display only .msg files, it’s recommended to update them to filter content based on the Email content type.
Alternatively, update them to include .eml files as well as .msg, as this is the format used by New harmon.ie.
Feature Differences: Classic vs. New
New harmon.ie offers the core functionality of harmon.ie Classic, and we’re continuing to roll out additional features.
For a detailed comparison, refer to harmon.ie Classic vs. New harmon.ie: Key Differences and Features.
Read or share with your team: Getting Started with New harmon.ie (For harmon.ie Classic Users).