> 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-02-releasenotes.md). # February 2025 ## Key Takeaways * **Updated Bandwidth Methodology** - Only end-user traffic is counted, reducing reported usage and encouraging caching. * **Custom Identity Provider** - Configure your own login provider directly in Umbraco Cloud and use it to sign into your project. ## Updated Bandwidth Methodology Measuring bandwidth usage in Umbraco Cloud has been updated to better reflect how other services calculate it.\ As of February 1st, 2025, only traffic between the end user and Umbraco Cloud is counted — internal traffic is no longer included. This change means bandwidth stats now give a more accurate picture of real-world usage. Bandwidth usage may now show around 50–100% of what you saw before, depending on your setup. ## Custom Identity Provider You can now connect your Active Directory to Umbraco CMS using OpenID Connect.\ This utilizes external login provider support in the CMS, configurable directly through the Umbraco Cloud portal—no coding required. A secure and convenient way to manage user access with your existing identity setup. It is useful for teams already using centralized authentication. --- # 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-02-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.