Azure Provider
This section of our documentation discusses how to configure a standby page for a Azure provider.
This section of the documentation contains additional information you will need when configuring your standby page with an Azure provider, it is split into two main sections: Entrypoints and Agent configuration.
For an exhaustive list of the entrypoints we support, please see the following page
Entrypoints
The table below, details the information you will need to provide and any additional information that will help you configure your standby page.
Azure Front Door
To configure Azure Front Door as an entrypoint you will require the origin group that your application is serves traffic from.
Application Gateway
To configure an Application Gateway as an entrypoint, you will require the backend pool that your application serves traffic from
Azure Load Balancer
To configure an Load balancer as an entrypoint, you will require the backend pool that your application serves traffic from
Public IP
To configure a Public IP, you will only need the public IP address that traffic is served from
Agent Configuration
For the agent to be deployed to your environment with the provider, we require additional items in order for us to ensure that is deployed in the correct location. You may require this information from the team that provisioned your infrastructure, alternatively it is available in the Azure portal. The table below details each item we require, and if they are a mandatory field.
Resource Group
This is the resource group that the agent will be deployed in.
VNET
This is the VNET where the agent will be deployed
Subnet
This is the subnet where the agent will be deployed
Network Security Group
(optional) You can configure a Network Security Group that will be attached the Network Interface of the agent
Application Security Groups
(optional) You can configure Application Security Groups that will be attached to the agent
Availability Set
(optional) Select an availability set for the agent to be deployed into
Create Public IP
(optional) Check this box if the Virtual Machine that is provisioned is required to have a public IP address. This will be required if your entrypoint does not have VNET integration enabled for example Traffic Manager
HTTP Ports
This is the ports that your application will utilise. Input a comma separated value list, for example if your application runs on ports 80,81,8111 then the input will be: 80,81,8111
Last updated