ai-agents-project66027542
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 12/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- azure, javascript, vscode
Research direction
The failure is reported from ModelDeployWebview.deployModel, but the call stack only points into minified extension.js, so start by finding that function in the source tree. The error is an Azure policy rejection of the gpt-5 resource, so the code change is unclear and may belong in deployment handling or in user configuration rather than the extension. The issue does not say what done looks like, so confirm the expected behaviour with a maintainer before writing code.
Written by the indexing model from the issue text.
Description
Does this occur consistently?
Repro steps:
Action: ModelDeployWebview.deployModel
Error type: RequestDisallowedByPolicy
Error Message: Resource 'gpt-5' was disallowed by policy. Policy identifiers: '[{"policyAssignment":{"name":"AI-3026-Lab01 - 66027542","id":"/subscriptions/36483c3d-b51d-4b62-98df-a09bdf830930/providers/Microsoft.Authorization/policyAssignments/AI-3026-Lab01 - 66027542"},"policyDefinition":{"name":"AI-3026-Lab01 - 66027542","id":"/subscriptions/36483c3d-b51d-4b62-98df-a09bdf830930/providers/Microsoft.Authorization/policyDefinitions/AI-3026-Lab01 - 66027542","version":"1.0.0"}}]'.
Version: 1.6.15
OS: win32
OS Arch: x64
OS Release: 10.0.26200
Product: Visual Studio Code
Product Version: 1.138.0
Language: en
UTC time: Fri, 09 Oct 2026 05:02:35 GMT
Call Stack
a extension.js:5718:1236329
l extension.js:5718:1235228
- Dominant language
- JavaScript
- Stars
- 2.1k
- Forks
- 260
- Avg merge
- 11h 16m
- Merged PRs (30d)
- 32
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/foundry-dev-tools
-
needs attention
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/foundry-dev-tools#854 · 1 comment ·
Maintainers usually reply within 1 day
-
issueOpenneeds attention
Difficulty 3/5 Half a day Newbie friendliness 35/100
microsoft/foundry-dev-tools#853 · 1 comment ·
Maintainers usually reply within 1 day
-
foundrytoolOpenneeds attention
Difficulty 5/5 Over a week Newbie friendliness 10/100
microsoft/foundry-dev-tools#852 · 1 comment ·
Maintainers usually reply within 1 day
-
needs attention
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/foundry-dev-tools#850 · 1 comment ·
Maintainers usually reply within 1 day
-
needs attention
Difficulty 3/5 1-2 days Newbie friendliness 38/100
microsoft/foundry-dev-tools#849 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoft/foundry-dev-tools
Similar issues
-
channels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 9 days
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4496 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
swc-project/swc#12516 ·
Maintainers usually reply within 1 day
-
Opening Files on a demo drive logs you outPossibly taken @RChang06 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
omegaup/omegaup#10323 · 1 comment ·
Maintainers usually reply within 5 days