Configuring Azure Active Directory with FME Flow

In order for FME Flow to communicate with Azure AD, you must create and register FME Flow as an enterprise application in Azure AD.

  1. From the Azure Active Directory portal, select Manage > App registrations > + New Registration, and complete the following fields:
    • Name: Provide a name for the registration, such as FMEFlow.
    • Supported Account Types: Specify whether to allow FME Flow to interact with a single Azure AD tenant or multiple Azure AD tenants.
    • Redirect URI:
      • type: Web
      • URI: <FMEFlowWebURL>/fmesso/azuread/redirect, where <FMEFlowWebURL> is the fully-qualified hostname for your FME Flow, including both the hostname and domain. For example:
      • Note  In most cases, Azure AD requires URI to begin with https. To configure FME Flow to use HTTPS, see Configuring for HTTPS.
  2. Click Register.
  3. An overview page of the application registration opens. Navigate to Overview > Essentials, and record the Application (client) ID and Directory (tenant) ID.
  4. Navigate to Certificates & secrets, and select + New client secret.
  5. Record the client secret.
  6. Warning  The client secret cannot be viewed after this step.
  7. (Optional) Navigate to Authentication > Web > Add URI, and add any other necessary URI redirects, according to the format specified above for Redirect URI.
  8. Navigate to API permissions, and select + Add a permission. Add the following permissions:
    • Microsoft Graph > Application permissions > Group.Read.All, User.Read.All
    • Microsoft Graph > Delegated permissions > User.Read
    • Grant admin consent for Name.
    • Note  Admin consent is required to proceed, and can be granted only by an Azure AD admin.
  9. If FME Flow uses Microsoft Internet Information Services (IIS) as a reverse proxy, perform the additional configurations:
    1. Append the URL of your reverse proxy to the fmeserver.sso.custom.baseurl= line in the SSO file. If your FME Flow uses an Apache Tomcat web application server provided with the installation, this file is located in <FMEFlowDir>\Utilities\tomcat\webapps\fmesso\WEB-INF\classes\.
    2. Restart FME Flow.
    3. Ensure the Redirect URI setting on your Azure Active Directory portal is set to the URL of your reverse proxy (rather than your FME Flow hostname), appended with /fmesso/azuread/redirect.
    4. Tip  In your IIS reverse proxy settings, clear Reverse rewrite host in response headers. In IIS Manager, this setting is located in the Application Request Routing Cache tool, under Actions > Server Proxy Settings.

What's Next?

Proceed to Creating an Authentication Service Connection.