We are running N8N in a non public Azure vnet.
In the same vnet we also have an Azure Bot instance running that is connected to the MS Teams channel.
In general I can push messages to teams no problem.
However when I want to publish a webhook for teams, I get Failed to resolve domain n8n.contoso.com: No such host is known
I am pretty sure that is because of our not publicly available N8N instance and someone is trying to resolve that domain who shouldn’t be resolving it.
Now my question is, is this just a plain and simple not supported setup?
Or are there steps I could take to remediate this issue.
The documentation on the Teams Trigger is a bit lacking.
@WD1 it’s not n8n and not unsupported, it’s the Teams channel. Even with the Azure Bot resource in your VNet, Teams routes through Microsoft’s public Bot Framework Connector, which HTTPS POSTs to your messaging endpoint from the public cloud. So it has to be publicly reachable. n8n.contoso.com is private, Microsoft can’t resolve it, hence “No such host is known.”
Two supported paths:
Keep n8n private, expose only the webhook via a public reverse proxy, Azure Application Gateway (WAF) or API Management with VNet integration, on a public DNS name. The Bot Connector reaches n8n through that; the editor stays private.
For zero public ingress, the only option is the Direct Line channel + Direct Line App Service Extension (stays fully in-VNet). That’s not the standard Teams channel, which always needs a public endpoint.
So put a public ingress in front of the webhook host and point the bot’s messaging endpoint at it.
