Fortinet black logo

Cookbook

Configuring Azure

Configuring Azure

  1. Login to the Azure portal. If you do not yet have a directory or need to create a new one, go to Azure AD and click Create a tenant.
    Configure the directory with the following settings:
    1. Select a directory type: Azure Active Directory.
    2. Organization name: Enter a name for the organization.
    3. Initial domain name: Enter the domain name.
    4. Country/Region: Select the relevant country or region.
    5. Click Create. The directory will be created after a few minutes. When finished, select the directory in the top-right corner of Azure.
  2. Go to Enterprise Applications, and select Create your own application. Enter a name for your application, for example: Azure_fac_as_idpproxy.

  3. Go to the Single Sign-on section, select SAML, and edit the basic SAML configuration.
    Here you will include information obtained from FortiAuthenticator. In this example, the FortiAuthenticator FQDN is fac.fortilab.local, and the name of the server is defined as Azure_fac_as_idpproxy. You should adjust these settings to match your FortiAuthenticator's configuration.
  4. Edit the User Attributes & Claims section to insert any attributes required for the SAML assertion. In this example, only user groups have been included.
    Click the edit icon, and then click Add a group claim. Select All groups.
  5. Download the certificate file. It will be used later when configuring FortiAuthenticator.
  6. Go to Users and Groups, and click Add user. Include all users that will be able to authenticate using this application.
  7. Go to Properties and get the Application ID. This will be required later.
  8. From the directory home, select Roles and Administrators > Directory Readers, and click Add assignments. Search for your application name, then select and add it.
  9. Finally, create your authentication key. Go to App Registrations, click Certificates & Secrets, and create a new key.
Note

Before proceeding, make sure to copy the key value. The key is presented only after its creation, and you cannot get this information again later.

Configuring Azure

  1. Login to the Azure portal. If you do not yet have a directory or need to create a new one, go to Azure AD and click Create a tenant.
    Configure the directory with the following settings:
    1. Select a directory type: Azure Active Directory.
    2. Organization name: Enter a name for the organization.
    3. Initial domain name: Enter the domain name.
    4. Country/Region: Select the relevant country or region.
    5. Click Create. The directory will be created after a few minutes. When finished, select the directory in the top-right corner of Azure.
  2. Go to Enterprise Applications, and select Create your own application. Enter a name for your application, for example: Azure_fac_as_idpproxy.

  3. Go to the Single Sign-on section, select SAML, and edit the basic SAML configuration.
    Here you will include information obtained from FortiAuthenticator. In this example, the FortiAuthenticator FQDN is fac.fortilab.local, and the name of the server is defined as Azure_fac_as_idpproxy. You should adjust these settings to match your FortiAuthenticator's configuration.
  4. Edit the User Attributes & Claims section to insert any attributes required for the SAML assertion. In this example, only user groups have been included.
    Click the edit icon, and then click Add a group claim. Select All groups.
  5. Download the certificate file. It will be used later when configuring FortiAuthenticator.
  6. Go to Users and Groups, and click Add user. Include all users that will be able to authenticate using this application.
  7. Go to Properties and get the Application ID. This will be required later.
  8. From the directory home, select Roles and Administrators > Directory Readers, and click Add assignments. Search for your application name, then select and add it.
  9. Finally, create your authentication key. Go to App Registrations, click Certificates & Secrets, and create a new key.
Note

Before proceeding, make sure to copy the key value. The key is presented only after its creation, and you cannot get this information again later.