Implementation Guide | Healthcare

    Passing Clinician Identity Through Copilot Studio Agents for HIPAA Access Control

    Carry the authenticated clinician's identity and role from the agent session to every downstream tool call, using delegated user credentials or token exchange rather than a shared service account or maker credential. Then decide access per request at the downstream system and at a runtime enforcement point, and record each decision against a unique individual. This supports the access control, audit control and authentication standards in 45 CFR 164.312 (as of November 2026).

    Where identity is typically lost

    1. 1

      Session authentication

      If the agent can be used without authenticating the clinician, or authenticates only at a coarse level, no identity exists to propagate. Verification under 164.312(d) starts here.

    2. 2

      Topics and generative orchestration

      Orchestration decides which tool to call and with what inputs. Identity and role must travel as call context, not as free text in a prompt that the model can alter.

    3. 3

      Connectors and actions

      A connection created once with shared or maker credentials silently replaces the user for every later call. Inventory each connection and the identity it uses.

    4. 4

      Custom API or MCP tool

      A tool endpoint that accepts the agent's call but then uses its own backend credential discards the clinician at the last hop that still knows who they are.

    5. 5

      Downstream EHR or FHIR service

      The service can only authorize and log what it receives. If it receives an application identity, its own audit trail attributes access to the application.

    Evidence to produce for each PHI request and tool call

    • Authenticated clinician identifier and how the session was verified
    • Role or workforce class evaluated at decision time
    • Tool or service called and the identity presented downstream
    • Category of PHI requested or returned
    • Decision taken (allow, redact or block) and the policy that produced it
    • Time of the request and any emergency access designation

    Why identity propagation is an architecture problem

    When a Copilot Studio agent retrieves or acts on PHI through connectors, custom APIs or other tools, the downstream system sees whichever identity the call runs under. If that identity is a shared service account or the agent maker's credential, the link between the clinician who asked and the data returned is gone at the point where it matters most.

    The HIPAA Security Rule is written around individuals. The access control standard in 164.312(a)(1) requires technical policies that allow access only to persons or software programs that have been granted access rights under 164.308(a)(4). Unique user identification, a Required specification, calls for a unique name or number to identify and track user identity. Audit controls in 164.312(b), also Required, call for mechanisms that record and examine activity in systems that contain or use ePHI. Person or entity authentication in 164.312(d) requires procedures to verify that the person seeking access is the one claimed.

    Per-clinician attribution of a PHI request touches all three standards: the identifier, the recorded activity and the verification of the claimed identity. A shared or maker identity at a downstream call is a design risk for individual attribution. Whether a given design meets the standard is a compliance determination for your counsel, but the architectural direction is clear.

    Credential modes compared by what the downstream system sees

    Whatever options a platform exposes, classify each by one question: which identity does the downstream service receive? The table groups the common patterns by that outcome. Confirm exact configuration names and behavior against current Microsoft documentation for your tenant.

    • End-user delegated credential: The clinician authenticates and the call carries a token issued for that user. The downstream service sees the individual. This is the most direct way to preserve identity, but it depends on every tool supporting user-delegated access.
    • Token exchange on behalf of the user: The agent exchanges the clinician's session token for a new token scoped to a downstream API, so the API still sees the user. It suits custom APIs and services that must be reached with their own audience and scopes. The exchange itself becomes a trust boundary to configure and evidence.
    • Shared service account: All calls run under one application identity. The downstream service sees the agent, not the clinician. Per-individual access decisions and attribution are not possible at that service unless identity is passed and enforced elsewhere.
    • Maker credential: Calls run under the credential of the person who built the agent or connection. Every clinician inherits the maker's access. This is the weakest pattern for role-based limits and attribution.

    Native authorization and runtime enforcement are separate layers

    Native authorization at the downstream system answers whether this identity may access this resource. It is necessary, and it is only as precise as the identity it receives. Runtime enforcement in the execution path answers a different question for each interaction and tool call: given who is asking, their role and the PHI involved, should this request or response be allowed, redacted or blocked?

    The 164.514 text contemplates identifying the classes of workforce who need PHI, the categories of PHI they need and any conditions on access, then making reasonable efforts to limit access accordingly. An enforcement point therefore needs more than a unique identifier. It needs the clinician's role or workforce class, and often context such as care-team relationship or purpose of use. Define the mapping from role or class to PHI category as a documented policy first, because a decision point can only evaluate policy that exists.

    Also define how emergency access, a Required specification, behaves for agent-mediated requests and how it is recorded. Treat the Addressable items, access authorization and access establishment and modification under 164.308(a)(4), as documented implementation decisions. Finally, each hop between agent, connector and downstream service is a network transmission of ePHI, so transmission security under 164.312(e)(1) applies to the whole chain.

    Where Trussed fits

    Trussed is the control, provenance and evidence infrastructure for consequential AI. It enforces policy in the execution path across models, agents, tools and MCP servers, so decisions are enforced at runtime, not reviewed after the fact. For a clinician-facing agent, that means a PHI-bearing interaction or tool call can be allowed, redacted or blocked based on clinician identity and role once that context reaches the enforcement point.

    Each enforcement decision produces audit-ready evidence, mapped to HIPAA including the 164.312(b) audit controls standard. Scope is individual interactions and tool calls. Trussed deploys self-managed in the customer cloud, with configurable retention and data residency, and runs in production with healthcare organizations in a regulated enterprise setting.

    It complements native authorization and correct identity propagation. It does not replace them, and it does not make a design compliant on its own.

    Identity chain for one PHI request

    Authenticate

    The clinician signs in and the session carries a verified identity.

    Propagate

    Each tool call presents the clinician's delegated identity, not a shared one.

    Enforce

    Access is decided per request using identity and role.

    Evidence

    Each decision is recorded against a unique individual.

    Review your agent identity chain

    Walk through your Copilot Studio tool calls with an expert and see how enforcement and evidence apply to each PHI request.

    Explore Agent and Tool-Call Enforcement
    Next step

    How does your AI governance program compare?

    See where your program has gaps in less than 2 minutes.