deployment-config:routing:
routing-rules:
# The following rules are for outgoing HTTP requests to the Teams Phone Mobile Consultation API.
# For each rule, fill in the "gateway" values. These can be found in the SDF for the deployment - find the
# subnet used by MCP nodes with a http "traffic-type".
#
# The "target" values correspond to the hostnames in the "name" attributes.
# Additionally, the deployment must allow outbound connections to the ranges in the "target" values (e.g. using
# firewall rules).
- name: "OAuth2.0 Routing 1 (login.microsoftonline.com)"
target: 20.190.128.0/18
interface: http
gateway: <HTTP_INTF_GATEWAY_IP_ADDRESS>
node-types:
- custom
- name: "OAuth2.0 Routing 2 (login.microsoftonline.com)"
target: 40.126.0.0/18
interface: http
gateway: <HTTP_INTF_GATEWAY_IP_ADDRESS>
node-types:
- custom
- name: "Teams Phone Mobile Consultation API Routing 1"
target: 52.112.0.0/14
interface: http
gateway: <HTTP_INTF_GATEWAY_IP_ADDRESS>
node-types:
- custom
- name: "Teams Phone Mobile Consultation API Routing 2"
target: 52.120.0.0/14
interface: http
gateway: <HTTP_INTF_GATEWAY_IP_ADDRESS>
node-types:
- custom
# # To create additional routing rules, extend the routing-rules list as shown in the example below.
# - name: Example1
# # The target for the routing rule.
# # Can be either an IP address or a block of addresses (e.g. 10.0.0.0/8).
# target: 8.8.8.8
# # The interface to use.
# # Must correspond to a valid traffic type for the node types this routing rule applies
# # to e.g. management.
# interface: management
# # The IP address of the gateway to route through.
# gateway: 0.0.0.0
# # The node types this routing rule applies to (As above, use `custom` for mcp nodes).
# # If ommitted, this routing rule will be attempt to apply itself to all node types.
# node-types:
# - tsn
# - mcp
# - name: Example2
# # ...
