Latest Contributions by AkshayHarshe

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. Set up the ArcGIS Online (ArcGIS) connector—ArcGIS Connectors for Power Automate | Documentation Tutorial: Create an API key | Documentation | Esri Developer Privileges | Documentation | Esri Developer 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.   ... View more

With the 2026.2 release, we introduced API Key Authentication to the ArcGIS Connector. Following this update, we are observing an issue where existing authentications appear as “connected” but shows errors in existing flows. During pre-release validation, we worked closely with Microsoft and did not encounter this behavior in our QA connectors existing flows with older connections continued to function as expected even after the change in authentication. At this time, it is unclear to us why connection tokens associated with existing connections are expiring or becoming invalid. Unfortunately, this is out of our control to troubleshoot as Power Automate maintains all connections. We have engaged Microsoft and scheduled a meeting to investigate this further. We will provide updates as soon as more information becomes available. Additionally, we’ve noticed that in affected connections, options such as Reconnect or Switch Account are not available, which limits recovery for existing connection. *** Change : The Following pathway is not available until MS rolls out the 2026.2 version with the fix. In the meantime, the following steps can help restore functionality. This process can be time-consuming if you have many flows: Open any flow that is not working. Select an ArcGIS action. Click Change connection on the left pane. Click Add New. Choose ArcGIS Online User Credentials in the dropdown and provide a meaningful connection name. Sign in to your ArcGIS Organization. Update all ArcGIS actions and triggers to use the newly created connection. If other flows are using the same connection, update those as well and save each flow. For Triggers/Webhooks, verify that the webhook is active and functioning on your Feature Service. We understand this is disruptive and appreciate your patience. Apologies for the inconvenience, and thank you for your understanding. *** Update 1 June 9 It appears that Microsoft tried reverting the recent release back to 2026.1 to minimize impact. It is frustrating to say the least, that this is not something we asked for to happen as many of you have already created new connections with (new) multi-authentication and updated your flows. Last night none of my flows were working. As of this morning they have provided a fix that I am testing. I will update everyone after I have additional information. Thank you for your patience. *** UPDATE Jun 10 4:15PM Since Microsoft rolled back the connector to the previous version, most existing connections are no longer working unless you create a new one (again). We’ve completed testing their latest updates, which include: Support for both Single Authentication (old method) and Multi-Auth (new dropdown-based connections), covering both existing and new connections A fix for the UI issue with connection status From what we understand, this update should begin rolling out in a few hours. Unfortunately, all testing is done using a temporary custom connector they provide, which is only deployed to Microsoft production after validation. This means we can’t test the actual production ArcGIS connector directly. That said, I’m optimistic this will resolve the connection issues, or at least provide a Reconnect option when tokens expire. We have multiple scenarios currently running on production connectors and will review those results later today. Realistically, some of you may notice the changes before we do. *** Update June 12 Noon Update with the fix is rolled out to following regions according to Microsoft: France, Brazil, India, Korea, Norway, Switzerland, Canada, Australia, Asia, Germany and South Africa. You should see the new authentication type and 2026.2 version. *** How do you know you are looking at 2026.2? Create a new flow with a manual trigger. Add Convert date and time format action. Use formula to add `utcNow()`  Run the flow In the run click on the Convert date and time format action then select Show raw outputs In the headers section you should see the arcgis_connector_version Alternatively, you click create new connection it should give you a dropdown to choose between User login and API Key. *** June 14th Morning The fix is rolled out to the US from Microsoft, please confirm you are on version 2026.2. Microsoft confirmed that the Fix with the update has been rolled out to the US this morning (Sunday June 14, 2026). I was able to test multiple scenarios. Here is a summary of my testing and cases with screenshots on how I was able to fix any issues I experienced. I will keep monitoring my flows for any errors. Connections created Comment If working If they are broken Pre June 3 before any issues stated, Version 2026.1 or older By stroke of luck if you did not touch any connections these should re-authenticate with no issues. For possible issues and fixes refer CASE 1, 2, & 3 Should continue to work Try not to reconnect at first, instead try this: Edit the flow that is failing the flow should fix any errors, then exit the flow without saving. If 1 doesn’t work then try changing connection back and forth on actions that are in error state. Try reconnecting existing connection or Switch accounts Using the workaround posted above   (between June 3-9) These connections created using the new Multi-Authentication in 2026.2 before Microsoft roll-back on June 8-9 These connections authenticated through both OAuth2 and API Key Should automatically start working. Refer Case 4 Check when the start working Try editing the flow (don't make changes) Save. They should start working After the roll-back (2026.1) These are essentially same as the last release if you created them after the roll back (between June 9 - 14ish) and only saw single-auth to connection These should continue to work. Refer CASE 1-3. Lucky Try reconnecting or switching account, They should show the sign-in dialog Case 1 Old connection Pre June 3rd that I reconnected after the roll-back (after June 9). The flow is working as expected but when I edit the flow I see this it is in the error state FIX Open the flow. Open the action with error Click change connection Select a different connection Re-select the original connection. Save the flow CASE 2 The Flow was failing with a time out error for no real reason. This is using the connection created after roll-back on June 9 (2026.1) Open the flow in Edit mode to show no errors then closed the flow without saving fixed this issue. If this doesn't work try saving.   CASE 3 If you see your connection is still connected but when using it in a flow throws following error. OR FIX Make sure you are not logged in to ArcGIS Online in another tab (so the reconnecting won't pick up the log-in details from local storage without asking you to log in), if in doubt use a incognito window to log into Power Automate. Open Connections dialog To find the connection associated with a flow click on 3 dots in front of the connection and click View Properties Check the flow(s) using that connection and confirm it includes the flow you are fixing Click Reconnect should open sign in dialog If you don't see Reconnect active choose Switch account. CASE 4 This connection created using the workaround in this post with 2026.2 multi-auth update before Microsoft rolled it back. (between June 3 - 9) Both Connections created using connection type OAuth2 and API key started working automatically with no intervention at around 8:20AM EST on Sunday, June 14th Flow started working automagically and you don't have to do anything else If the connection failed then try fixes in Case 1-3 with reconnecting being the last Find out when they started working Open the flow Under run history  click All Runs Filter only failed runs using the dropdown on the top right corner. See all the runs that failed. See example below   I hope this helps. Please let me know if you are experiencing other issues that are not fixable.  Thank you everyone for their patience.  ... View more