Issue with Custom Engine Agent for Copilot – Service Not Responding After Deployment to Kubernetes

Question

Issue with Custom Engine Agent for Copilot – Service Not Responding After Deployment to Kubernetes

Hasan, Md. Mehedi 0

I’m trying to create a Custom Engine Agent for Copilot. I have set up a bot, an app registration, and a manifest file. When I run the service locally using DevTunnel, everything works fine—the bot responds as expected in Teams chat and Copilot chat.

However, after deploying the service to a Kubernetes cluster (running in a pod), I updated the bot configuration endpoint accordingly. The service is accessible from Postman and responds correctly to API calls, so I’m confident it’s active. It also works when tested via the “Test in Web Chat” feature on the bot configuration page.

The issue is that when I ask questions from Teams chat or Copilot chat, there is no response. I checked the pod logs, and there’s no trace of any incoming requests from Teams or Copilot. The same manifest and app registration work perfectly when the service runs locally via DevTunnel.

Could you help me identify why the bot is not receiving requests from Teams or Copilot after deployment to Kubernetes?

Prasad-MSFT 10,496 Reputation points Microsoft External Staff Moderator

2025-11-25T12:15:29.39+00:00

Is your Kubernetes service exposed via a public LoadBalancer or Ingress with HTTPS? Can you access https://<your-bot-endpoint>/api/messages from the public internet (not just inside your VNet)? Also, in the Azure Portal, go to your Bot Channels Registration resource and verify the Messaging endpoint matches your deployed service.
Hasan, Md. Mehedi 0 Reputation points

2025-11-26T06:26:59.9866667+00:00

Hi
Thank you for your response.
Yes, the endpoint is accessible from the public internet. It is esposed via ingress with HTTPS.
Yes I double check and can ensure you the messaging endpoint in Bot Configuration matches my deployed service.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Hasan, Md. Mehedi 0 Reputation points

2025-11-26T18:43:54.1066667+00:00

Hi I see my comment was deleted. I found that it is working when I use dev tunneling and it is requesting from teams bot with http instead of https. I'm guessing that's the reason why direct communication is not happening. Devtunnel can redirect it's request from http to https, so it's working. Do you have any idea why it's happening, though I've used https in bot configuration endpoint? Actually I'm stuck by this issue.
Prasad-MSFT 10,496 Reputation points Microsoft External Staff Moderator

2025-12-24T13:16:03.5433333+00:00

Teams doesn’t call your bot directly. It goes through the Bot Framework Service, which may forward requests using HTTP, even if your bot endpoint is configured as HTTPS.

DevTunnel works because it accepts HTTP and auto-redirects to HTTPS. Kubernetes fails because your ingress likely blocks HTTP, so requests never reach the pod.

Fix: Allow HTTP (port 80) at the ingress and redirect HTTP → HTTPS.