Search

How to Connect to Microsoft Dataverse using FME Form

Divya Sakpal
Divya Sakpal
  • Updated

Introduction

Microsoft Dataverse is a cloud-based data platform used by Power Apps, Dynamics 365, and other Microsoft business applications. This article describes how to configure Azure and FME so that you can read and write Dataverse table data. The steps below cover creating an Azure App Registration, identifying the Power Platform environment, configuring a Web Service in FME, and authenticating a Web Connection for use with the Microsoft Dynamics 365 Reader and Writer.

This article demonstrates a single tenant configuration, which is the most common setup for enterprise Dataverse environments. Multi-tenant configurations are possible but are generally used only for applications designed to serve external organizations.

 

Requirements

Before we begin, ensure that the following requirements are met:

 

Step-by-Step Instructions

Part 1: Azure App Registration

In this section, we will create an Azure App Registration that allows FME to authenticate with Microsoft Dataverse. This app represents FME in Azure Portal and defines how authentication and permissions are handled.

1. Register an App in the Azure Portal

Sign in to the Azure Portal and go to App Registrations.

 

Click on New registration.

 

Provide a Name for the application and select “Accounts in this organizational directory only (single tenant)”. Leave the Redirect URI blank for now, we will update this in a later step.

 

Click Register.

 

2. Configure the Platform and Redirect URI

This step configures the authentication flow used by FME. The platform setting defines how the application authenticates, while the Redirect URI specifies where Azure sends the authentication response after a successful sign-in. The Redirect URI must match exactly between Azure and FME for authentication to succeed.

On the newly created App, select Authentication and then click on “Add Redirect URI”.

 

From the Platform ribbon, click on Mobile and Desktop Applications.

 

For a Custom redirect URI, enter:

https://fmeauth.safe.com/v1/oauth2

The redirect URI https://fmeauth.safe.com/v1/oauth2 is used in FME 2025.2+ to authorize the web connection in an external browser. This is the recommended approach. To learn more, please read External Browser Authentication. For older versions of FME that still use an embedded browser, you can use http://localhost as the redirect URI.

After entering the URL, click Configure.

 

3. Configure the Permissions

API permissions allow the application to request access tokens and act on behalf of the signed-in user when accessing Microsoft Dataverse.

On the app, select API Permissions. Click Add a permission.

 

In Request API Permissions, scroll down to Dynamics CRM under Microsoft APIs.

 

Enable user.impersonation permission and click Add permissions

 

4. Record Application Details

Note the Application (Client) ID and the Directory (Tenant) ID, which can be found on the app’s Overview page. These will be used to configure the web service in the later steps.

 

Part 2: Power Platform Environment

A Power Platform environment is a space to store, manage, and share your organization's business data, and can contain zero or one Dataverse database. Every environment has an environment URL, which is used by external applications such as FME to connect to the Dataverse database.

 

1. Identify the Environment URL

Log in to Power Apps and make sure the correct Environment is selected in the top banner.

 

Click the Settings icon and select Advanced settings.

 

This will open Power Platform Environment Settings. The base URL shown in the browser address bar is your Environment URL.

 

For more information about Power Platform environments, including environment types and governance considerations, see the Microsoft documentation: Environments Overview.

 

Part 3: Configure the Web Connection in FME Form

This part configures FME to authenticate with Azure and connect to the Power Platform environment. We will create a Web Service that defines how authentication is performed and references the Azure App Registration and Power Platform environment URL from Parts 1 and 2.

 

1. Create a Web Service in FME

Open FME Form and go to Tools > FME Options > Web Connections > Manage Services.

 

On the Manage Web Services window, click the plus sign below the list of web services and then select Create From > Microsoft Dynamics 365 (Template) (safe.microsoft-dynamics365)

 

2. Configure the Web Service parameters

This section configures the parameters required for FME to authenticate against the Azure tenant and connect to the Power Platform environment.

Single tenant Azure app registrations must use tenant specific endpoints. The /common endpoints are intended for multi tenant applications and should be replaced with your Directory (tenant) ID.

Configure the parameters as follows:

  1. Web Service Name: Provide a unique name. It is recommended to include the transformer that this web service will be used for and the Azure app registration name, so the service can be easily identified later.
  2. Client ID: Enter the Application (client) ID from the Azure App.
  3. Not Required: leave this checked. Client secrets are only required when configuring this connection in FME Flow.
  4. Redirect URI: Enter the Redirect URI that matches your Azure App Registration.

It’s important to ensure that the web service’s Redirect URI value matches the custom redirect URI that was applied to the Azure registered application in Create the Azure App Registration step 2. If these two values do not match, the web service will not function properly.

  1. Redirect Strategy: Select 'Proxy Redirect (Safe Software)'. This uses your system browser to complete authentication. Note: This option is not available in versions of FME prior to 2025.2, which use the embedded browser.
  2. Authorization Parameters URL: Replace common with your Tenant ID
  3. Authorization Parameters URL: Replace [ENVIRONMENT_URL] with your Power Apps environment URL.
  4. Retrieve Token Parameters URL: Replace common with your Tenant ID
  5. Retrieve Token Parameters URL: Replace [ENVIRONMENT_URL] with your Power Apps environment URL.
  6. Refresh Token Parameters URL: Replace common with your Tenant ID
  7. Refresh Token Parameters URL: Replace [ENVIRONMENT_URL] with your Power Apps environment URL.
  8. Click Apply to save all the values

 

3. Test the Web Service

Scroll down to the bottom of the web service and click Test.

 

This will open a browser window to authorize the web service. When prompted, sign in using your Microsoft organizational account. If Microsoft prompts you to grant permissions to the Azure app, click Accept.

Once the web service test is successful, you can create a web connection. Close the Manage Web Services dialog to return to the Web Connections menu.

 

4. Create the Web Connection

In the Web Connections menu, click the plus (+) button to add a new connection.

 

On the Add Web Connection window, select the web service you created from the dropdown. Give the connection a unique name and click OK.

 

You will be prompted to authenticate with Microsoft again.

Once the Web Connection is successfully authenticated, it can be used with the Microsoft Dynamics 365 Sales Reader and Writer transformers to read and write Dataverse table data.
 

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.