Riva Cloud 2026.2 Release Notes

Tristan Coyle
Tristan Coyle
  • Updated
Release Candidate Rollout (z-pods) Pre-Release Rollout (y-pods) Production Rollout 
Starts 		Production Rollout 
Ends 		Interested?
April 21, 2026 May 05, 2026 May 20, 2026 May 24, 2026 Schedule a Consult

Deployment details can be found here.

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 Modern Microsoft Exchange Connector (Graph)

Riva now supports synchronization of Phone Calls and Service Appointments when using the Microsoft Modern Exchange Connector (Graph).

  • 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 the Modern Microsoft Exchange Connector (Graph) (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.

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

Security Updates

We have implemented several enhancements to strengthen the security of Riva Cloud in the 2026.2 release:

  1. Proxy Disclosure (19369)
    As part of this update, we improved how our infrastructure handles certain HTTP methods and server responses. These changes reduce the amount of system-level information that could potentially be exposed externally and further harden our environment against reconnaissance-based attacks.

  2. Stricter SNI validation during TLS handshake (20033)
    We have enhanced our TLS (Transport Layer Security) handling to enforce stricter validation of Server Name Indication (SNI) during the connection process. This update ensures that only properly formed connection requests are accepted, aligning our platform with current security best practices.

Bug Fixes

Several bug fixes have also been included in the 2026.2 release for Riva Cloud:
 

  1. Salesforce to Email System Event Sync Reliability (Microsoft Graph) (19334, 19440)
    We 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.
     
  2. Unnecessary OAuth Token Refresh for EWS Client Credential Connections (18347)
    We 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.
     
  3. Microsoft Graph Migration Sync Initialization Failure (19107)
    We 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 a successful sync startup following migration.
     
  4. Appointment Synchronization Issues Between Exchange and CRM (Microsoft Graph) (19336)
    We resolved an issue where appointments were not consistently syncing between Exchange and CRM. This fix improves the reliability of bidirectional synchronization for calendar items and updates.
     
  5. Graph Connection Licensing Not Applied After License Update (19815)
    We 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.
     

  6. Salesforce Email-to-Task Field Mapping Not Applied Consistently (19282)
    We resolved an issue in which email field mappings to related Tasks in Salesforce were applied only under certain conditions. Field mappings are now consistently applied regardless of email content.
     

  7. Connection Testing Issues with Microsoft Graph in Riva Cloud (20337)
    We resolved an issue in which connection tests could fail during Microsoft Graph connection validation due to incorrect service routing. Connection testing now completes reliably during configuration.
     

  8. Dynamics + Microsoft Graph Support (20474)
    We resolved an issue in which the default policy for a Dynamics + Microsoft Graph connection was unavailable. This caused an issue in which customers were unable to create a new sync policy when Dynamics and Graph were their selected connections.
     
  9. Null Reference Exceptions (15445)
    We resolved several specific application errors affecting the audit viewer, policy updates, and user functionality, enhancing overall system stability and ensuring our applications work as expected.

Announcements

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 the Default Address Book, Riva Sync correctly syncs them, 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 behaviour with folder-based workflows; requiring categories may prevent syncing.

Deployment Details 

Riva Cloud Sync and Web (rivacloud.com) are scheduled to be upgraded to 2026.2 between May 18, 2026 and May 22, 2026. To ensure a smooth transition, we are providing the following schedule:

Riva Cloud Sync Release

  • Release Candidate Channel Upgrade (z-pods): April 21, 2026, after regular business hours
  • Pre-Release Channel Upgrade (y-pods): May 05, 2026, after regular business hours
  • Release Channel Upgrade (x & main pods): May 18-20, 2026, after regular business hours.
    • May 18 (Sync)
      • au1x
      • eu1x
      • na4x
      • na5x
      • na6x
      • na8x
      • na10x
      • edupx
    • May 19 (Sync)
      • au1
      • na4
      • na5
      • na6
      • edup
    • May 20 (Sync)
      • eu1
      • ca1
      • na8
      • na10

Riva Cloud Web (rivacloud.com) Release

  • Pre-Release Channel Upgrade: May 06, 2026, after regular business hours
  • Release Channel Upgrade: May 21-22, 2026, after regular business hours.
    • May 21 (rivacloud.com)
      • Australia
      • Canada
    • May 22 (rivacloud.com)
      • Europe
      • United States

Note that you can determine which pod and data residency your account resides on by logging into your Riva Cloud account, navigating to “Manage Account” and selecting “Account Summary”. In the top right, under the header Data Residency Region /Configuration Pod.

Testing Period

You will have approximately three (3) weeks to test this release on the pre-release channels before it is rolled out to the release channels. 

Next Steps

  • Testing: Conduct thorough testing in your lower environment after the May 05 upgrade. If you are unsure if you have a lower environment on the pre-release channel, please contact the Technical Support team here.

Potential Impacts

The upgrade will be completed after regular business hours. During the upgrade, there could be a short window of service disruption (10-20 minutes).

Support
For any questions or concerns, please contact the Technical Support team here.