Proxy authentication error 2606 stops OneDrive, Outlook or Teams from signing in, and says a proxy would not let the client through. The first useful thing to know is that Microsoft does not publish a meaning for the number. It is not on their own list of OneDrive error codes.
Which is why every guide on this error gives you steps instead of an explanation. There is one fix that circulates everywhere, a single command pasted from a Microsoft forum thread where more than six hundred people have clicked "same question". It helps some of them. It also does not do what every page recommending it says it does, and Microsoft's own documentation is where that becomes clear.
So: what the error is actually telling you, what Microsoft does and does not document, what that command actually erases and what it leaves untouched, the five checks worth running first, and what to do when the proxy is genuinely asking for credentials rather than imagining it.
Quick Answer: Proxy Authentication Error 2606
What Proxy Authentication Error 2606 Is Telling You
Two things, and only two. A Microsoft 365 client tried to sign in, and something in the path presented itself as a proxy demanding credentials that the client could not satisfy.
That is the whole message. Everything else has to be worked out from context, because the number itself is undocumented.
It shows up most often in OneDrive, where people meet it as a sync that will not start, and the same string appears in Outlook and Teams. The Microsoft Q&A thread most of this advice is copied from is titled for OneDrive, and its counter shows more than six hundred people have clicked "same question" on it.
| What the message tells you | What it does not tell you |
|---|---|
| A proxy was involved in the attempt | Whether that proxy is real or a leftover entry on your own machine |
| Authentication to it did not succeed | Whether credentials were wrong, missing, or never requested properly |
| The client stopped rather than continuing | Which of Windows' several proxy stores it was reading |
That last row matters more than it looks. Windows does not keep one proxy setting, it keeps at least three: the per-user WinINET configuration, the WinHTTP one that services read, and the environment variables command-line tools follow. Knowing which one a failing application reads is the difference between a two-minute fix and an afternoon, and our guide to where Windows actually keeps its proxy settings maps all three.
If the word proxy itself is doing unfamiliar work here, the general version is covered in how a proxy server works and where it sits in a network, and the setting people are usually being asked about is explained in what that Configure Proxy setting means.
One detail from that thread is worth carrying forward without overstating it. The person who opened it said the error began after a password change. That is one report from one machine, not a pattern, but it is the only trigger anybody names.
Why the Number Is Missing From Microsoft's Own Error List
Microsoft publishes a page called What do the OneDrive error codes mean?. Its own instruction to the reader is to "Select your error message or error code from the lists below to learn more". It documents entries like "OneDrive cannot connect to Windows", "You do not have access permissions to the item" and "Couldn't start Files on Demand".
2606 is not on it, checked on 23 September 2026. Nor could I find the number defined anywhere else Microsoft publishes. That explains something about the search results you have probably already been through: every one of them gives you a list of steps, because a list of steps is all anyone has.
Be careful what you take from that. It does not mean the error is fake or that your machine is unusual. Applications carry internal codes that never reach public documentation, and this is one of them. What it does mean is that anybody telling you confidently what 2606 stands for is guessing, and you should treat their next sentence accordingly.
What Microsoft does publish, on a different page entirely
So the next question is not what a custom Internet option is. It is whether the fix everybody recommends removes one.
The Fix Everyone Recommends Does Not Do What They Think
The accepted answer in that Microsoft thread, posted in February 2024 and marked helpful by more than a hundred people, is five short steps: sign out of your Microsoft account, open the Run box, run one command, leave the checkbox in the dialog clear, then sign back in. Its own wording calls the Run box a command prompt window, which is worth knowing before you go looking for the wrong thing.
# opens the Internet Options reset dialog.
# leave the "Delete personal settings" box UNCHECKED.
Now the part that changes how you should think about this, and which I did not find on any of the ranked pages I read on 23 September 2026, including TheWindowsClub, Pixelscan, VPNCentral and Izoate. That reset does not touch your proxy settings.
Microsoft's own Internet Explorer team documented the feature the command invokes, and the sentence is unambiguous: "RIES does not clear Favorites and Feeds. It also does not reset Connection settings as the settings can be used from other programs." Connection settings is where the proxy lives. The reset leaves it alone by design.
There is a second piece of evidence, and it is the kind I find more persuasive than any single sentence. Microsoft publishes a separate article for resetting Internet Explorer proxy settings, and its method is not this command at all. It is two registry operations:
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v ProxyServer /f
Two notes on those, because Microsoft prints them in a form that does not run. The key path contains a space, and Microsoft's own reference for the command says: "If the registry key name contains a space, enclose the key name in quotes." Their proxy article omits the quotes. I have added them above, and without them reg.exe reads the key as ending at "Internet" and rejects the rest.
The second note is where to type them. Microsoft's article puts each one in the Run box rather than a terminal, which works either way, and it tells you to back up the registry first. That is worth doing.
That article never mentions the reset command anywhere. If the reset cleared the proxy, the article would have no reason to exist.
So why does the reset help anybody? Microsoft does not say, and I am not going to invent a mechanism. What the same page does list is everything RIES does clear: "Temporary Internet Files, Cookies, Browsing History, Form data, passwords and auto-complete data", plus every user-defined browser setting. A stale cached credential sitting in that pile is the explanation I would reach for first, and I want to be clear that reaching for it is my reading, not Microsoft's.
Which leaves the two commands above as the targeted option. If a proxy entry really is the problem, those change exactly that and nothing else.
The elephant nobody on this topic mentions
1 Write down what is there first
2 Read the other store too
3 Sign out of the client
4 Run the command, leave the box unchecked
5 Sign in, then check what changed
Which brings us to the cost, because this command is not free even though it spares your proxy.
What That Command Actually Costs You
Microsoft prints a note directly beneath the advice to reset. None of the four ranked pages named above carries it, and it matters more now that we know what the reset really clears.
The sentence nobody quotes
There is a second reason for caution. The thread everybody quotes is locked, because it was migrated from the old Microsoft Support Community, so nobody can add an outcome to it either way. The accepted answer dates from February 2024 and carries a counter saying more than a hundred people found it helpful. What nobody can tell you from that page is how many ran it and got nowhere.
An undocumented number, a locked thread and a fix whose own documentation says it does not touch the setting being blamed is a poor reason to start by clearing your passwords. Start with the checks instead.
The Five-Minute Checks That Come First
Run these in order before you reset anything. Between them they separate a phantom proxy from a real one, which decides everything that follows.
netsh winhttp show advproxy
# Microsoft has deprecated the older form, but it is the one
# Windows 10 has, and it still works on Windows 11:
netsh winhttp show proxy
# then, as the signed-in user and in a NORMAL window,
# open Internet Options and screenshot the LAN settings page:
control inetcpl.cpl
Is a proxy or VPN actually running? A VPN client, a security agent or a corporate filtering tool can install a proxy configuration you never typed. Turning it off temporarily is the single fastest test, and it is the first thing Microsoft's own moderator asked in that thread.
Did credentials change recently? A password change is the one trigger anybody in that thread names. If a saved credential no longer matches, a proxy that was happy yesterday will refuse today.
Does a browser work while the app does not? Useful, but read it carefully, because this is where most people draw the wrong conclusion. A working browser rules out a proxy that is broken or unreachable.
It does not rule out a proxy that wants credentials, for the reason Section 6 explains. Treat it as one signal, not a verdict.
If the checks come back clean and it is only Microsoft's applications failing, the pattern is worth naming properly, because it is not a OneDrive problem. If instead you need to change the address your machine presents, that is a different job covered in changing your IP address on Windows.
Outlook, Teams and OneDrive: One Error, Three Clients
Most pages on this topic file the error under OneDrive, because that is where the famous thread started. Several of the ranked ones do note that it also hits Outlook and Teams, and one names all three in its title. What none of them does is say why those three fail together, which is the part that tells you where to look.
| Where you see it | What it looks like | Fails with the others? |
|---|---|---|
| OneDrive | Sync will not start, or stops and will not resume | Yes, and usually at the same moment |
| Outlook | Sign-in fails, or a credential prompt that will not accept anything | Same pattern |
| Microsoft Teams | Reports you are disconnected while everything else is online | Same pattern |
| Your browser | Usually fine, which is what makes the error confusing | Different tolerance for failure |
That last row is the whole point, and it is why the browser test in Section 5 misleads people. A browser meeting a proxy that wants credentials shows you a login box and waits for you. A background sync client has nobody to ask, so it gives up and prints a number. Same network, same proxy, completely different experience, which is how you end up certain your connection is fine while three applications insist it is not.
I should be straight about the limit of this. Microsoft does not publish which proxy configuration the OneDrive, Outlook and Teams clients read, and I could not find it documented anywhere. That they fail together is observable; the shared source is my inference from that, and it is the reason the fixes that work on one tend to work on all three.
Browsers are not quite identical here either, and the reasons are in where Chrome's proxy settings really come from. But if all of Microsoft's clients fail together, suspect the store they share rather than any one of them.
When 2606 Is Telling the Truth
Sometimes there is no stale entry and nothing to clear. There is a proxy, it wants credentials, and it is refusing you correctly. Resetting your settings in that situation removes the only configuration that was working.
The underlying HTTP behavior is well defined even though Microsoft's number is not. MDN describes the relevant status code, 407, as indicating "that the request did not succeed because it lacks valid authentication credentials for the proxy server that sits between the client and the server with access to the requested resource", sent "with a Proxy-Authenticate header that contains information on how to correctly authenticate requests". A proxy is allowed to demand identification, and the client is expected to supply it.
I want to be precise about one thing here, because the internet is not. I could not find any source connecting Microsoft's 2606 to HTTP 407. The name of the error and the behavior line up, and that is all I can honestly say. I am describing what proxy authentication means, not asserting that this number is that status code.
| Signal | Points to a phantom proxy | Points to a real one |
|---|---|---|
| Who owns the machine | You bought it, nobody administers it | Issued by an employer or school, or enrolled |
| Colleagues on the same network | Working normally | Hitting the same wall |
| What the proxy fields contain | An address you do not recognize, or a broken one | Your organization's proxy, deliberately set |
| The right move | Clear it, having recorded it first | Ask for credentials. Do not reset anything |
There is a structural wrinkle worth knowing if you land in the right-hand column. Windows' own proxy screen has an address box and a port box and no place at all to put a username and password, so a proxy demanding credentials has to collect them some other way. If privacy rather than access is what brought you here, our browser leak test shows what a page can still read from you regardless of any of this.
Stopping It From Coming Back
If the error returns days later, something is putting the configuration back. That is not the same problem and it does not have the same answer.
On a managed device the usual culprit is policy re-applying a configuration you cleared, which buys you hours rather than a fix. The giveaway is the same either way: your change reverts on its own, without anybody touching the machine. A VPN client or security agent can do it too, whenever it starts.
The habit that shortens all of this: before you run anything, record each store. One screenshot of Internet Options and whatever netsh winhttp show advproxy prints back is enough, and it means you are never guessing about what was there before.
And if the failure turns out not to involve a proxy at all, the wider troubleshooting sequence is in our guide to fixing IP address not found errors, which covers the layer underneath this one.
The Short Version
Proxy authentication error 2606 means a Microsoft 365 client met something claiming to be a proxy and could not authenticate to it. Microsoft publishes no definition of the number, which is why every page on the subject offers steps rather than an explanation.
The fix that circulates resets Internet Explorer, and almost every page describing it says it clears your proxy settings. Microsoft's own documentation says the opposite: the reset "does not reset Connection settings as the settings can be used from other programs", and Microsoft publishes a separate article, using two registry commands, for the job everyone thinks the reset is doing.
What the reset clears instead is browser state, and Microsoft's two descriptions of it disagree on how much. It also "cannot be undone". So run the five-minute checks first: turn off any VPN or security agent, ask whether a password changed recently, and look at whether the failure is confined to Microsoft's clients.
If a proxy entry really is the problem, Microsoft's own two registry commands change that and nothing else. Add the quotes their article leaves out, because the key path has a space in it.
Whatever you change, confirm it from outside the machine rather than from a dialog box. Our IP trust score checker tells you how the address you are actually leaving from is classified, which answers the real question faster than any settings screen can.