Data Import & Export

How to Connect Excel and Power BI to an OAuth 2.0 OData Feed

Anum MushtaqAnum Mushtaq Nov 11, 2026 869 views

Question details

The user wants to securely connect Microsoft Excel or Power BI to an OData service protected by OAuth 2.0 to enforce user-specific data access.

How to Connect Excel or Power BI to an OAuth 2.0 OData Feed
Product
Microsoft Excel, Power BI
Device & OS
not provided
Scenario
Importing data from a secure OData service requiring OAuth 2.0 authentication into spreadsheet or BI tools.
Observed behavior
Native OData feed connections may not directly support custom OAuth 2.0 configurations without workarounds like API gateways or custom connectors.
Before you start

Ensure you have the necessary endpoint URLs, client IDs, and authorization details for your OAuth 2.0 OData feed, and verify your organization's security and data access policies before proceeding.

Solution 1Recommended

Use Native Power Query OData Authentication

Use the built-in OData feed connector in Excel and Power BI to test and configure available OAuth 2.0 settings via organizational accounts.

Current versions of Excel and Power BI support OAuth 2.0 for Microsoft-based and specific third-party OData feeds natively through Power Query's Organizational Account sign-in.

1
Open Get Data

Launch Excel or Power BI Desktop. Navigate to the Data tab (in Excel) or the Home tab (in Power BI) and select Get Data > From Other Sources > From OData Feed.

2
Enter the Feed URL

Input the base URL of your OData service and click OK.

3
Select Authentication Method

In the authentication window, select 'Organizational account' on the left sidebar to trigger the OAuth 2.0 login flow.

4
Sign In and Connect

Click Sign In, enter your credentials in the OAuth pop-up, and click Connect to load your user-specific data.

Use Native Power Query OData Authentication
Compatibility Limitation: This method relies on Azure Active Directory or natively supported OAuth providers. If your OData feed uses a custom OAuth 2.0 implementation, this native option may fail.
Free Microsoft Office alternative

Try WPS Office for Your Data Analysis Needs

While advanced custom OData connectors for proprietary OAuth implementations are specific to Microsoft's Power Query environments, WPS Office provides a free, lightweight, and highly compatible alternative for everyday spreadsheet data analysis. Enjoy familiar features, seamless Excel format compatibility, and advanced data processing without expensive subscriptions.

  1. 1. Download WPS Office: Visit the official WPS website to download and install the free, lightweight suite.
  2. 2. Open Your Spreadsheets: Launch WPS Spreadsheet and seamlessly open any exported .xlsx or .csv files generated from your data feeds.
  3. 3. Analyze Data Quickly: Utilize powerful built-in pivot tables, formulas, and chart functions to analyze your data effortlessly.
Fully compatible with Microsoft Excel (.xlsx, .xls, .csv) formats.Free, lightweight, and incredibly fast to install and launch.Familiar user interface requiring zero learning curve.Built-in tools for data cleaning, pivot tables, and professional charting.
QA img-9

Frequently Asked Questions

Why doesn't the Excel OData connector accept my OAuth 2.0 credentials?

Native OData connectors in Excel typically only support specific OAuth flows like Azure AD or predefined Organizational accounts. If your OData service relies on a custom or third-party OAuth 2.0 provider, the native connector may not recognize the authorization flow, requiring an API gateway or custom connector.

Can I use Power Query Custom Connectors directly in Excel?

Custom connectors built with the Power Query SDK are primarily designed and optimized for Power BI Desktop. While there is limited support in specific Excel versions, utilizing an API gateway is generally the more stable and widely supported approach for Excel users.

How do I secure user-specific data access when using an API gateway?

To enforce user-specific access, ensure your API gateway passes user identity context (such as via specific headers or passthrough tokens) to the backend OData service. Implement strict access control policies both at the gateway layer and the underlying database.