This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 90%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJT%3C/text%3E%3C/svg%3E)
I have a function deployed in a functionapp that accesses a cosmosdb to write some data. My function works locally but when I deploy to Azure I keep getting an error that states:
No connection adapters were found for <DB_URI>
I'm using python and am creating the CosmosClient using the DB_URI and the Account_Primary_Key which I'm fetching from a key vault.
For some reason it works when I run locally passing the same parameters through env variables via local.settings.json but throws this error when pushed to the cloud.
Anyone have any pointers? The FunctionApp has rights to read the key vault as well as db contributor role access. The error message isn't helping me find the root cause.
Thanks,
Jason
@Jason Taylor Can you please confirm if your DB_URI has https:// as this could cause the error : No connection adapters were found for <DB_URI>
I do have https:// as a prefix... but I noticed I had :443 at the end of it. Removing that seemed to solve the problem. Now the question is why would having the port number included in the URI work when I am testing locally but not work once published into Azure?
@Jason Taylor The only reason I could think would be SDK code and the versions installed both locally and on azure function. I am not sure if you have done a remote build that could have got a different version that could be the region of this behavior from the Cosmo DB SDK end.