Skip to contentIf you are trying to figure out how to set up a proxy in Microsoft Excel, the first surprise is simple: Excel usually does not offer a neat little proxy switch of its own. Most of the time, the real path is Windows, Microsoft 365 sign-in, or a browser-backed feature inside Excel that follows the system network settings. That means the answer is less about one Excel menu and more about where Excel gets its network rules.
There is a difference between a workbook opening on your desktop and a workbook pulling data from the cloud. One can work fine while the other fails. That split matters.
For many users, the right Excel proxy setup is really the Windows proxy configuration that Excel inherits automatically. For others, especially people using Excel for the web or Microsoft 365-connected features, the browser and account layer matters just as much. A proxy can affect sign-in, licensing, add-ins, and file sync without touching the spreadsheet grid at all.
What “proxy in Excel” actually means
Excel on Windows does not behave like a separate browser with its own proxy box. If you open a local .xlsx file, the proxy may not matter at all. If you open a file from OneDrive, refresh Power Query data, or use an add-in that talks to a web service, the network path can run through Windows proxy settings, Office identity components, or browser services behind the scenes. That is why two people can have the same Excel version and still get different results.
Think of the workbook as only part of the story. The other part is the network call Excel makes when it signs in, checks your subscription, loads an add-in, or reaches SharePoint. If that call is blocked, Excel may open but complain later, which is annoying because the spreadsheet itself looks healthy.
Desktop Excel, Excel for the web, and Microsoft 365 sign-in each behave a little differently. Desktop Excel often inherits from the operating system. Excel for the web depends on the browser and your corporate network. Microsoft 365 authentication may use system proxy rules plus whatever your organization has set for identity traffic.
When you need Excel-specific proxy setup vs. a system proxy
If you are on Excel for Windows and your goal is simply to let the app reach the internet through a company proxy, start with the system proxy first. That is the common path for desktop users and the one most IT teams expect. If your company uses a PAC file or authenticated proxy, Excel is usually not the place to enter those details manually. Windows or enterprise policy does that job.
Excel for the web is different. It runs in a browser, so the browser and OS proxy behavior are part of the result. If the browser can reach Microsoft services and the account can sign in, the web app often behaves. If the browser is blocked, Excel for the web will fail in the same way a normal website would.
There is also the Microsoft 365 sign-in layer. A proxy can interfere with license checks, connected templates, cloud file access, and add-ins that need authentication. If Excel starts, but your workbook from SharePoint never opens, the proxy issue may sit outside the workbook itself.
One useful reference here is the SOCKS5 proxy vs HTTP proxy article, because the protocol choice can matter when you are comparing what your network team gave you against what Office services can actually use. A mismatch between proxy type and client behavior is a common dead end.
Check the proxy details and network conditions before changing anything
Before you touch Windows settings, collect the proxy host, port, and authentication method. If your network uses a PAC URL, write that down exactly. If the proxy needs a username and password, get the format from IT before you start guessing. Guessing usually costs more time than asking once.
You should also ask whether SSL inspection is involved and whether custom certificates are installed. That detail matters because Excel may connect to Microsoft services over HTTPS, and a proxy that rewrites certificates can trigger sign-in errors, trust warnings, or failed workbook refreshes. If your company uses a managed device, this is often decided by policy, not by the user.
If you need background on authentication formats, the proxy authentication best practices guide is a good companion read. It helps when the problem is not the proxy address, but the login method the proxy expects.
Keep one more fact in view: some organizations route Microsoft 365 traffic differently from general web traffic. That means a proxy can allow ordinary websites while still breaking Excel sign-in or cloud files. Small difference. Big headache.
Set the proxy at the Windows level so Excel can inherit it
This is the path most desktop users need. If Excel is on Windows, the operating system proxy settings often decide what Excel can reach. Here is the usual sequence.
- Open Windows Settings.
- Go to Network and Internet.
- Select Proxy.
- Choose either automatic setup or manual setup, depending on what your IT team provided.
- If you have a PAC address, enter the script URL in the automatic setup field.
- If you have a fixed proxy host and port, enter them in the manual proxy section.
- Save the changes.
If Windows asks for credentials when you browse or open a cloud file, enter the username and password your organization issued. Do not invent a local account format unless IT told you to. Some environments accept the Windows logon automatically; others need explicit proxy authentication. That difference decides whether Excel can reach the network or sits there waiting forever.
After you save the Windows proxy settings, close Excel completely and open it again. A restart matters. Excel can keep an old network session alive for longer than expected, and that stale session may hide the effect of the new proxy. Two minutes now can save twenty later.
If you also want to understand how proxy structure affects the broader client setup, see the article on proxy port numbers for web scraping. The context is different, but the port logic is the same: the wrong port means no traffic at all.
Use proxy with Excel sign-in, activation, and Microsoft 365-connected features
Once Excel is open, the proxy may still get in the way of sign-in. That happens most often with Microsoft 365 licensing, OneDrive files, SharePoint links, Teams-linked add-ins, or accounts that need a web authentication page. You can have a working workbook and a broken account session at the same time. That is not rare.
If Excel launches but keeps asking you to sign in again, test the account in a browser first. If the browser cannot complete the Microsoft login through the proxy, Excel will usually not do better. In that case, the issue is not the spreadsheet. It is the path to Microsoft identity services.
Sometimes the fix is as small as allowing the right Microsoft endpoints through the proxy. Sometimes it is larger, because the proxy blocks modern auth redirects, device registration, or token refresh calls. That is why “Excel is open” does not mean “Excel is fully working.” It means only that the app window loaded.
When you need to use proxy with Excel in a managed office, the network team may also need to permit add-in endpoints, SharePoint, and the Office licensing service. If you are comparing proxy types and sign-in behavior, the article on authenticated SOCKS5 proxy can help you understand why some client software tolerates one setup and rejects another.
Test whether Excel is actually using the proxy
Do not assume success from the splash screen. Test something that requires the network. Open a workbook from OneDrive or SharePoint. Refresh a data connection. Sign out and sign back in. Then watch what happens. If those three steps work, you are much closer to a real proxy setup than if Excel merely starts without errors.
You can also check whether Excel can refresh an external data source that depends on the internet. If the refresh hangs, fails with authentication errors, or returns stale data, the proxy may still be blocking one part of the request path. Some connections call one domain for data and another for authentication. One passes, the other fails.
Try a simple cloud file test first. Open a document stored in OneDrive, make a visible change, save it, and confirm that it syncs back. That gives you a direct signal that Excel is reaching the cloud through the proxy. It is a small test, but small tests expose large problems quickly.
If you need a broader framework for network access testing, the article on how to hide your IP address is useful because it explains why the network path matters even when an app appears local. Excel is local on your desktop, but its cloud features are not.
Troubleshoot common Excel proxy setup problems
Sign-in loops are one of the most common failures. Excel opens, you enter credentials, and then the prompt comes back. In that case, clear the saved Office credentials, check the proxy authentication method, and test the browser login separately. If the browser fails too, the proxy is the likely culprit.
Another frequent issue is cloud files that will not open. If local files work but OneDrive or SharePoint files do not, the proxy may be blocking the account service or the document service. That distinction matters. You are not fixing “Excel” in the abstract. You are fixing one network path.
Add-ins failing to load are another clue. Many add-ins use web requests, and a proxy can block their scripts or endpoints. If an add-in says it cannot connect, inspect whether the company proxy allows the add-in domain, not just Microsoft’s main login pages. One missing domain is enough to break the whole feature.
If Excel seems to ignore the proxy entirely, check whether another tool or policy is overriding Windows settings. Group Policy, enterprise security software, VPN clients, and even browser-specific proxy rules can take precedence. That means the setting you changed may be correct and still not be the one Excel uses.
A useful side check is to compare Excel behavior with the browser on the same machine. If both fail in the same way, the network path is wrong. If only Excel fails, the issue may sit in Office sign-in, cached credentials, or a specific Office policy. That one detail saves a lot of false troubleshooting.
When to involve IT or switch to a different proxy approach
If the proxy is controlled by policy, you may not be able to finish the setup yourself. Managed devices often ignore local edits, and some enterprise networks require an approved PAC file, firewall exception, or identity-aware gateway before Excel can reach cloud services. At that point, the fix is not another click in Excel. It is a network change.
Bring IT the exact symptom, the exact URL or feature that fails, and the proxy details you collected earlier. “Excel does not work” is too broad. “Excel opens local files but fails to sign in to OneDrive through a PAC-based proxy” is useful. Specifics shorten the back-and-forth.
If your organization wants a consistent use proxy with Excel setup across dozens or hundreds of machines, ask whether the configuration should be pushed through policy rather than left to each user. That is often the cleaner path for Windows desktops, especially where Microsoft 365, add-ins, and cloud storage all need the same network rules. Human hands are fine for one laptop. They are a poor rollout plan for fifty.
And if the network team is still deciding between routes, name the exact Microsoft services involved, the proxy type, and whether authentication is required. Those three details usually decide whether Excel behaves or stalls on the first cloud call.