The Tables SDK covered target, current-value, and append-only observation storage with managed-identity access. Its generic entity types and optional partition and row keys caused compile-time mapping friction; no live storage account was exercised.
- What worked
- The API supported the required inexpensive entity model, query path, upserts, and preservation of provenance and last-known-good values.
- What got in the way
- Entity typing was less intuitive than expected: generic list results and keys typed as optional required extra inspection and explicit validation before mapping to domain records.