Power BI OData integration for business application data
Power BI OData integration connects reports to any system that publishes its data as an OData feed. OData is an open standard for data over the web, and many business applications expose one. Microsoft documents an OData Feed connector, so Power BI reads a feed from its service URL. However, feeds can be slow when a query asks for too much, so design matters.
- OData Feed connector
- Filters at the source
- Refresh without surprises
Last updated
How does Power BI OData integration read a feed?
The author chooses the OData Feed connector and pastes the root URL of the service. Then Power BI asks for a sign-in type. Microsoft's page lists anonymous, Windows, basic, Web API key and organizational account.
After that, the navigator lists the entity sets in the feed, which look like tables. The author picks the ones a report needs. There is also a button that selects related tables, because feeds describe how their entities link.
Power BI then imports the rows into the semantic model. So the report works from a copy, and a scheduled refresh updates it. One limit is worth knowing early: Microsoft states that this connector does not support Microsoft Graph.
Where OData feeds for Power BI usually come from
The source decides the sign-in method and whether a gateway is part of the route.
Cloud business apps
Many hosted ERP and CRM products publish a feed. These usually sign in with an organizational account.
On-premises systems
A feed inside the company network needs an on-premises data gateway. Also, Windows and basic sign-in require one.
Custom services
Developers can publish their own feed over a database. Then the feed exposes only the fields that reporting should see.
Why are some OData feeds slow in Power BI?
A feed returns data in pages over the web. So a table with many rows and wide columns takes many round trips. Each trip is small, but together they make a refresh long.
The fix is to ask for less. Power Query can pass filters and column choices back to the feed, so the source does the trimming. For example, a filter on the posting date can limit a ledger table to recent periods. We check each step to confirm the feed really applies it.
Expanded related columns are another cause. Instead of expanding a customer record on every order row, we load customers once as their own table. Then the model joins them, which is what it does best.
Common faults in a Power BI OData integration
Most feed problems we fix trace back to one of these six points.
- The query loads every column of every entity
- Filters run in Power BI, not at the source
- Related records expand on each row
- The service test fails on a URL with filters
- Credentials belong to a person who left
- No gateway exists for an internal feed
Our steps for Power BI OData integration
We follow four stages and show the result each week.
Read the feed
First we open the service document and list the entities, keys and links it offers.
Write the quote
Then the scope goes on paper: which entities, which measures and which pages.
Shape the queries
We select columns, push filters to the source and build a star schema in your tenant.
Prove the refresh
Finally, we schedule refresh, time it and note the settings, so your team can maintain it.
Questions about OData feeds and Power BI
Does Power BI have a native OData connector?
Yes. Microsoft's Power Query connector list includes OData Feed, and it is generally available for Power BI semantic models and dataflows. The author enters the service root URL and a sign-in type. Microsoft's article also covers advanced options and known issues, so it is the right reference for current details.
Does an OData feed need a gateway in Power BI?
It depends on the feed. A public cloud feed with an organizational account or an API key often refreshes without one. However, Microsoft's page marks Windows and basic sign-in as requiring a gateway. A feed on an internal network needs one too, because the service cannot reach it directly.
Can Power BI use DirectQuery over OData?
The OData Feed connector is an import route. So Power BI copies the rows on each refresh instead of querying the feed per visual. When a business needs near real-time figures, we look at the system behind the feed. A database or a lakehouse copy is often the better live source.
When is OData the wrong route into Power BI?
It is a weak fit for very large tables, since paging over the web takes time. When a product also offers a dedicated connector or a database export, that path is usually faster. So we compare the options first. Sometimes a staging database fed from the application is the simple answer.
How do we begin an OData project with Power BI Agency?
Send us the feed URL and a short note on what the report should show. We reply within 2 hours and set up a free 30-minute assessment with one of our consultants. Power BI Agency is a division of Sataware Technologies, independent of Microsoft. The phone number is (480) 485-7373.
Let's build your first dashboard together.
Tell us what you report on today. A consultant replies within 2 hours with next steps.
Trusted partners
Microsoft Solutions Partner · AWS Partner
Cloud & AI Platforms
Azure SQL, Microsoft Fabric and the data pipelines behind your reports.
AI Business Solutions
Power BI reporting on your Dynamics 365, Business Central and Power Platform data.
Security
Row-level security and Entra ID sign-in on every report and workspace.
Amazon Web Services
Power BI on your AWS data, with connectors for Redshift, Athena and S3.