You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a regression in newer releases of mcr.microsoft.com/azure-functions/python:4-python3.8-slim when connecting to an Azure SQL database when using User Managed Identity as authenication (the problem doesn't happen for Service Principal).
When the following python script runs on an docker image based on this older image it works fine mcr.microsoft.com/azure-functions/python:4-python3.8-slim@sha256:691c02f8c5d40e8ee93f9d9af1ec4d815d524d8a6d11b473a819e5f3dbba7601
If I run in an image based on this newer image: mcr.microsoft.com/azure-functions/python:4-python3.8-slim@sha256:74f2a9774e5b7f65965846cfd4b195177def72f283f4736760c1e43c12f66c0f I get Login timeout expired (0)
@kshyju Sorry for tag but I'm unsure if the issue is picked up directly here, or need to be reported via other channels as it seems to be the case for some Azure products :-)
There is a regression in newer releases of
mcr.microsoft.com/azure-functions/python:4-python3.8-slim
when connecting to an Azure SQL database when using User Managed Identity as authenication (the problem doesn't happen for Service Principal).When the following python script runs on an docker image based on this older image it works fine
mcr.microsoft.com/azure-functions/python:4-python3.8-slim@sha256:691c02f8c5d40e8ee93f9d9af1ec4d815d524d8a6d11b473a819e5f3dbba7601
If I run in an image based on this newer image:
mcr.microsoft.com/azure-functions/python:4-python3.8-slim@sha256:74f2a9774e5b7f65965846cfd4b195177def72f283f4736760c1e43c12f66c0f
I getLogin timeout expired (0)
I connect ot the Azure SQL database using VNet Integration where the Function is joined into a subnet which is then whitelisted(https://learn.microsoft.com/en-us/azure/azure-functions/functions-networking-options?tabs=azure-cli) and I'm on a Premium App service plan.
The text was updated successfully, but these errors were encountered: