Comment on page

Using Docker with Azure Functions and SignalR Service

If you want to use Serverless Azure Functions and Azure SignalR Service with TaaS WebSocket/SignalR

Running TaaS with Azure Functions and Azure SignalR Service

In this configuration we are using a different docker image - this one is only sending a new blocks to our Azure Function, which then sends parsed information to subscribers through Azure SignalR Service.
If you just want to use a Docker container without having to setup Azure infrastructure please check Using Docker documentation section.
Ready-to-use docker image is available from Docker Hub here:
Example of the docker run command
  • setting the Tezos:NodeUrl env. variable to
  • setting the Azure:AzureFunctionUrl env. variable to
  • setting the Azure:AzureFunctionKey env. variable to MySecretFunctionKey
Be sure to configure the following ENV keys correctly per your environment
  • Tezos:NodeUrl
  • Azure:AzureFunctionUrl
  • Azure:AzureFunctionKey
docker run -it --env Tezos:NodeUrl="" \
--env Azure:AzureFunctionUrl="" \
--env Azure:AzureFunctionKey="MySecretFunctionKey" \
This infrastructure setup has the following benefits
  • It allows you to have a more robust security out of the box as all communication is encrypted by TLS.
  • It makes scaling your applications for thousands of subscribers much easier by using serveless compute with scalable SignalR Service.
For client side instructions please see
More information about Azure Functions can be found at
More information about Azure SignalR Service can be found at