Add AgenticIdentity API surface

[heyitsaamir]

Adds RequestOptions to all API methods that support agentic identity and/or service URL override:

• RequestOptions<K> type — Pick<{ agenticIdentity?, serviceUrl? }, K>
• agenticIdentityExtension(options) — converts options to HTTP config extensions
• resolveServiceUrl(defaultUrl, options) — per-call service URL override
• Updated API methods: activities (create, update, createTargeted, updateTargeted, delete, getMembers), members, meetings, reactions, teams
• Targeted methods accept RequestOptions<'serviceUrl'> only (no agenticIdentity)

[heyitsaamir]

This change is part of the following stack:

• DNP - Feature Branch ACF support #627
  • Add Agent 365 token support #628
    • Support Entra inbound Agent ID tokens #629
      • Add agentic auth provider infrastructure #630
        • Add AgenticIdentity API surface #631 ◀
          • Add agentic send helpers #632

_{Change managed by git-spice.}

[Copilot]

Pull request overview

Adds a standardized RequestOptions API surface across the Teams API clients so callers can (a) override serviceUrl per request and (b) pass an agenticIdentity that flows through to the auth provider interceptor via request extensions.

Changes:

• Introduces RequestOptions, plus helper utilities agenticIdentityExtension() and resolveServiceUrl().
• Updates multiple client methods (conversations/activities & members, meetings, reactions, teams) to accept optional RequestOptions and thread them into HTTP calls.
• Updates and extends unit tests to validate option passing (service URL override + agentic identity extensions).

Reviewed changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
packages/apps/src/activity-sender.spec.ts	Updates expectations to account for the extra (empty) request config object passed through the API client calls.
packages/api/src/clients/team.ts	Adds RequestOptions support for team reads and serviceUrl override resolution.
packages/api/src/clients/team.spec.ts	Updates tests and adds coverage for serviceUrl override + agentic identity extensions.
packages/api/src/clients/request-options.ts	New shared request options types/helpers (agentic identity extensions + serviceUrl resolution).
packages/api/src/clients/reaction/reaction.ts	Adds RequestOptions support and forwards agentic identity extensions and serviceUrl override.
packages/api/src/clients/reaction/reaction.spec.ts	Updates tests and adds coverage for serviceUrl override + agentic identity extensions.
packages/api/src/clients/meeting.ts	Adds RequestOptions support for meeting APIs and forwards agentic identity extensions and serviceUrl override.
packages/api/src/clients/meeting.spec.ts	Updates tests and adds coverage for serviceUrl override + agentic identity extensions.
packages/api/src/clients/index.ts	Exports the new request-options surface from the clients barrel.
packages/api/src/clients/conversation/members.spec.ts	Updates conversation member client tests to include the new request config argument.
packages/api/src/clients/conversation/member.ts	Adds RequestOptions support for conversation member APIs and threads options into HTTP calls.
packages/api/src/clients/conversation/index.ts	Extends conversation client sub-APIs to accept RequestOptions in their method signatures.
packages/api/src/clients/conversation/activity.ts	Adds RequestOptions support for activity APIs, including serviceUrl override resolution and agentic identity extensions (non-targeted).
packages/api/src/clients/conversation/activity.spec.ts	Updates tests and adds coverage for serviceUrl override + agentic identity extensions.
packages/api/src/clients/auth.ts	Re-exports AGENTIC_IDENTITY_EXTENSION to make it part of the auth surface.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 14 out of 14 changed files in this pull request and generated 3 comments.

[corinagum]

in PY, create_targeted accepts agentic_identity. Is this difference intentional?

[heyitsaamir]

Hm, it doesn't -- https://github.com/microsoft/teams.py/pull/464/changes#diff-760256f62e295bca9c2b2149244c9d0901092a2ef286d026dcb9e4e91e8bf9bfR176

[corinagum]

Encoding path params seems correct, but Teams conversation IDs contain : / @ / ; , so this changes the bytes we send to the connector. Could you confirm the connector accepts %3A / %40 -encoded IDs, (b) apply it consistently, and (c) mirror it in Python?

Targeted methods drop agenticIdentity but Python keeps it. The description says targeted methods are RequestOptions<'serviceUrl'> by design, but Python's create_targeted/update_targeted/delete_targeted do accept agentic_identity and attach the extension. Is the TS asymmetry intentional? If so a one-line note on why would help; if not, we have a cross-SDK gap.

[heyitsaamir]

Encoding path params seems correct, but Teams conversation IDs contain : / @ / ; , so this changes the bytes we send to the connector. Could you confirm the connector accepts %3A / %40 -encoded IDs, (b) apply it consistently, and (c) mirror it in Python?

Targeted methods drop agenticIdentity but Python keeps it. The description says targeted methods are RequestOptions<'serviceUrl'> by design, but Python's create_targeted/update_targeted/delete_targeted do accept agentic_identity and attach the extension. Is the TS asymmetry intentional? If so a one-line note on why would help; if not, we have a cross-SDK gap.

I'm removing the encoding logic. It seems like something we can pick up separately (if needed).
Python actually doesn't keep agentic ids in its targeted-message functions, so I think we should be okay here?