> 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-03-releasenotes.md). # March 2025 ## Key Takeaways * **A Refreshed Sign-In Experience** - Updated sign-in page with a new look and feel that matches the Umbraco identity. * **Smoother Experience on Usage page** - Improved performance on usage pages for a faster and smoother experience. ## A Refreshed Sign-In Experience The Umbraco ID sign-in page has received a visual facelift to better reflect the identity and style you know from Umbraco. The updated look offers a more familiar and welcoming experience for signing in to your projects or the Umbraco Portal while maintaining the same functionality. ## Smoother Experience on Usage page Some under-the-hood performance improvements have been made that result in a faster and smoother experience when viewing usage data on your projects. The pages now load quickly, so you can get the insights you need with less waiting. --- # 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-03-releasenotes.md?ask=&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.