> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/help-and-support/release-notes.md). # Release notes This page includes the latest enhancements, fixes, and new features in SoftwareOne’s FinOps for Cloud. ## Release Date: 15 September 2026 ### Date range filtering and report export in Pools The **Pools** feature now supports date-based filtering and report exports to help you analyze and share pool data. When filtering data, you can now select a custom date range or use the following predefined ranges: * This month * Last month * Last 7 days * Last 30 days Additionally, you can download the pool breakdown and allocation data in CSV or XLSX format using the **Download report** option on the **Pools** page. For more information, see [Pools](/insights/pools.md). ### Data source entitlement status The **Data sources** page now includes a new **Entitled** column for connected AWS accounts and Azure subscriptions. The **Entitled** column indicates whether the AWS account or Azure subscription is associated with a SoftwareOne service entitlement. When an entitlement exists, the associated entitlement ID is also displayed. For more information, see [Add data sources](/finops-for-cloud/getting-started/data-sources.md). ### Interface language selection FinOps for Cloud now includes a **language selector** in the top navigation header, allowing you to choose your preferred display language. The selected language is applied to navigation menus and elements, such as labels, buttons, and other on-screen text. For more information, see [Navigate the user interface](/finops-for-cloud/getting-started/overview.md). ### Organization lifecycle statuses To provide clarity on the organization's availability and data processing, the organization lifecycle statuses are now standardized as follows: * **Active** – The organization is operational and actively processing data. * **Terminated** – The organization is no longer operational, but its data remains available for historical reporting. Terminated organizations don't process any new data. * **Deleted** – The organization has been removed. Deleted organizations are not visible in FinOps for Cloud, but their data is retained in the system. All data is managed in accordance with the billing and compliance retention requirements. Organization statuses are displayed beside the organization name in the header and on the **Organizations overview** page. For more information, see [Navigate the user interface](/finops-for-cloud/getting-started/overview.md). ### AWS Assumed Role authentication with optional External ID To enhance security and align with AWS best practices, FinOps for Cloud now supports an optional **External ID** when configuring AWS data sources that use **Assumed Role** authentication. To support this capability, an **External ID** field has been added to the AWS data source configuration page. Use the **Generate** option to create a unique external ID for your AWS data source. If you choose to use an **External ID**, you must add the generated value to the `Condition` block of your AWS IAM role trust policy using `sts:ExternalId`. For more information about configuring AWS accounts, see [Add your AWS account to FinOps for Cloud](/system/data-sources/amazon-web-services/add-your-aws-account-to-finops-for-cloud.md) and [Create a new IAM role](/system/data-sources/amazon-web-services/configure-aws-access.md#create-a-new-iam-role). *** ## Release Date: 3 February 2026 ### Switch AWS data source from access key to assumed role FinOps for Cloud now supports seamlessly updating an AWS data source from using an access key to an assumed role. SoftwareOne and AWS strongly recommend using an assumed role. {% hint style="warning" %} Switching from an access key to an assumed role is permanent. After you make this change, you can’t switch back to using an access key for this data source. For more information, see [Switch from Access Key to Assumed Role](/system/data-sources/amazon-web-services/switch-from-access-key-to-assumed-role.md). {% endhint %} ### Automatic configuration of AWS data sources discontinued To strengthen our alignment with a read‑only operating model and least‑privilege security practices, FinOps for Cloud no longer supports automatically creating AWS Cost and Usage Reports (CUR) or provisioning their associated S3 buckets. Administrative users must now create and configure CUR exports and S3 buckets directly in AWS before connecting them to FinOps for Cloud. FinOps for Cloud continues to support connecting to existing customer‑managed CUR exports without requiring elevated permissions. *** ## Release Date: 12 December 2025 ### Download Recommendations You can now download insights directly from recommendation tiles, making it easier to export and share optimization suggestions. ### Fixes * Removed all usages of the deprecated ADAL authentication library and upgraded all Microsoft authentication to MSAL. This is Microsoft's recommended library for all new development. For more details, see [Microsoft Learn](https://learn.microsoft.com/en-us/entra/identity-platform/msal-migration). * Minor improvements to **AWS Assumed Role** data source for better reliability. * Various stability, reliability, and performance improvements. *** ## Release Date: 15 September 2025 ### Cost Map for Cloud Spend Analysis Cost map is a new feature that offers a visual and interactive representation of your cloud spend across regions and cloud providers. The **Cost map** page includes two tabs: * **Region** – This tab allows you to visualize your spending geographically across cloud deployments. * **Network traffic** –This tab allows you to analyze costs associated with data transfer and connectivity. Additionally, the Cost Explorer view now includes a new breakdown option called **Geography**, allowing you to analyze expenses by region. ### New Download functionality A new download option has been introduced to facilitate offline analysis, reporting, and integration with external tools. You can now download data from the following modules in FinOps for Cloud: * **Resources** – Download your resource data as an Excel spreadsheet or JSON file. You can also download Charts as PNG files. * **Cost explorer** – Download the data as a PDF. * **User management** – Export your list of users as an Excel spreadsheet or JSON file. ### New filters in resource view New filtering options are added to the [Resources](/insights/resources.md) page to help you narrow down and analyze cloud assets more effectively. You can now filter resources by: * **Multi-select fields** – This allows you to select multiple values across key dimensions for more flexible filtering. * **First seen date** – This allows you to identify newly discovered resources. * **Last seen date** – This allows you to track resources that might have been removed or are inactive. ### Improved email formatting We have enhanced the formatting of monetary values in all email communications. Currency values are now presented consistently for better readability and a reduced risk of misinterpretation, especially in automated alerts and summaries. *** ## Release Date: 15 May 2025 ### Global availability SoftwareOne's [FinOps for Cloud](https://portal.finops.softwareone.com/) is a new solution designed to help you optimize costs and manage your resources effectively. With FinOps for Cloud, you can explore and analyze your cloud expenses, monitor resource usage, and implement policies to ensure efficient and cost-effective cloud management. With a user-friendly interface and robust features, the solution provides greater visibility and control over cloud infrastructure. Use the left sidebar to learn more about these features in detail. --- # 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.finops.softwareone.com/help-and-support/release-notes.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.