OneStream figures into Azure and Power BI
CPM data from OneStream
Yres retrieves data from OneStream through the REST API of your OneStream environment. You provide the environment's address and the name of the OneStream application, and choose how Yres signs in: with OAuth2 client credentials through your identity provider, or with a personal access token from OneStream. The data lands in an Azure SQL database in your own Azure tenant.
At a glance
- Connection
- The REST API (Web API) of your OneStream environment; you provide the base address and the application name
- Sign-in
- A choice between OAuth2 client credentials (client ID, client secret and your identity provider's token address) and a personal access token created in OneStream
- Identity providers for OAuth2
- Microsoft Entra ID, Okta or PingFederate: wherever the application for the OneStream Web API is registered
- Incremental loading
- OneStream is among the sources for which two delta columns are supported; the higher of the two values counts
- Network
- The cloud integration runtime by default. A self-hosted runtime is only needed if OneStream is reachable solely inside a closed network
- What is stored
- Address, application name, sign-in method and the token or client details sit in the Key Vault of your own Azure environment
What you arrange yourself
- 1Ask your OneStream administrator for the base address of the REST API and the exact application name.
- 2Choose the sign-in method. For OAuth2: have an application registered with your identity provider with a client secret, and have it authorised for the OneStream Web API. Copy the secret immediately; it is usually visible only once.
- 3For a personal access token: have the token created in OneStream.
- 4Add the OneStream source in Yres and fill in the fields that belong to the chosen sign-in method. With Entra ID the token address is https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token.
When you need this — and when you don't
A standalone connector is enough if…
If your consolidation and planning reporting stays inside OneStream and only finance users read it, a data warehouse adds little.
Yres adds value if…
Yres earns its place when consolidated figures and planning data from OneStream must sit in Power BI next to operational sources such as ERP, HR or sales data, so the rest of the organisation works from the same numbers.
Frequently asked questions: OneStream
What should I ask my OneStream administrator before I start?
Three things: the base address of the REST API of your OneStream environment, the exact name of the OneStream application, and the sign-in details. The latter is either a personal access token, or the client ID, client secret and token address of the application registered with your identity provider for the OneStream Web API.
Should I choose OAuth2 or a personal access token?
Both are supported. With OAuth2, Yres signs in as an application registered with your identity provider; you enter client ID, client secret and the token address. A personal access token is created in OneStream itself and needs only that one field.
Does OAuth2 sign-in only work with Microsoft Entra ID?
No. The application can be registered with Microsoft Entra ID, Okta or PingFederate. You enter that provider's token address. Have your OneStream administrator set up the registration and the authorisation for the OneStream Web API.
Who in my organisation do I need to involve?
Your OneStream administrator, who supplies the address, the application name and the token or client details. For OAuth2 you also need the administrator of your identity provider for the app registration and the client secret.
Full technical description in the knowledge base →·Last reviewed:
Data warehouse automation that runs in your own Azure
Built for organisations on Azure and Power BI. Yres connects your sources, keeps the history and promotes changes in a controlled way, without manual work.