Issue body:
I’m seeing a reproducible authentication inconsistency in Foundry Toolkit for VS Code.
Environment:
Extension: ms-windows-ai-studio.windows-ai-studio
Version: 1.6.3
OS: Windows
Subscription: GTLU - Dev-Test Sandbox
Project region: swedencentral
Problem:
The extension can display my Foundry project in the left navigation and I can see the project node and its sections. However, as soon as I click any child node under the project, such as Models, Tools, or other sub-sections, the extension immediately shows this error:
“You are not signed in to an Azure account. Please sign in.”
Why this looks like a bug:
I am signed in with the correct Microsoft account in VS Code.
The project is visible inside Foundry Toolkit, which suggests Azure access is at least partially working.
The issue happens only when opening child nodes under the project.
GitHub sign-in is unrelated here and does not fix the issue.
I already tried:
reloading the VS Code window
uninstalling and reinstalling the extension
signing out and signing back in
disconnecting GitHub/Copilot to rule out account confusion
Repro steps:
Open VS Code.
Sign in to Azure with the correct Microsoft account.
Open Foundry Toolkit.
Select the Foundry project.
Expand or click a child node such as Models or Tools.
Observe the error: “You are not signed in to an Azure account. Please sign in.”
Expected behavior:
If the project is visible and accessible in the extension, clicking child nodes should load their contents normally.
Actual behavior:
The project tree is visible, but clicking any child node fails with the Azure sign-in error.
Relevant log:
2026-07-08 18:37:55.803 [error] You are not signed in to an Azure account. Please sign in.
Additional context:
The logs also show the Foundry Toolkit runtime user agent as:
windows-ai-studio/1.6.3
This suggests the issue may be caused by a broken internal authentication path in the extension, where the project tree can load through one mechanism but child-node requests use another auth flow that is not picking up the active Azure session.
Issue body:
I’m seeing a reproducible authentication inconsistency in Foundry Toolkit for VS Code.
Environment:
Extension: ms-windows-ai-studio.windows-ai-studio
Version: 1.6.3
OS: Windows
Subscription: GTLU - Dev-Test Sandbox
Project region: swedencentral
Problem:
The extension can display my Foundry project in the left navigation and I can see the project node and its sections. However, as soon as I click any child node under the project, such as Models, Tools, or other sub-sections, the extension immediately shows this error:
“You are not signed in to an Azure account. Please sign in.”
Why this looks like a bug:
I am signed in with the correct Microsoft account in VS Code.
The project is visible inside Foundry Toolkit, which suggests Azure access is at least partially working.
The issue happens only when opening child nodes under the project.
GitHub sign-in is unrelated here and does not fix the issue.
I already tried:
reloading the VS Code window
uninstalling and reinstalling the extension
signing out and signing back in
disconnecting GitHub/Copilot to rule out account confusion
Repro steps:
Open VS Code.
Sign in to Azure with the correct Microsoft account.
Open Foundry Toolkit.
Select the Foundry project.
Expand or click a child node such as Models or Tools.
Observe the error: “You are not signed in to an Azure account. Please sign in.”
Expected behavior:
If the project is visible and accessible in the extension, clicking child nodes should load their contents normally.
Actual behavior:
The project tree is visible, but clicking any child node fails with the Azure sign-in error.
Relevant log:
2026-07-08 18:37:55.803 [error] You are not signed in to an Azure account. Please sign in.
Additional context:
The logs also show the Foundry Toolkit runtime user agent as:
windows-ai-studio/1.6.3
This suggests the issue may be caused by a broken internal authentication path in the extension, where the project tree can load through one mechanism but child-node requests use another auth flow that is not picking up the active Azure session.