> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cloud/release-notes/archive/overview-2025/2025-04-releasenotes.md).

# April 2025

## Key Takeaways

* **Flexible Environment for Umbraco Cloud** - Flexible Environment is now in open beta on Umbraco Cloud. You can start working on larger features in isolation, which is available for Standard and Professional plans.
* **Canada Region Available** - Umbraco Cloud now has a Canada region.

## Flexible Environment for Umbraco Cloud (Open Beta)

To work on larger features and continue to push your code and content through the regular flow of environments, Flexible Environment is introduced for your project. It is now available as an open beta on Standard and Professional plans.

The Flexible Environment is a vertical environment connected to your development environment.\
It allows you to pull code and content from the development environment and work in isolation on larger features.

## Canada Region Available

Umbraco Cloud now has a Canada region, allowing you to host your projects in Canada.\
This is particularly beneficial for organizations with data residency requirements or those looking to enhance performance for users in Canada.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-cloud/release-notes/archive/overview-2025/2025-04-releasenotes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.