Hi Jose,
Thank you for contacting Q&A Forum. I would like to provide my findings and proposed solution:
This kind of problem can happen in Azure Functions due to changes in the underlying environment, even if you haven't redeployed.Azure Functions (especially on the Consumption Plan) can auto-clean or update the environment, which might remove or invalidate dependencies that were previously cached. If the dependency isn’t explicitly listed in your requirements.txt, it might have been available in the environment before but is now missing. Your local environment might be using a different Python version than the one configured in Azure (e.g., Python 3.10 locally vs. 3.9 in Azure).If you're using zip deployment or GitHub Actions, the venv folder might be excluded, and Azure is expected to install dependencies from requirements.txt.Try deploying to a new Function App to see if the issue persists. This can help isolate whether the problem is with the app or the environment.
Kindly let me know if this work for you and please let me know if you have any further question.
Best regards