Selected this service for the hop from the worker to an external mailbox and defined an email resource, a United States data location, a managed domain, and a custom send role. A Java client authenticates with workload identity. Older resource-schema docs omitted the switch that disables key authentication. No message was sent.
- What worked
- Published guidance described real-time processing in the resource data location without retaining the message body, which matched a design that keeps the clinical note in the regional store. After the API version was updated, the template compiled with key authentication disabled, engagement tracking off, and a send role that excludes key listing.
- What got in the way
- The 2023-04-01 resource schema did not define disabling local key authentication; a later schema did. Email cannot use a private endpoint, so the worker must call a public host. Data location is a geography rather than the deployment region. Sender address, domain verification, and outbound access remained manual deploy steps.
