> For the complete documentation index, see [llms.txt](https://documentation.grax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.grax.com/notices/release-notes/april-2026-release-notes.md).

# April 2026 Release Notes

## GRAX Release Notes — April 2026

***

### Storage

**Active/Passive Storage.** You can now configure a passive storage location alongside your primary storage. GRAX syncs your data from active to passive in the background, and the storage settings page shows sync progress as a percentage. AWS cross-region passive storage is supported. This is useful for disaster recovery, multi-region redundancy, and compliance requirements that need a second copy of your data in a separate location.

**Azure Storage via OAuth app registration.** GRAX can now connect to Azure Blob Storage using a multi-tenant OAuth app registration instead of a storage account key. Azure authentication method options are available in storage settings. This gives Azure customers more secure and manageable storage connections without sharing long-lived credentials.

**Improved S3-compatible storage support.** GRAX now handles checksum and authentication requirements correctly for S3-compatible storage providers beyond AWS — including Dell ECS and other custom endpoints. Customers running GRAX against non-AWS object storage will see more reliable connections.

***

### Search

**Search is faster and more accurate.** The search backend has been upgraded to V2. Reference-field searches now pass improved object context for better index usage. Filtering by Salesforce record ID now works correctly when AND is the default operator. 18-character Salesforce IDs are normalized for case-correct matching. The old V1 search endpoint has been retired.

**More precise search export field selection.** When you download search results, GRAX now exports exactly the fields you have selected at the time of download. Previously, the field list could reflect an earlier selection if you changed it before downloading. Search exports now represent your current field configuration.

***

### Restore

**Restore now includes embedded images in rich text fields.** Records with images embedded in rich text fields — case descriptions, knowledge articles, email bodies — now carry those images through restore and sandbox seeding. Previously, inline images were silently excluded from the restored output.

**Formula fields stay current after data operations.** Formula field refresh now runs across all objects following restore and other data operations, not just a subset. Formula values should reflect current underlying data more consistently across your org.

***

### Govern

**New Governance preview is available.** This uses existing salesforce settings for Sheild, Data Sensitivity, and Compliance Groups to create a new datalake that protects this data while making non-sensitve data available to more uses. It now shows a list of fields that are protected, along with the reason each field is protected. This is in preview by request.

***

### Backup

**Sandbox backup consistency improvements.** Sandbox environments now use snapshot pinning for backup and search, and sandbox backfill jobs run independently of production. This means sandbox and production backup schedules no longer interfere with each other, and the data visible in a sandbox reflects a consistent point in time.

***

### Security

**Audit activity logging.** GRAX now can log all audit events internally, including the source IP address of the request. This supports security review, compliance reporting, and investigation workflows for customers who need visibility into who accessed or changed what.

***

### Coming Soon

**Salesforce username/password login retires June 1, 2026.** GRAX is retiring support for connecting to Salesforce via username, password, and token credentials on June 1. If your GRAX instance still uses this connection method, you need to reconnect using OAuth before that date. You should have received an email with instructions. Contact support if you need help reconnecting.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.grax.com/notices/release-notes/april-2026-release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
