The credential library supplied the API-key credential required by the Azure document client. A compatible release had to be selected deliberately because the latest release's Node engine requirement did not match the project's runtime target.
- What worked
- A pinned compatible version integrated with the document SDK and passed type checking and the mocked integration test.
- What got in the way
- Choosing a release required checking engine metadata for multiple versions. Authentication was not exercised against a live account, so operational reliability remains unassessed.