Power Query Problems

How to Fix Excel OData Basic Authentication Issues in Data Model

Olivia MillerOlivia Miller Nov 2, 2026 869 views

Question details

Users experience an endless loop requesting Basic authentication credentials when trying to connect to an OData feed using the legacy Manage Data Model wizard, despite successful connection tests.

How to Fix Excel OData Basic Authentication Issues in Data Model
Product
Microsoft Excel
Device & OS
not provided
Scenario
Importing data from an external OData feed into the Excel Data Model using Basic authentication.
Observed behavior
The legacy Manage Data Model and OData import wizard repeatedly prompt for Basic authentication credentials and fail to establish the final connection.
Before you start

Verify that your OData feed URL is currently accessible and that your Basic authentication credentials (username and password) are active and correct before configuring the new connection in Excel.

Solution 1Recommended

Use the Power Query OData Feed Connector

Bypass the legacy Manage Data Model bug by using the modern Power Query connector, which handles Basic authentication correctly.

Microsoft's modern Power Query engine properly manages Basic authentication tokens for OData feeds, unlike the legacy Manage Data Model wizard. Connecting through this newer interface resolves the credential loop while still allowing you to load the data into the Data Model.

1
Open Get Data Menu

Navigate to the 'Data' tab on the Excel ribbon. Click on 'Get Data' located in the Get & Transform Data group.

2
Select OData Feed

Hover over 'From Other Sources' in the dropdown menu, then select 'From OData Feed'.

3
Enter URL and Credentials

Paste your OData feed URL into the dialog box. When prompted for credentials, select the 'Basic' tab and enter your username and password.

4
Load to Data Model

Once the preview window loads, click the arrow next to 'Load', select 'Load To...', and check the box for 'Add this data to the Data Model'.

Use the Power Query OData Feed Connector
Connection Secured: Using Power Query securely stores your Basic authentication credentials in your Data Source Settings, preventing the repeated login prompts.
Free Microsoft Office alternative

Try WPS Office as a Seamless Spreadsheet Alternative

If you frequently encounter legacy feature bugs or slow performance in complex spreadsheet environments, consider switching to WPS Office. It provides a highly compatible, lightweight, and efficient platform for all your essential data tasks.

  1. 1. Download and Install: Visit the official WPS Office website to download the lightweight installer for your operating system.
  2. 2. Open Your Workbooks: Launch WPS Spreadsheet and open your existing .xlsx files without worrying about formatting loss.
  3. 3. Analyze Data Smoothly: Use the familiar ribbon tools to process, analyze, and visualize your data seamlessly.
Fully compatible with Microsoft Excel formats (.xlsx, .xls, .csv).Lightweight application that loads quickly and saves system memory.Familiar tabbed interface requiring zero learning curve to get started.Rich set of built-in data analysis and visualization tools completely free.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Excel's Manage Data Model keep asking for my OData credentials?

This is a known issue with Excel's older, legacy Manage Data Model wizard. It often fails to securely pass Basic authentication credentials to the OData server, resulting in an endless loop of credential prompts.

What is the difference between Manage Data Model and Power Query Get Data?

Manage Data Model uses an older framework for importing data. Power Query (accessed via 'Get Data') is Microsoft's modern, robust data connectivity tool that correctly handles advanced connections and modern authentication protocols.

Can I still add the OData feed to my Data Model using Power Query?

Yes. After connecting via Get Data > From OData Feed, you can choose 'Load To...' instead of a standard 'Load', and then check the box labeled 'Add this data to the Data Model'. This bypasses the bug while achieving the exact same result.