Cosmos DB trigger is not working properly after migrating to isolated process model

lakshmi 631 Reputation points

Hi Team,

We have migrated our Azure Function to the isolated worker model and made the necessary changes.

Previously, the Cosmos DB trigger worked by triggering when a new entity was added or removed in a specific table. Now, the trigger is still being hit, but not all values, such as email and locale, etag are being set in the entities.

Can anyone help with this

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,496 questions
{count} votes