ODATA Feed credentials error

Hii G_CR_23 

Requesting IT to configure Kerberos Constrained Delegation on the Standard Gateway is the proper and definitive fix. There is no reliable workaround unless:

• Business Central is reconfigured to support another auth method (e.g., AAD), or

• You switch to a different integration approach (e.g., API layer).

Your Fiddler findings align exactly with expected behavior.

Hi G_CR_23,

Thank you rohit1991, for your insights.

This issue arises because Power BI Desktop connects to on-premises Microsoft Dynamics 365 Business Central using Windows authentication, but Power BI Service uses an Azure AD bearer token, which the on-prem server can't accept. To resolve this, you need to install a Standard On-premises data gateway and set up Kerberos Constrained Delegation in Active Directory. The gateway should run under a dedicated domain service account with the necessary SPNs and delegation permissions, allowing it to impersonate users and authenticate to Business Central via Kerberos. That Personal Gateway mode won't work in this case. This is an infrastructure authentication setup requirement, not a Power BI credential problem.

Configure Kerberos-Based SSO from Power BI Service to On-Premises Data Sources - Power BI | Microso…

Active Directory (AD) SSO - Power BI | Microsoft Learn

Overview of single sign-on for on-premises data gateways - Power BI | Microsoft Learn

Test single sign-on (SSO) configuration - Power BI | Microsoft Learn

Thank you.