@Mason-1850 Thanks for reaching here!
It's possible that the issue is related to the Cosmos DB account key or connection string being stored as an App Setting. You may try below few things.
- Verify the Connection attribute and that it references a setting that exists in your Azure function app. The value on this attribute shouldn't be the connection string itself, but the name of the configuration setting.
- Verify that the databaseName and containerName values exist in your Azure Cosmos DB account. If you're using automatic value replacement (using %settingName% patterns), make sure that the name of the setting exists in your Azure function app.
- Confirm your Azure Cosmos DB account's firewall configuration to ensure that it's not blocking the Azure function.
- Also, Azure Functions trigger and bindings for Azure Cosmos DB depend on the extension package Microsoft.Azure.WebJobs.Extensions.CosmosDB over the base Azure Functions runtime. Always keep these packages updated, because they include fixes and new features that can help you address any potential issues you might encounter.
- Note that the Azure Functions trigger uses latest version change feed mode. Currently, the Azure Functions trigger for Azure Cosmos DB is supported for use with the API for NoSQL only.
Let us know.