[BUG] MongoDB Connector 401 when trying Azure Function data API #3997
Description
Type of Connector
Certified Connector
Name of Connector
MongoDB
Describe the bug
In preparation for Mongo deprecating their Data API I've followed the suggested approach of deploying an Azure Function to replicate the API features and maintain access to Mongo data from a PowerAutomate Flow.
As explained here: https://github.com/microsoft/PowerPlatformConnectors/tree/dev/certified-connectors/MongoDB#option-2-set-up-azure-function-using-zipdeploy
The Azure Function was setup successfully and testing it from Azure portal and Postman works great. Even testing it from a Flow HTTP action works fine. However the Mongo connector fails from a Flow.
I've tried every app key option (master and default from both host and function levels). No matter which I get a 401 Unauthorized.
Is there some way to debug further and see the underlying request the Mongo connector is making? Is it just not formatting the request properly to the Azure Function?
Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 1 - Connector is broken or there's a very serious issue
To Reproduce
Follow instructions here: https://github.com/microsoft/PowerPlatformConnectors/tree/dev/certified-connectors/MongoDB#option-2-set-up-azure-function-using-zipdeploy
Expected behavior
The Mongo connector properly executes during Flow run.
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Additional context
