> 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-2024/2024-11-releasenotes.md).

# November 2024

## Key Takeaways

* **Umbraco 15** - Umbraco 15 and .NET 9 are now available on Umbraco Cloud.
* **Web Application Firewall now available** - This feature is enabled by default in new environments. Existing projects can enable it through the portal.

## Umbraco 15

You can now start new projects on Umbraco 15 or upgrade your existing projects to take advantage of the latest features and improvements.

Support for .NET 9 is now available on Umbraco Cloud, simplifying the process of staying current with the latest Microsoft tech stack.

## Web Application Firewall now available

Web Application Firewall (WAF) is now enabled by default for all new environments on Umbraco Cloud.\
It protects your project from common threats like SQL injections, JavaScript exploits, and known vulnerabilities, utilizing Cloudflare’s managed ruleset.

For existing projects, WAF can be enabled through the Umbraco Cloud Portal. It is recommended to enable it on existing projects for added protection.


---

# 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-2024/2024-11-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.