microsoft / microsoft/vscode-azureresourcegroups

No explanation shown in chat view on first run of "Ask Copilot about the Azure Activity Log" command

Open
#1,166 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

AT-CTI
Dominant language
TypeScript
Stars
78
Forks
55
Avg merge
16h 49m
Merged PRs (30d)
139

Description

OS: Win 11 ARM64
Build Version: 20250621.1
Regression: Not a regression

Repro Steps:

  1. Make sure no “github.copilot” & "github.copilot-chat” extensions installed.
  2. Create a container apps environment.
  3. Click "Ask Copilot about the Azure Activity Log" icon in Azure activity window.
  4. Check whether there is explanation for the activity log in the opened chat view.

Expect:
There is explanation for the activity log in the opened chat view.
Image

Actual:
There is no explanation for the activity log in the opened chat view.
Image

More Info:
This issue only reproduces when executing "Ask Copilot about the Azure Activity Log" command the first time.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the first execution of the “Ask Copilot about the Azure Activity Log” command with the extensions absent, then trace the command's chat-view initialization. Compare the first-run view with later executions; done means the opened chat view includes the activity-log explanation on the first execution.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript, vscode
Domain
cloud, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.