TS80070 error on excel when trying to import a table from TFS.
Hi, This message appears on every mouse click while working with Excel Team imported list. (From our Azure DevOps cloud account). The user has basic Azure DevOps license, other users with the same license do not have any issues working with such imported lists.
Windows 10,
Excel 365, latest version
We have searched and tried all the forums solution, including reinstallation of the Office 365.
Thanks in advance
Azure DevOps
-
Durga Reshma Malthi • 6,835 Reputation points • Microsoft External Staff • Moderator
2025-06-25T12:33:13.5633333+00:00 Could you please try the below steps:
- Close Excel completely.
- Delete local TFS/Azure DevOps cache: %LOCALAPPDATA%\Microsoft\Team Foundation\7.0\Cache
- Open Excel -> File -> Options > Add-ins -> At the bottom, choose COM Add-ins > Click Go -> Uncheck or Remove Team Foundation Add-in -> Exit Excel
- Open Registry Editor and go to: HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\TFExcelAddIn.Connect
- Delete the TFExcelAddIn.Connect key
- Reopen Excel and re-enable the add-in if needed.
- Try Excel in Safe Mode
- Press
Win + R
, type:excel /safe
- Open the Azure DevOps query again
- Press
- Create a new local user account on Windows -> Log in with that user -> Set up Excel and connect to Azure DevOps again. If it works, the issue is in the original user's profile (roaming data, registry, etc.).
Additional References:
Hope this helps!
Please Let me know if you have any queries.
-
Durga Reshma Malthi • 6,835 Reputation points • Microsoft External Staff • Moderator
2025-06-26T08:19:42.77+00:00 Just checking in to see if you had a chance to review the response provided to your question.
Feel free to reach out if you have any further queries.
-
Ilya Polyansky • 5 Reputation points
2025-06-26T20:21:23.8933333+00:00 Hi, Thank you all for your support. Unfortunately, none of your suggestions worked, so I decided to try using ChatGPT to check if I missed something. Please see below the steps I tried based on ChatGPT’s guidance — bottom line, none of the following helped:
Initial Action: The working URL was changed from https://dev.azure.com/p-cure/ to https://p-cure.visualstudio.com/. This change successfully allowed Excel to connect and load Azure DevOps queries via the Team tab without authentication errors. However, after performing a repair on the Azure DevOps Office Integration 2019 installation, Excel began showing persistent authentication errors:TF31003: Unable to connect to the server.
TF30063: You are not authorized to access https://p-cure.visualstudio.com.
These errors persisted even when reverting back to the previously working URL (https://p-cure.visualstudio.com/), indicating that the repair had broken the authentication token handling or registry configuration.
Goal: Link Excel to Azure DevOps (TFS) using the Team tab to pull/push work item queries via https://p-cure.visualstudio.com/.
Actions Performed:
Environment Setup:
Verified user is an Azure DevOps administrator.
Confirmed the same Microsoft account is used in Excel and DevOps.
Confirmed user is listed in https://p-cure.visualstudio.com/_users.
Verified Team tab appears in Excel.
Confirmed only flat queries were used (not tree or linked queries).
Software Installation & Cleanup:
Installed Azure DevOps Office Integration 2019.
Repaired the Office Integration install (which triggered the issue).
Uninstalled legacy TFS 2015 components:
Microsoft Visual Studio Team Foundation Server 2015 Office Integration (x64)
Language Pack (x64) - ENU Verified Office version is 2016 or newer.
Credential & Cache Cleanup:
Cleared all related credentials from Windows Credential Manager (Windows Credentials + Web Credentials).
Deleted:
%LOCALAPPDATA%\Microsoft\Team Foundation
%APPDATA%\Microsoft\Team Foundation Removed registry keys: HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\TFCOfficeShim.Connect.14 HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\TFCOfficeShim.Connect.16 HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\AddInLoadTimes\TFCOfficeShim.* Recreated the missing registry key under Addins: TFCOfficeShim.Connect.16 with LoadBehavior = 3
Authentication Fixes:
Signed out of all Office accounts in Excel and signed in again.
Removed and re-added account under Windows Settings → Accounts → Email & Accounts.
Verified access to the Azure DevOps project.
Set registry to force modern authentication:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity
EnableADAL = 1 Version = 1
Internet Options Configuration:
Added both URLs to Internet Options → Security → Trusted Sites:
https://p-cure.visualstudio.com
https://*.visualstudio.com Disabled "Require server verification" checkbox.
Testing & Workarounds:
- Attempted simplified one-work-item queries.
Created minimal flat queries with basic fields only (ID, Title, State).
Cleared Excel COM Add-ins except for Team Foundation Add-in.
Attempted to use Excel Safe Mode (confirmed Team tab is hidden in safe mode).
Switched between p-cure.visualstudio.com and dev.azure.com URLs.
Observed: After using correct URL, authentication worked, but stopped after running a repair.
Current Problem: TF31003 and TF30063 errors continue to appear even though setup is otherwise correct. Team tab is present and queries load partially or completely, but authentication fails due to broken or blocked token handoff likely caused by the repair process.Initial Action:
The working URL was changed from https://dev.azure.com/p-cure/ to https://p-cure.visualstudio.com/.
This change successfully allowed Excel to connect and load Azure DevOps queries via the Team tab without authentication errors.
However, after performing a repair on the Azure DevOps Office Integration 2019 installation, Excel began showing persistent authentication errors:TF31003: Unable to connect to the server.
TF30063: You are not authorized to access https://p-cure.visualstudio.com.
These errors persisted even when reverting back to the previously working URL (https://p-cure.visualstudio.com/), indicating that the repair had broken the authentication token handling or registry configuration.
Goal:
Link Excel to Azure DevOps (TFS) using the Team tab to pull/push work item queries via https://p-cure.visualstudio.com/.Actions Performed:
Environment Setup:
Verified user is an Azure DevOps administrator.
Confirmed the same Microsoft account is used in Excel and DevOps.
Confirmed user is listed in https://p-cure.visualstudio.com/_users.
Verified Team tab appears in Excel.
Confirmed only flat queries were used (not tree or linked queries).
Software Installation & Cleanup:
Installed Azure DevOps Office Integration 2019.
Repaired the Office Integration install (which triggered the issue).
Uninstalled legacy TFS 2015 components:
Microsoft Visual Studio Team Foundation Server 2015 Office Integration (x64)
Language Pack (x64) - ENU Verified Office version is 2016 or newer.
Credential & Cache Cleanup:
Cleared all related credentials from Windows Credential Manager (Windows Credentials + Web Credentials).
Deleted:
%LOCALAPPDATA%\Microsoft\Team Foundation
%APPDATA%\Microsoft\Team Foundation Removed registry keys: HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\TFCOfficeShim.Connect.14 HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\TFCOfficeShim.Connect.16 HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\AddInLoadTimes\TFCOfficeShim.* Recreated the missing registry key under Addins: TFCOfficeShim.Connect.16 with LoadBehavior = 3
Authentication Fixes:
Signed out of all Office accounts in Excel and signed in again.
Removed and re-added account under Windows Settings → Accounts → Email & Accounts.
Verified access to the Azure DevOps project.
Set registry to force modern authentication:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity
EnableADAL = 1 Version = 1
Internet Options Configuration:
Added both URLs to Internet Options → Security → Trusted Sites:
https://p-cure.visualstudio.com
https://*.visualstudio.com Disabled "Require server verification" checkbox.
Testing & Workarounds:
Attempted simplified one-work-item queries.
Created minimal flat queries with basic fields only (ID, Title, State).
Cleared Excel COM Add-ins except for Team Foundation Add-in.
Attempted to use Excel Safe Mode (confirmed Team tab is hidden in safe mode).
Switched between p-cure.visualstudio.com and dev.azure.com URLs.
Observed: After using correct URL, authentication worked, but stopped after running a repair.
Current Problem:
TF31003 and TF30063 errors continue to appear even though setup is otherwise correct. Team tab is present and queries load partially or completely, but authentication fails due to broken or blocked token handoff likely caused by the repair process. -
Durga Reshma Malthi • 6,835 Reputation points • Microsoft External Staff • Moderator
2025-06-27T07:41:20.8633333+00:00 Could you please try the below steps to resolve this issue:
- Office sometimes caches tokens in a hidden location outside Credential Manager. Try this:
- Open Command Prompt as admin.
- Run the cmd:
dsregcmd /leave
- Then reboot and rejoin the device to Azure AD (if applicable).
- Sign back into Office and retry Excel Team tab.
- Modern Office authentication uses WebView2. Try clearing its cache:
- Navigate to: %LOCALAPPDATA%\Microsoft\EdgeWebView
- Delete the entire folder (Office will recreate it).
- Reboot and relaunch Excel.
- If possible, create a test user in the same Azure DevOps org and try connecting via Excel. If it works, the issue is likely user-profile-specific rather than machine-wide.
Hope this helps!
Please Let me know if you have any queries.
- Office sometimes caches tokens in a hidden location outside Credential Manager. Try this:
-
Durga Reshma Malthi • 6,835 Reputation points • Microsoft External Staff • Moderator
2025-06-30T08:51:08.34+00:00 Hi Julia Ginzburg / Ilya Polyansky
Just checking in to see if you had a chance to review the response provided to your question.
Feel free to reach out if you have any further queries.
-
Durga Reshma Malthi • 6,835 Reputation points • Microsoft External Staff • Moderator
2025-07-01T08:53:49.3+00:00 Hi Julia Ginzburg / Ilya Polyansky
Just checking in to see if you had a chance to review the response provided to your question.
Feel free to reach out if you have any further queries.
-
Defendsys • 0 Reputation points
2025-07-02T07:49:16.8733333+00:00 Hi Durga,i will keep you updated today if it helped.
thank you,
Ori
-
Defendsys • 0 Reputation points
2025-07-02T07:50:59.67+00:00 also - please note that we use local AD so advising a user to leave the domain is risky :)
-
Defendsys • 0 Reputation points
2025-07-02T10:37:35.7066667+00:00 Hi Durga,
We will attend this tomorrow, and will keep you updated.
thank you!
-
Durga Reshma Malthi • 6,835 Reputation points • Microsoft External Staff • Moderator
2025-07-03T08:02:33.4733333+00:00 Hi Defendsys
Please let me know if you have tried the above workaround.
Feel free to reach out if you have any further queries.
-
Durga Reshma Malthi • 6,835 Reputation points • Microsoft External Staff • Moderator
2025-07-04T08:24:15.27+00:00 Hi Defendsys
Please let me know if you have tried the above workaround.
Feel free to reach out if you have any further queries.
Sign in to comment