Skip to content

[PA bug fix] use incomming activity's serviceUrl if not set in outgoing activity.#374

Merged
singhk97 merged 7 commits intonext/corefrom
next/core-conversation-fix
Mar 18, 2026
Merged

[PA bug fix] use incomming activity's serviceUrl if not set in outgoing activity.#374
singhk97 merged 7 commits intonext/corefrom
next/core-conversation-fix

Conversation

@singhk97
Copy link
Copy Markdown
Collaborator

  1. Refactor PA bot - remove multi-host setup, support two identities simulatneously (bot & agent)
  2. [PA bug fix] In Microsoft.Teams.Bot.Compat, If serviceUrl is not set in outgoing activity then use the one from the incomming activity as fallback
  3. Make ConversationAccount.GetAgentIdentity() public. It's being used in the compat adapter.

@singhk97 singhk97 changed the title fix missing service url error [PA bug fix] use incomming activity's serviceUrl if not set in outgoing activity. Mar 16, 2026
@singhk97 singhk97 added the CORE label Mar 16, 2026
singhk97 and others added 6 commits March 17, 2026 09:46
Fixed two instances where AddBotAuthentication overloads were called with
parameters in the wrong order:
- Line 39: The sectionName-based overload was passing parameters as
  (schemeName, clientId, tenantId, logger) instead of the correct
  (clientId, tenantId, schemeName, logger)
- Line 59: The IServiceCollection overload had the same parameter ordering issue

This ensures that clientId, tenantId, and schemeName are passed to the correct
parameter positions, preventing authentication configuration errors.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@singhk97 singhk97 merged commit fb238fd into next/core Mar 18, 2026
6 checks passed
@singhk97 singhk97 deleted the next/core-conversation-fix branch March 18, 2026 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants