Skip to content

Update configuration comments: Azure Bot → Agent Blueprint#153

Merged
pontemonti merged 2 commits into
mainfrom
copilot/fix-appsettings-azure-bot-reference
Jan 22, 2026
Merged

Update configuration comments: Azure Bot → Agent Blueprint#153
pontemonti merged 2 commits into
mainfrom
copilot/fix-appsettings-azure-bot-reference

Conversation

Copilot AI commented Jan 13, 2026

Copy link
Copy Markdown
Contributor

Configuration comments referenced "Azure Bot" where users actually provide Agent Blueprint IDs from the a365 CLI, causing confusion about required services.

Changes

  • appsettings.json: Updated ClientId comments in TokenValidation.Audiences and Connections.ServiceConnection.Settings
  • AspNetExtensions.cs: Updated documentation example and TokenValidationOptions.TenantId summary

Before/After

// Before
"ClientId": "", // this is the Client ID used for the Azure Bot

// After  
"ClientId": "", // this is the Client ID used for the Agent Blueprint

Users configure their agent blueprint credentials, not Azure Bot Service. The underlying token validation infrastructure may use Azure Bot Service, but that's an implementation detail not relevant to configuration.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • learn.microsoft.com
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Original prompt

This section details on the original issue you should resolve

<issue_title>appsettings.json references Azure Bot instead of Agent Blueprint</issue_title>
<issue_description>Describe the bug
The terminology used in the sample dotnet semantic kernel agent references Azure Bot for authentication configuration. This can be misleading as it may lead users to beleive they need Azure Bot service for their setup, but absed on the docs at https://learn.microsoft.com/en-us/microsoft-agent-365/developer/testing?tabs=dotnet, this should actually represent the agent blueprint id created with the agent365 CLI.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'dotnet/semantic-kernel/sample-agent/appsettings.json'
  2. See "Azure Bot" referenced in the comment in the TokenValidation and Connections sections

Screenshots
Image

Environment (please complete the following information):

  • OS: Windows
  • SDK Version: n/a
    </issue_description>

<agent_instructions>Please fix the comments mentioning Azure Bot, so suers know this is related to the agent blueprint. See https://learn.microsoft.com/en-us/microsoft-agent-365/developer/testing?tabs=dotnet for more details</agent_instructions>

Comments on the Issue (you are @copilot in this section)


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

…nces to Agent Blueprint

Co-authored-by: danevora <43191483+danevora@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix appsettings.json to reference agent blueprint instead of Azure Bot Update configuration comments: Azure Bot → Agent Blueprint Jan 13, 2026
Copilot AI requested a review from danevora January 13, 2026 16:45
@pontemonti pontemonti marked this pull request as ready for review January 21, 2026 18:50
@pontemonti pontemonti requested a review from a team as a code owner January 21, 2026 18:50
Copilot AI review requested due to automatic review settings January 21, 2026 18:50
@pontemonti pontemonti enabled auto-merge (squash) January 21, 2026 18:50

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request updates configuration comments to replace "Azure Bot" references with "Agent Blueprint" where users configure their agent credentials. This improves clarity by aligning the documentation with the a365 CLI workflow, where users create and configure Agent Blueprints rather than Azure Bot Service resources directly.

Changes:

  • Updated ClientId configuration comments in appsettings.json to reference "Agent Blueprint" instead of "Azure Bot"
  • Updated corresponding XML documentation in AspNetExtensions.cs to maintain consistency

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
dotnet/semantic-kernel/sample-agent/appsettings.json Updated ClientId comments in TokenValidation.Audiences and Connections.ServiceConnection.Settings sections to reference Agent Blueprint
dotnet/semantic-kernel/sample-agent/AspNetExtensions.cs Updated XML documentation example and TenantId summary to reference Agent Blueprint for consistency

@pontemonti pontemonti merged commit d3b9ad0 into main Jan 22, 2026
13 checks passed
@pontemonti pontemonti deleted the copilot/fix-appsettings-azure-bot-reference branch January 22, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

appsettings.json references Azure Bot instead of Agent Blueprint

5 participants