ArcGIS Connectors for Power Automate: What’s New in Release 2025.2
I am excited to share that ArcGIS Connectors for Power Automate release of version 2025.2, rolled out on Tuesday, July 22. We added a host of new capabilities and refinements that empowers users to use Spatial queries and filtering. Whether you’re building complex automations or simply connecting your GIS data to the Microsoft stack, these updates are crafted to elevate your experience.
In this post, I’ll Walk through all the major changes and improvements in 2025.2.
Major Enhancements to “Get Data from Feature Layer” Action
The “Get Data from Feature Layer” is one of the most used actions we offer and really is a soul of this product. I am most excited to share in the 2025.2 release; this action has received a significant overhaul and updates. This includes a redesigned interface to make it easier to use, additional options to query by geometry, and flexibility of querying by combining multiple parameters together. This update applies to both ArcGIS and ArcGIS Enterprise Connector.
Revised interface
The user interface for the “Get Data from Feature Layer” action has a revised options and placeholders to let you know what combination of options to use. In the older version of this action, it was difficult to interpret what is possible without glancing at the documentation.
The “Available Fields” option has been renamed to “Query by field” this matches the Query Endpoint of the ArcGIS REST API. The placeholder text will let you know what other parameters you need.
Older interface
New Interface
Combine different options
You can now combine any set of necessary parameters. E.g “Query by Field” (and its related “Comparison Type” and “Search Value” parameters) with a “Where” clause. This enables more powerful and granular queries, giving you the flexibility to filter records using field-based criteria alongside complex SQL expressions in your “Where” clause.
Here is an example:
Enhanced Geospatial Querying Using Esri Geometry
A major leap forward is the capacity to retrieve data using “Esri Geometry.” When leveraging this option, you can specify the spatial relationship for your query using available parameters. The default Spatial relationship is set to “intersects,” but other relationships supported by the Feature Layer REST API’s Query endpoint (such as “contains,” “within,” “touches,” etc.) are also available. You can search for features that intersect a geometry which can come dynamically from previous actions or can be manually added. This give ability to automate complex spatial operations and workflows and really opens up doors for automating on the fly spatial analysis.
- Note: The set of available spatial relationships and defaults might differ between ArcGIS Online and ArcGIS Enterprise connectors. Be sure to consult the ArcGIS REST API documentation for the specific connector you are using to understand the exact options. https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/
- You can also understand how the available Spatial Relationship options here: https://developers.arcgis.com/javascript/latest/api-reference/esri-rest-support-Query.html#spatialRe...
Search by Buffer Distance and Unit
Another significant addition is the ability to specify a “Buffer distance” and “Unit” (such as meters, kilometers, miles, etc.) instead of supplying raw geometry as input. This feature makes it far easier to execute proximity analyses or find records within a given radius. e.g. “find all service requests within 5 kilometers of this point.” By combining this with other query options, you can now design sophisticated spatial automations without the need for custom scripts.
Here is an example where I am trying to find public or private water wells withing Stream water quality stations.
Result Offset and Output Spatial Reference
Further refinements include renaming “Starting count” to “Result offset,” aligning terminology with REST API conventions and making pagination more intuitive for users. Additionally, the action now supports an “Output Spatial reference” parameter, allowing you to specify the coordinate system in which you want your results returned. This is valuable for integrating with downstream systems that require data in a consistent spatial reference.
Restrict ArcGIS Triggers (Webhooks) by Esri Geometry
Building on the enhanced geospatial querying capabilities, the “Fetch updates, changes, and deletions” action can now restrict triggers to extract changes occurring within a user-specified geometry. This is especially useful for monitoring only the areas that matter most for your workflows such as a field office, project site, or administrative boundary ensuring your automations remain focused and relevant.
In the following example, when a record is updated in my Water quality stations, I am adding a `Get data from Feature layer` action and to get the geometry of watersheds that I am responsible for and only using those (two) watersheds to restrict my “Fetch” action to extract relevant changes. Since the output of the get data from feature layer action is an `Array` the fetch action will be added inside a “For Each” loop.
Note that this update is for both ArcGIS and ArcGIS Enterprise connectors
Enterprise Webhooks now support referenced Feature & Map Services
On ArcGIS Enterprise connector webhooks are now officially supported on Feature Services and Map Services when data is referenced from Enterprise databases (When publishing from ArcGIS Pro with `Reference Data` option instead of “Copy All Data”.
- Practical Impact: If you are using ArcGIS Enterprise connector you can now use triggers to run your automation and visualize the same data in ArcGIS for Power BI visual as a data layer by adding the underlying database. You should be able to see your reports updated as the data comes in. This of course depends on how much data you are showing in PowerBI and Esri visual as both have some limits.
New Action: Get Item Information
2025.2 introduces the “Get Item Information” action. This action retrieves all relevant metadata and details for a specific item from your portal, such as:
- Title
- Description
- Comments
- Number of views
- Other key metadata
This makes it easier than ever to pull information about portal content for dashboards, reports, or automated documentation.
In the first parameter write the name of the Item you are trying to search and click the dropdown to find the relevant items.
Other Fixes & Improvements
In addition to the headline features, 2025.2 includes a series of smaller but impactful refinements:
- The expected field type for Create, Update, Read, and Delete actions are now clearly visible in the placeholder, reducing guesswork and errors in workflow configuration.
- Documentation has been updated for both the Enterprise connector and the Microsoft documentation set, ensuring users have access to the latest information and guidance.
- ArcGIS Connectors for Power Automate (and other ArcGIS for Microsoft Products) get its own documentation page on esri.com Introduction to ArcGIS Connectors for Power Automate—ArcGIS Connectors for Power Automate | Document...
- This gives us more flexibility of updating and customizing documentation for the product need. We expect to improve on this in upcoming releases to add more details for each actions and triggers.
