Extension with Azure provider is still trying to send data to ChatGPT
Resolved 💬 8 comments Opened Oct 13, 2025 by heyarny Closed Oct 22, 2025
💡 Likely answer: A maintainer (gpeal, contributor)
responded on this thread — see the highlighted reply below.
What version of the VS Code extension are you using?
0.4.19
Which IDE are you using?
VS Code
What platform is your computer?
Darwin 25.0.0 arm64 arm
What steps can reproduce the bug?
At our company the security policy does not allow to use chatgpt, but we are allowed to use openai via azure.
Thats why our proxy do block ChatGPT.
With some workarounds we use the VS Extension with Azure as provider, but the extension is still trying to send data to ChatGPT.
You can clearly see the output inside VS Code > Output Window > Codex:
2025-10-13 13:00:51.846 [error] Error fetching https://ab.chatgpt.com/v1/rgstr?k=client-xxxx&st=javascript-client-react&sv=3.25.5&t=1760353251613&sid=xxxxx&ec=1002: 403 Forbidden (null)
What is the expected behavior?
Do not send anything to chatgpt when using azure as provider.
What do you see instead?
Fetching ... chatgpt...
Additional information
_No response_
8 Comments
Same here, cannot use Azure with extension, despite the same
config.tomlworks on Azure for CLI too.@heyarny how did you manage to use Azure provider with VS Code extension?
@pai4451
As of now, I'm using gpt-5.
this is my
config.toml:auth.jsonIt seems that the
CodexStatsigProviderreact component of the Webview sends that. Once removed from the UI, it doesn't send logs. The Codex Webview is not published to create a pull request, is it? I can't find an oss license for it, either ;-(. Maybe logging could optionally be disabled there.Those requests are independent of the model you select. You may configure your network proxy to provide additional guarantees though.
@gpeal ok, they are independent, does it still make sense to have them when using azure provider?
Why is there no option to disable them? Whats the point of still having them, other than stressing our proxy?
Yes, there may be other issues such as features that never get turned on or other configurations that aren't set correctly.
So why is this issue closed then? How did you solve the issue?
This is a real issue in big companies, when they see codex sending something somewhere without respecting the security regulations.
Here's a recording.
https://github.com/user-attachments/assets/423a3b3a-c523-4dd6-8fce-c9e1fb93bbf9