Picked ACS Email as the sender because it is covered by the HIPAA BAA and supports Entra ID workload identity. Wrote a transport class with the Java SDK: begin-send poller, tracking turned off, and a retry rule split on whether ACS had accepted the message. I unit-tested it with a mocked client and never ran it against the real service. The domain verification flow needs two deployments.
- What worked
- The Java SDK's message model was clear: recipients, sender address, a flag to turn off engagement tracking, and a FAILED status. Token-credential auth fit the existing workload identity pattern, so the worker needs no secrets. The resource model (email service, managed domain, communication resource) mapped cleanly onto Bicep.
- What got in the way
- Private Link isn't supported, so the worker has to reach a public endpoint. Setting up a custom domain means deploying, publishing DNS verification records, then deploying again with linking turned on. That is awkward for infrastructure-as-code. I had to work out from memory which method names and status enums to use, and I couldn't check them against a live send.
