When Password Changes Break RoboHelp: A Fix for Azure DevOps Credential Issues

For far too long, every domain password change at our organization triggered a now-familiar headache: our RoboHelp projects—sourced from Azure via Team Foundation Server (TFS)—would suddenly become unreachable inside RoboHelp. We could still access the source files externally, but within RoboHelp, the connection vanished in a "You are not authorized..." message. The workaround? Limping through until something clicked or the cache cleared.

Despite working with both internal IT and Adobe support, the issue persisted for years. Everyone knew the drill: change your password, brace for disruption, lose a day, several days, or a week of productivity.

That is—until we finally figured out a reliable fix. If you’re a technical writer or content developer using RoboHelp with Azure DevOps and TFS, here’s what you need to know.

🔧 The Root of the Problem

RoboHelp caches your Azure DevOps credentials. But if your domain password changes and RoboHelp doesn’t re-prompt for new credentials, it can silently fail to authenticate—and won’t reconnect until the cache is reset.

✅ The Fix: Force Reauthentication with tf.exe

This solution uses Microsoft’s tf.exe utility from Visual Studio’s Team Explorer to force a credential reset.

Manual Reset via Command Prompt

• Close RoboHelp completely.
• Open Command Prompt: press Windows + R, type cmd, then press Enter.
• Navigate to the Team Explorer directory:

cd "C:\Program Files (x86)\Microsoft Visual Studio\2019\TeamExplorer\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer"        

• Run the following command:

tf settings connections /switchuser https://dev.azure.com/YOUR_ORG_NAME        

• When prompted, log in with your updated Azure DevOps credentials.
• Reopen RoboHelp and access your project.

What this does: The command clears cached credentials and prompts a fresh login session. RoboHelp then inherits this updated authentication.

One-Click Scripted Reset

If this happens often, I suggest making a script to put on your desktop to accomplish this same goal. When you need to reset it to resume work in RoboHelp, double-click the script, log in, and resume working.

Here is a script You can modify to work in your own organization:

@echo off
echo Press any key to reset your TFS login.
pause >nul

"C:\Program Files (x86)\Microsoft Visual Studio\2019\TeamExplorer\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\tf" settings connections /switchuser https://dev.azure.com/YOUR_ORG_NAME

echo TFS Login reset completed.
echo Press any key to exit.
pause >nul        

Make sure you clear any of these procedures with your IT department before performing them.

💡 Final Thoughts

This may seem like a small technical hiccup—but for documentation teams working under deadlines, a “limping” tool can create real bottlenecks. It’s a quiet productivity killer.

If this issue sounds familiar, I hope this fix saves you the hours we lost. Sometimes the best solutions come from within the trenches—not from tickets or forums, but from persistence and community sharing.

Let’s make technical writing a little smoother—one workaround at a time.

#TechSupport #WritersHelpingWriters #TFS #RoboHelp #AzureDevOps #TechnicalWriting

Eric Johnson is a Lead Technical Writer at Sphera Solutions, where he's been shaping clear, effective documentation since April 2022. Outside of work, Eric writes novels, fosters cats, and enjoys the tranquility of life beside a 7-acre lake.