Riva On-Premise 2026.2 Release Notes

Medha Gupta (Agent)
Medha Gupta (Agent)
  • Updated
Release Version: 2026.2.xx
Release Date: 2026.May.18
Update Procedure: How to update Riva
Manual Update Procedure: How to update Riva from a ZIP file
Interested? Schedule a consult

 

New! 

Dynamic Per-User Sync Module Control via Salesforce

Riva now supports per-user sync module overrides driven directly from a Salesforce User custom field. This enables administrators to manage which modules run for individual users without creating and maintaining multiple policies, reducing administrative overhead and helping prevent Sync Configuration conflicts that can occur when users are moved between policies.

If you’re interested in trying this feature, please reach out to Riva Technical Support Team.
 

Support for Phone Calls and Service Appointments with Microsoft Graph

Riva now supports synchronization of Phone Calls and Service Appointments when using the Microsoft Graph connector.

  • Expanded Object Support: Appointments categorized as Phone Calls or Service Appointments in Outlook can now sync with corresponding CRM records.
  • Bi-Directional Sync: Changes made in either system are reflected across both Exchange and CRM.
  • Improved CRM Alignment: Enhances support for Microsoft Dynamics CRM scenarios where these activity types are commonly used.

Enhancements

Enhancement Suite for Microsoft Graph Connector (2026.2)

Riva continues to expand its Microsoft Graph integration with new capabilities, performance improvements, and enhanced configuration support to ensure feature parity with Exchange Web Services (EWS) and improved synchronization reliability.

  • 18214 Attachment Removal Support: Administrators can now remove attachments during synchronization using existing configuration controls, ensuring consistency between CRM and email systems.
  • 18837 HTML to RTF Body Conversion: Added support for body format conversion to maintain compatibility with existing configurations during Graph migrations.
  • 18210 Address Resolution Caching: Improves calendar sync performance by reducing redundant address resolution calls, especially for large and recurring meetings.
  • 19653 Optimized Change Notification Processing: Reduces API calls by batching Graph change notifications, improving performance and scalability.
  • 17774 Enhanced Directive & Customization Support: Improves compatibility for existing CRM and Exchange directives when migrating to Graph.
  • 20420 Microsoft Graph Delta Query API Alignment: Riva updated its use of Microsoft Graph delta queries to align with the v1.0 API. This change improves consistency and reliability of incremental synchronization.

Platform Modernization and Architecture Improvements

Riva continued investing in platform modernization and internal architecture improvements to enhance performance, scalability, and long-term maintainability.

  • 19674 Improved System Maintainability: Refactored core components to remove redundant logic, improve code quality, and increase test coverage—resulting in more stable and reliable processing.
  • 19885 .NET 8 Enablement: Advanced the transition to a modern runtime framework, enabling improved performance, security, and future scalability across Sync components.
  • 18153 Standardized Dependency Management: Streamlined how shared components are managed across the platform, reducing system complexity and improving consistency across services.

 

Bug Fixes

  1. 19181 Policies and connections alphabetical sorting: Riva resolved an issue where policies and connections were not displayed in alphabetical order in the Riva On-Premise application. Policies and connections are now displayed in alphabetical order by name.

  2. 19440 & 19334 to Email System Event Sync Reliability (Microsoft Graph):
    Riva resolved an issue where updates and deletions to Events created in Salesforce were not consistently syncing to the email system. This fix ensures that changes to CRM-originated Events are reliably reflected in the connected mailbox. A new configuration key Sync.Ex.PrivateDefault.AllowUpdateCrmOriginatingItem has been introduced (default: false), and the deprecated key Crm.Calendar.SupportsPrivateFlagOverride should be removed.

  3. 19042 Microsoft Graph Configuration Reset During On-Premise Installation:
    Riva fixed an issue where installing or upgrading the on-premise package could overwrite existing Microsoft Graph configuration settings. Existing configurations are now preserved during installation and upgrades.

  4. 18041 Duplicate Sync Activity Logs:
    Riva resolved an issue in the Riva Admin Center – Activity Monitoring feature where duplicate performance and activity log entries were generated for individual sync cycles. This fix improves the accuracy and reliability of monitoring and reporting data.

  5. 19513 Inconsistent Logging Behavior Across Environments:
    Riva resolved an issue where logging output could be incomplete or inconsistent across environments due to initialization timing. Logging is now reliably captured, improving troubleshooting and diagnostics.

  6. 18347 Unnecessary OAuth Token Refresh for EWS Client Credential Connections:
    Riva fixed an issue where OAuth token refresh processes were incorrectly triggered for certificate-based (client credential) EWS connections. This change reduces unnecessary background processing and improves overall efficiency.

  7. 19107 Microsoft Graph Migration Sync Initialization Failure:
    Riva resolved an issue where sync could fail to initialize after migrating to the Microsoft Graph connector, preventing users from completing sync cycles. This fix ensures successful sync startup following migration.

  8. 19336 Appointment Synchronization Issues Between Exchange and CRM (Microsoft Graph):
    Riva resolved an issue where appointments were not consistently syncing between Exchange and CRM. This fix improves bidirectional synchronization reliability for calendar items and updates.

  9. 19815 Graph Connection Licensing Not Applied After License Update:
    Riva fixed an issue where updated license files did not correctly apply to Microsoft Graph connections, causing users to appear unlicensed and preventing synchronization. Graph users are now properly recognized after license updates.

  10. 19282 Salesforce Email-to-Task Field Mapping Not Applied Consistently:
    Riva resolved an issue where email field mappings to related Tasks in Salesforce were only applied under certain conditions. Field mappings are now consistently applied regardless of email content.

  11. 20337 Connection Testing Issues with Microsoft Graph in Riva Cloud:
    Riva resolved an issue where connection tests could fail when validating Microsoft Graph connections due to incorrect service routing. Connection testing now completes reliably during configuration.

 

Announcement

Outlook “New Contacts” and category requirements (OWA + new Outlook for Windows)

Outlook on the web (new People experience) and the new Outlook for Windows save newly created contacts into the Default Contacts folder by default.

Riva Sync compatibility

  • When users create contacts using New Contacts and use the Default Address Book, Riva Sync correctly syncs new contacts, including when Categories are required.

  • Note: In OWA Old Contacts view, contacts created in the Default Address Book may not sync when Categories are required. In this mode, syncing works only when Sync all new is enabled and category requirements are not enforced.

Recommended usage

  • For New Contacts, use the Default Address Book and organize contacts using Categories.

  • If using the OWA Old Contacts view, avoid mixing the Default Address Book’s New Contacts behavior with folder-based workflows; requiring categories may prevent syncing.