Fortinet Document Library

Version:


Table of Contents

6.0.0
Copy Link

Overview

This section includes a step-by-step guide for configuring a Fabric Connector on Azure Stack.

Some of the use cases for using a Fabric Connector are:

  • Autoscaling and elasticity of security policies (such as dynamic IP address learning for dynamic security policies).
  • FortiGate Unicast active-passive HA requires Fabric Connector configuration to make changes to Azure Stack environments using API calls.

Before installing and configuring the Fabric Connector for Azure Stack, the following components must be in place:

  • For dynamic policy using dynamic addresses, a single FortiGate must be deployed.

  • For HA deployments, two FortiGates must be deployed and configured with Unicast Active-Passive HA.

    The use case is for making API calls to change Azure environment routing and public IP association. If the use case is for a FortiGate Active-Passive unicast HA with the use of load balancers, Fabric Connectors configuration is not required.

Overview

This section includes a step-by-step guide for configuring a Fabric Connector on Azure Stack.

Some of the use cases for using a Fabric Connector are:

  • Autoscaling and elasticity of security policies (such as dynamic IP address learning for dynamic security policies).
  • FortiGate Unicast active-passive HA requires Fabric Connector configuration to make changes to Azure Stack environments using API calls.

Before installing and configuring the Fabric Connector for Azure Stack, the following components must be in place:

  • For dynamic policy using dynamic addresses, a single FortiGate must be deployed.

  • For HA deployments, two FortiGates must be deployed and configured with Unicast Active-Passive HA.

    The use case is for making API calls to change Azure environment routing and public IP association. If the use case is for a FortiGate Active-Passive unicast HA with the use of load balancers, Fabric Connectors configuration is not required.