Fortinet Document Library

Version:


Table of Contents

5.6.0
Copy Link

Overview

In this section, you configure FortiGate Fabric connector for use with Azure.

In the FortiGate interface, these connectors are called Fabric connectors and are software-defined network (SDN) connectors that provide integration and orchestration of Fortinet products with key SDN solutions. The Fortinet Security Fabric provides visibility into your security posture across multiple cloud networks, spanning private, public, and Software as a Service (SaaS) clouds. By using the Fabric Connector for use with the Azure IaaS, changes to attributes in the Azure environment can be automatically updated in the Fortinet Security Fabric.

Before installing and configuring the Fabric connector for Azure, the following Azure infrastructure and Fortinet FortiGate components should be in place :

  • A valid Azure account and subscription. This could be one established by your organization or simply one of the free trial options available from Azure. If you do not specify the resource group, you can find all resources that the account has access to.
  • You should deploy a FortiGate-VM appliance in Azure
  • An IPv4 outbound policy from the FortiGate-VM appliance on port 2 (internal) to port 1 (external)
  • A VM instance of a resource in the Azure environment. In this instance, a Linux server has been used for testing tag assignment.

In FortiOS 5.6, there can only be one Fabric connector for each type of environment (AWS/Azure/VMware NSX, and so on) on a FortiGate. In this section, it is a Fabric connector for Azure. If the FortiGate is a virtual device in one of those environments, it is likely the only connector configured

Overview

In this section, you configure FortiGate Fabric connector for use with Azure.

In the FortiGate interface, these connectors are called Fabric connectors and are software-defined network (SDN) connectors that provide integration and orchestration of Fortinet products with key SDN solutions. The Fortinet Security Fabric provides visibility into your security posture across multiple cloud networks, spanning private, public, and Software as a Service (SaaS) clouds. By using the Fabric Connector for use with the Azure IaaS, changes to attributes in the Azure environment can be automatically updated in the Fortinet Security Fabric.

Before installing and configuring the Fabric connector for Azure, the following Azure infrastructure and Fortinet FortiGate components should be in place :

  • A valid Azure account and subscription. This could be one established by your organization or simply one of the free trial options available from Azure. If you do not specify the resource group, you can find all resources that the account has access to.
  • You should deploy a FortiGate-VM appliance in Azure
  • An IPv4 outbound policy from the FortiGate-VM appliance on port 2 (internal) to port 1 (external)
  • A VM instance of a resource in the Azure environment. In this instance, a Linux server has been used for testing tag assignment.

In FortiOS 5.6, there can only be one Fabric connector for each type of environment (AWS/Azure/VMware NSX, and so on) on a FortiGate. In this section, it is a Fabric connector for Azure. If the FortiGate is a virtual device in one of those environments, it is likely the only connector configured