I would expect this behavior if the environment variables are not set in Azure. If they are not defined, the CosmosClient created at module-load time throws immediately, so the function is not registered.
Could you double check if the environment variables are set in Azure? You can find them in the portal under Settings -> Environment variables.