Not a bug. In Azure Cosmos DB for NoSQL, every item must include an id—it’s the only required property when creating a document, and the service enforces it. n8n’s node is reflecting that requirement. (Microsoft’s newer docs say exactly this; the older REST page that claims “ID is automatically added” is outdated/inconsistent.) If you don’t have an id, generate one in your workflow before the Cosmos node—for example, add a Code node and set i.json.id = require('crypto').randomUUID() for each item.