How to Create a MicrosoftTeamsConnector Web Connection for FME Flow

Introduction

This article will review the additional configuration steps required to get your functional FME Form MicrosoftTeamsConnector web connection working in FME Flow. 

Please note that Microsoft Azure is subject to change at any time, so the instructions and screenshots in this article may not exactly reflect those relevant to your Azure Portal. The overall concepts, however, will be the same.

Requirements

Step-by-step Instructions

Part 1: Modify the Azure App Registration

To successfully use your functional FME Form MicrosoftTeamsConnector web connection with FME Flow, your related Azure app registration must include the web as a platform, with a valid Client Secret and FME Flow redirect URI. The following steps detail how to modify your single-tenant or multitenant Azure app registration to meet these requirements.

1. Open Your Single-Tenant or Multitenant App Registration in Azure Portal

Login to Azure portal and go to App Registrations. 


App Registrations

Click on the app registration tied to your functional FME Form MicrosoftTeamsConnector web connection to access its configuration options.

Edit App Registration

2. Add the Web Platform and Redirect URI

Click the Authentication menu at left, and then select 'Add a platform'. Choose Web.
Add Web Platform

For the redirect URI, enter your FME Flow URL followed by /fmeoauth. For example, https://myfmeserver.mydomain.com/fmeoauth. Note that your FME Flow instance must be configured to use HTTPS.

Click Configure.
Configure Web URI
You should now see Web added with the redirect URI. You can add additional redirect URIs for other Instances of FME Flow that you plan to use with your MicrosoftTeamsConnector web connection.


RedirectURI

3. Create a New Client Secret

To connect to Microsoft Teams from FME Flow, you must have a client secret applied to your Azure app registration. This is not required in FME Form; it is only required in FME Flow.
Microsoft requires a client secret for confidential web apps (and this should not be used in a native app, like FME Form).

Click Certificates & secrets from the left-side menu, and then select 'New client secret'. 
CreateClientSecret

Give your client a description of the secret and its expiration date. Click Add. 

Once your client secret expires, you will need to create a new one and update your FME Flow web service with the new Client Secret value to continue connecting to Microsoft Teams.
Add New Client Secret

After clicking Add, make sure to copy the secret value (not the Secret ID) and store it in a safe place, like a password manager. You will only get one chance to save the secret value! You can create another secret if needed.


Client Secret Value

Your Azure app registration is now ready for use with FME Flow. 
 

Part 2: Publish the FME Form MicrosoftTeamsConnector Web Service and Connection to FME Flow and Modify

1. Publish to FME Flow

In FME Form, open a workspace that makes use of the MicrosoftTeamsConnector and your working MicrosoftTeamsConnector web connection. Confirm that this web connection is tied to the Azure app registration you modified in Part 1, above. You can confirm this point by checking that the Client ID value of your FME web connection's web service matches the Application (client) ID value of the Azure app registration you modified. The Client ID value of the web service can be accessed in FME Workbench by navigating to Tools > FME Options > Web Connections > Manage Services, and then selecting the web connection's web service from the list of web services displayed.  1, above. 

With confirmation that the web connection in use in the workspace is tied to the modified Azure app registration, connect to FME Flow and click the Publish button in the FME Workbench ribbon.
FME Form Publish

Proceed through the publish wizard. On the Upload Connections step, make sure to select the check box next to the MicrosoftTeamsConnector web connection you use in your workspace. This action will upload both the web connection and its underlying web service to FME Flow.
PublishTeamsConnection.jpg

Click Next, and then click Publish to publish the workspace with the web connection to FME Flow.
Publish to Flow

The MicrosoftTeamsConnector is a custom, embedded transformer downloaded from FME Hub and made available for use in FME Form the first time it is added to a workspace. Publishing a workspace containing this connector to FME Flow will make the connector available for use on FME Flow without any additional steps needed. You will not be presented with options in the Publish Wizard for publishing the connector, as they're not required. 

2. Modify the Web Service on FME Flow

Once the workspace and connection are published successfully, log in to the Web UI of the FME Flow instance you published to in Step 1. From the side menu, click Connections & Parameters > Web Connections. If you’re using a version of FME Flow prior to 2023, click Files & Connections. You should see the connection(s) you published from FME Workbench and their associated web services. Click Manage Web Services.
Flow_TeamsConnection.jpg

Click on the web service you want to edit (i.e, the web service that was published along with your MicrosoftTeamsConnector web connection).
Flow_WebService.jpg

Fill in the details for your web service:

  • Description (optional): It’s recommended to update the description so that it reflects at minimum the name of the Azure app registration used by this web service
  • Client ID: This value should already be present and match the Application (client) ID from the Azure app registration that you modified in Part 1, above
  • Client Secret: The client secret value from your Azure app registration is found in Certificates & Secrets. If you did not save the value when you first created the secret, you will need to create another in Azure.
  • Redirect URI (or Authorization URL): the Redirect URI, ending in fmeoauth, for your FME Flow instance. This was added to the web platform in your Azure app under Authentication in Part 1 - Step above. For example, https://myfmeserver.mydomain.com/fmeoauth

FlowWebServiceEditsOverview.jpg

Click OK to save the changes.

3. Authorize the Web Connection on FME Flow

Return to the Web Connections page. Click on the web connection associated with the web service. 
Flow_SelectTeamsConnection.jpg

Click Authorize. You will be prompted to log in with your Microsoft credentials and may be prompted to grant consent to the Azure app registration. Once authorized successfully, the web connection will have a green checkmark. Click OK to close the web connection.
Flow_WebConnection_Authorize.jpg

The MicrosoftTeamsConnector web connection is now ready for use on FME Flow.

Repeat this same process of modifying the web service and authorizing the web connection for any other MicrosoftTeamsConnector web connections that you publish from FME Form to FME Flow. The process is the same for single-tenant or multitenant-based MicrosoftTeamsConnector web connections. 

Related Resources

How to Create a MicrosoftTeamsConnector Single Single-Tenant Web Connection for FME Form

How to Create a MicrosoftTeamsConnector Multitenant Web Connection in FME Form

Was this article helpful?

We're sorry to hear that.

Please tell us why.

As of January 14th, 2026, comments on knowledge base articles have been closed. To make sure questions don’t get missed and to enable more community support, we’ve moved discussions to the FME Community. If you have a question or a comment about this article, please create a new post or create a support ticket.