---
title: "Xray Cloud 4.7.0 Release Notes"
canonical: "https://docs.getxray.app/space/XRAYCLOUD/44579700/Xray%20Cloud%204.7.0%20Release%20Notes"
format: markdown
---
**May 19th, 2024 **


The Xray team is proud to announce the release of **Xray Cloud v**<span style="color: #172b4d">**1.1.98-AC**</span>** -4.007.000**  
  
We're thrilled to introduce our newest functionality, ...   


> Macro (toc)

# Release Highlights

We are excited to announce a new release of Xray, which introduces comprehensive support for data residency.   
This release ensures that your sensitive data complies with regional regulations and organizational policies by allowing you to specify the geographic location where your data is stored and processed. Here are the key features and improvements included in this release:

- Data Residency Configuration (Figure 1):  
Data Location Selection: Administrators can now select specific geographic regions for data storage and processing, ensuring compliance with local data sovereignty laws.
- Performance Enhancements:  
Optimized data processing and retrieval speeds for region-specific operations.  
Reduced latency for users by routing requests to the nearest data center.

![Figure 1 - Data residency](media://1dd1370f-c137-4c1b-9e22-4b454791f47d)

Learn more [here](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565771).


> ⚠️ **Important: Update Required for Xray URL Changes**
> ⚠️ 
> ⚠️ Due to data residency options, the URLs for accessing Xray have changed (Internal API's).   
> ⚠️ If your organization filters internet traffic, please update your firewall rules to allow the appropriate URLs based on your selected data residency location. 
> ⚠️ 
> ⚠️ - US - [https://us.xray.cloud.getxray.app](https://us.xray.cloud.getxray.app)
> ⚠️ - EU - [https://eu.xray.cloud.getxray.app](https://eu.xray.cloud.getxray.app)
> ⚠️ - AU - [https://au.xray.cloud.getxray.app](https://au.xray.cloud.getxray.app)
> ⚠️ 
> ⚠️ By default, the US endpoint ([https://us.xray.cloud.getxray.app](https://us.xray.cloud.getxray.app)) will be used for current instances.
> ⚠️ 
> ⚠️ 
> ⚠️ **Note**: All the requests to Xray GraphQL API are now required to be POST requests, instead of GET requests. Please refer to the following image (Figure 2) for your reference.
> ⚠️ 
> ⚠️ ![image](media://bb5c98ea-8fcf-4d33-8dc0-92f9586418c1)


# Just one last, yet <u>important</u>, thing...

Documentation is always important, and sometimes you may miss it.

We included a new tutorial to show how to migrate from other Test management tools, to foster adoption of Xray in your teams.

Here's a summary of all the relevant articles that we've added and updated recently:

- **Tutorials, Tips, and Tricks**
  - **[TTT - Automation](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566207)**
    - [Testing Rust applications](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Testing+Rust+applications)
  - **[TTT - Migration](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565782)**
    - [Tips for a successful migration path from Azure DevOps to Xray](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/Tips+for+a+successful+migration+path+from+Azure+DevOps+to+Xray)