Encountering integration challenges between Dialogflow CX and Azure Bot.

[eBiz]

I've built an AI Agent using Google’s 1.5 Flash AI model, uploaded my data into a data store, and successfully connected it to Vertex AI. After thorough testing within Vertex AI, where I received accurate responses to all queries, I proceeded to integrate the Agent with Microsoft Teams. I followed the instructions in the GitHub repository (https://github.com/GoogleCloudPlatform/dialogflow-integrations/blob/master/cx/azure-bot-service/READ...), which I accessed through the ‘Azure Bot Service/Skype’ integration option in the Agent console.

However, I encountered challenges during this integration. The `server.js` and `package.json` files in the repository were outdated. After updating these files and deploying the repository to Cloud Run, I set the webhook URL in Azure Bot Service. Yet, testing the connection in the webchat yields no responses. Occasionally, the platform prompts me to review the source code for further adjustments.

I would appreciate any guidance on resolving these integration issues, particularly around ensuring compatibility and functionality in the Azure Bot Service.

[porunga]

Hi I tested this integration ***until the Azure Bot test*** and it works fine even in the nodejs18 runtime, nake sure to check the .env file parameters:

MICROSOFT_APP_ID=[from azure cloud]
MICROSOFT_APP_PASSWORD=[from azure cloud]
PROJECT_ID=your-project-at-gcp-sandbox
LOCATION=global
AGENT_ID=[your agent id from GCP]
DIALOGFLOW_ENDPOINT=dialogflow.googleapis.com

LOCATION and DIALOGFLOW_ENDPOINT I had a lot issue with this combination because “global” wasn’t an option initially (I’d get error logs saying it’s not allowed).

Also AGENT_ID looks like this and not the entire link (seem some errors like that): 

11XXXXXXX-1XX1-1XXX-X1XX-1XXXXXXX1

(Notice I replace X for security).

Also dont use " " in the .env file.

[Tim-Moor]

I’m experiencing the exact same issue. While the Azure integration instructions are well-written, they seem outdated and somewhat misleading.

There are two README files—one in the main directory and another in cx\azure-bot-service. Which one is correct? I have tried both but got the same result.

• The Docker image was successfully built and loaded.
• The webhook function was deployed with allUsers access.

However, when I test it using the following command:

Invoke-RestMethod -Method POST -Uri $url1 `
    -Headers @{ "Content-Type" = "application/json" } `
    -Body (@{ 
        "type" = "message";  
        "text" = "Hello" 
    } | ConvertTo-Json -Depth 10)

I get a "Unauthorized Access" error.

From what I understand, this is not related to Azure Bot, but rather an issue with the webhook function itself or its access rules.

I'm deploying in us-east1—could that be causing the issue?

Has anyone successfully made this work?