We’re excited to share the 2026.2 release of ArcGIS Connectors for Power Automate. This update brings meaningful improvements from new API key support to better feature layer filtering and premium feature service support.
Release highlights
- API key authentication for the ArcGIS Online (ArcGIS) connector
We are most excited about update in 2026.2. You can now connect to the ArcGIS Online (ArcGIS) connector by using either user authentication or an API key. This gives organizations more flexibility in how they enable automation for their users. You no longer need to create a named user for your customers to offer ArcGIS services such as geocoding, enrichment, and routing. It also opens the door to more controlled access patterns by scoping API keys to specific Feature services or items, making it easier to support multiple clients efficiently. Most actions in the ArcGIS Online (ArcGIS) connector can be used with API key authentication when the key has the appropriate privileges and access. At this time, triggers and Survey123 actions are not supported with API key authentication, and the Run Data Pipeline action still has a known issue that will be addressed in a future release. For details on creating API key credentials, see the Esri documentation.
This effectively reduces the need for you to use ArcGIS PaaS connector, which you can continue to use. We do not plan make any updates to the ArcGIS PaaS connector as it is simpler story and less maintenance to offer it as an authentication type in ArcGIS Connector.
- Name your connection
As a welcome side benefit of API key authentication, users can now provide a custom name for ArcGIS Online (ArcGIS) connections while connecting in a flow. This has been a top request at UC for many years and pain point for all of us who want a cleaner, more manageable way to organize multiple ArcGIS Organizations. Turns out Microsoft allows naming the connections if you are using API key as an authentication type which wasn’t possible before. - Know why you flow triggered and what changed?
The Fetch updates, changes, or deletions from feature layer action now returns information about changes in other layers within the same feature service. Because webhooks are created at the feature service level, updates in layers other than target layer could trigger the flow but lead to empty output in the fetch action. With this release, when changes occur in a layer other than the target layer, hasChangesInOtherLayers returns true and changesInOtherLayers identify the relevant changes and their object IDs. This makes it easier to build more intelligent follow-up logic in downstream steps.
"changesInOtherLayers": {
"1": {
"name": "MyFeatureLayer",
"url": "https://mydomainname.com/server/rest/services/Hosted/MyFeatureService/FeatureServer/1",
"items": {
"adds": [],
"updates": [
10,
9
],
"deletes": []
}
}
}- Larger image support for Extract EXIF tags from image
In the ArcGIS Enterprise connector, the Extract EXIF tags from image action now supports images up to 50 MB, increased from the previous 10 MB limit. This improvement makes the action more practical for high-resolution photos and field workflows where image size can vary significantly.
- Feature layer filtering in triggers and actions
You can now use the “Layers in” drop-down filter when working with the Fetch updates, changes, or deletions from feature layer action and with triggers that prompt you to provide a feature layer. For performance reasons, the drop-down loads up to 1,000 layers. This was a problem especially if your connection is created using admin account who will have access to all the layers in an organization. If you have more feature layers in your Content or Organization, then you can add them to My Favorites and use the Favorites filter or copy the layer URL and paste it as a custom value in the Feature layer parameter. This enhancement is especially helpful for admin-level connections that have visibility into many layers across an organization. If you need a layer beyond the initial list, you can add it to Favorites and use the Favorites filter or paste the layer URL directly as a custom value. - Improved dynamic content for Get coded value domains action
The Get coded value domains from feature layer action now returns each code-and-domain pair for configured fields as dynamic content. That means it is easier to reference the correct values in later steps of a flow without extra parsing or transformation. - Support for premium feature services
ArcGIS Connectors for Power Automate now support premium feature services. - Documentation Updates
ArcGIS Connectors documentation has been evolved significantly to include details for input parameters for each actions . E.g Get data from feature layer action now lists all the options available for you to use. Get data from feature layer—ArcGIS Connectors for Power Automate | Documentation. We hope this gives everyone clearer understanding of what each action and connector can do. For additional details we have also included links to the REST API Documentation if you want to see how they are working.
We’re especially excited about what API key authentication and premium feature service support unlock for organizations building scalable automation with ArcGIS. We hope these updates make it even easier for you to create robust, location-aware workflows for you and your users and we’d love to hear what you build with them next.
