"The service returned an invalid token" error

[coverturfLSH]

Hi,

I'm using Power Query to connect to a Microsoft Fabric warhouse via the SQL Server connector. I received an error message when I went to refresh my query that says "The service returned an invalid token. Please contact your IT administrator". In searching for a solution, I saw several posted solutions but the only one that worked for me was disconnecting from my current wifi, connecting to my phone's hot spot, signing in, then going back to my old/current wifi. 

It seems as though there's an "internal" type token that was valid for approximately a year but needed a reset. For others that are running into this issue, I'm suggesting what I did and it works for them. But I'm wondering if anyone else has had this issue and if there are alternative resolution options as not every has a wifi hotspot available to them.

Thanks,

[v-venuppu]

Hi @coverturfLSH ,

If you receive any added insights from MIcrosoft after raising the Support Ticket, you can post it here so that it will be helpful for others in the community who are facing similar issues to find solutions more easily.

Thank you.

[v-venuppu]

Hi @coverturfLSH ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @Poojara_D12 @PacoTaco @tayloramy for the prompt response.

I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.

Thank you.

[coverturfLSH]

Hi venuppu,

All of the responses have provided the same solution that is already working for me. I'm going to open a support ticket with Microsoft when I have time and can recreate the issue to see if they're aware of the problem.

[Poojara_D12]

Hi @coverturfLSH 

When connecting to a Microsoft Fabric warehouse through the SQL Server connector in Power Query, you might occasionally encounter the error message “The service returned an invalid token. Please contact your IT administrator.” This issue generally occurs because the authentication token that Power Query uses to connect to the Fabric service has expired or become invalid—often after a long period (around a year) without being refreshed. In your case, disconnecting from your current Wi-Fi, switching to a mobile hotspot, re-signing into the Fabric service, and then reconnecting to the original network effectively forced Power Query to request a new authentication token. While this workaround resolves the issue, it suggests that the problem lies in cached credentials or token renewal not functioning properly within the local network or tenant authentication flow. Other users have reported similar experiences, and alternative solutions include clearing stored credentials from the Data Source Settings in Power BI or Excel, re-authenticating to the Fabric workspace through Organizational Account login, or removing and re-adding the Fabric data source connection. Essentially, the goal is to trigger a new token issuance—without relying on a network change—so that Power Query can successfully authenticate again.

[PacoTaco]

Hello,

Did you ever find a solution to this problem.

This just started to happen to me. Same issue. 

The onlu was to get past this is to use my mobile hotspot.

[coverturfLSH]

Switching internet is the only thing that's worked for me. The good thing is you can switch back to your original connection after signing in on the new connection.

[tayloramy]

Hi @coverturfLSH, 

I am very facinated by this. This has bever happened in my environment and I have over 1000 users and have had my capacity since before Fabric existed, it was an old Power BI premium capacity. 

We have had issues with our firewall blocking SQL ports and therfore blocking SQL endpoints in client tools, but this doesn't sound like that. 

Are you able to re-create this issue? I wonder if I could somehow replicate it in my environment. If it is replicatable, then I would wager to say this is a bug and should be reported. 

If you found this helpful, cosnider giving Kudos. If I solved your problem or answered your question, mark this post as a solution. 

[coverturfLSH]

I think it's very specific to using Power Query to connect to a Fabric Warehouse. I have several users who are connecting this way through a process I created about a year ago. And they're slowly one by one starting to receive this error message. I guess the other way I could think of to replicate the issue would be to create a PQ connection to a warehouse and then wait a year to see if the token expires.

Not much to go on, but since Fabric warehouses were released over a year ago, I was wondering if any others were starting to encounter the issue.