Fortinet Document Library

Version:


Table of Contents

Azure Cookbook

Resources

Upgrade Path Tool

Azure Cookbook

6.2.0
Download PDF
Copy Link

Automatically updating dynamic addresses using Fabric connector (Azure)

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

In the FortiGate interface, these connectors are called Fabric connectors and are 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 Security Fabric.

Before installing and configuring the Azure Fabric connector, the following Azure infrastructure and Fortinet FortiGate-VM 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.
  • A FortiGate-VM virtual appliance should be deployed in Azure
  • An IPv4 outbound policy from the FortiGate-VM virtual appliance on port2 (internal) to port1 (external)
  • A VM instance of a resource in the Azure environment. This instance uses a Linux server for testing tag assignment.

This section describes configuring an Azure Fabric connector. If the FortiGate is a virtual device in one of those environments, it is likely to be the only connector configured.

Resources

Automatically updating dynamic addresses using Fabric connector (Azure)

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

In the FortiGate interface, these connectors are called Fabric connectors and are 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 Security Fabric.

Before installing and configuring the Azure Fabric connector, the following Azure infrastructure and Fortinet FortiGate-VM 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.
  • A FortiGate-VM virtual appliance should be deployed in Azure
  • An IPv4 outbound policy from the FortiGate-VM virtual appliance on port2 (internal) to port1 (external)
  • A VM instance of a resource in the Azure environment. This instance uses a Linux server for testing tag assignment.

This section describes configuring an Azure Fabric connector. If the FortiGate is a virtual device in one of those environments, it is likely to be the only connector configured.