Logic App SQL Connector (Azure)- Please create new connection with VNET Private Endpoint

by Asish PunnoseAzure Logic Apps

{“status”: 404,“source”: “https://logic-apis-australiaeast.token.azure-apim.net:443/tokens/logic-apis-australiaeast/c08521edf6a2297f/sql/b27996f6a1cd4fc2a97aa47815f7f5ce/exchange”,“message”: “Error from token exchange: The connection (logic-apis-australiaeast/sql/b27996f6a1cd4fc2a97aa47815f7fwr6) is not found. Please create new connection and change your application to use the new connection.”} Solution: Only Built-in connectors supports VNET integration and private endpoint

{“code”:”InvalidTemplateDeployment”,”message”:”The template deployment ‘Microsoft.Web-FunctionApp-Portal-b06e931b-bcdb’ is not valid according to the validation procedure. The tracking id is ‘4d7b14aa-8133-4818-aa26-2ca3dab75b77’. See inner errors for details.”,”details”:[{“code”:”ValidationForResourceFailed”,”message”:”Validation failed for a resource. Check ‘Error.Details[0]’ for more information.”,”details”:[{“code”:”MaxNumberOfServerFarmsInResourceGroup”,”message”:”The maximum number of ServerFarms allowed in a Resource Group is 100.”}]}]}

by Asish PunnoseAzure

Logic Apps (Preview) Workflows missing

by Asish PunnoseAzure Logic Apps

Getting following warning while deploying from Visual Studio code through Azure extension 6:37:58 AM: WARNING: Deployment succeeded, but failed to list http trigger urls. Solution:- Check the storage account associated with the logic apps does have private endpoint enabled. If so please ensure that the associated storage account has private link resource types enabled for files… Read More