Snowflake data into your Azure data warehouse and Power BI
Integrate Snowflake data
Yres reads Snowflake through a direct connection. Instead of a host and port you enter the Snowflake account identifier, plus the database, the virtual warehouse that runs the queries, a user with read access and optionally a role. Because Snowflake is a publicly reachable cloud data warehouse, Yres normally uses the Azure Data Factory cloud runtime. The selected tables land in an Azure SQL database in your own Azure tenant, next to your other sources, ready for Power BI. Plan for full loads for now: incremental filtering is not yet guaranteed for Snowflake.
At a glance
- Connection
- Direct connection with user name and password. No host or port field: you enter the account identifier
- Required fields
- Account name, user name, password, database and warehouse
- Role
- Optional. Leave it empty and the Snowflake user's default role applies
- Warehouse
- An existing, active virtual warehouse; it runs the queries Yres issues
- Integration runtime
- Normally the cloud runtime. Self-hosted only when Snowflake sits behind a firewall or private link
- Incremental loading
- Currently not guaranteed: the change filter is not guaranteed to be applied for Snowflake. Full loads work
- Credentials
- Account, user, password, database, warehouse and role are written as secrets to your own Azure Key Vault and are not stored in Yres
What you arrange yourself
- 1Look up the account identifier in Snowsight through the account menu at the bottom left (View account details), or derive it from the account URL.
- 2Under Admin → Warehouses, choose an existing, active virtual warehouse for the queries Yres runs.
- 3Create a separate Snowflake user with read-only access to the database, and decide whether it should use a specific role.
- 4Add the Snowflake source in Yres, fill in the fields, refresh the metadata and select the tables.
When you need this — and when you don't
A standalone connector is enough if…
If all the data you report on already lives in Snowflake and Power BI reads from it directly, you do not need a second data warehouse in Azure.
Yres adds value if…
Yres earns its place when Snowflake is one of several sources: for example a data platform run by a sister company, supplier or another team, part of which you want to combine with your own ERP, HR or CRM data in a single Azure environment you manage yourself.
Frequently asked questions: Snowflake
Can Yres load incrementally from Snowflake?
You cannot count on that at the moment. You can configure change columns, but for Snowflake the filter on those columns is not guaranteed to be executed. So assume full loads and choose your tables and schedule accordingly.
Where do I find the account name Yres asks for?
It is the Snowflake account identifier, preferably in the organisation-account form; the older account locator works too. You find it in Snowsight through the account menu at the bottom left under View account details, or in the account URL in front of snowflakecomputing.com.
Why does Yres ask for a warehouse and a role?
The virtual warehouse runs the queries Yres uses to read the tables; it has to exist already and be active. The role determines which permissions the connection has. The role is optional: without one, Snowflake uses the user's default role.
Do I have to arrange staging storage for the Snowflake connection myself?
No. The connector internally uses a storage container as an intermediate step while copying. It is part of the Yres infrastructure and needs no extra input or setup from you.
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.