✅Resolved: Authentication Issue with ArcGIS Connector (Release 2026.2)

[AkshayHarshe]

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:

1. Open any flow that is not working.
2. Select an ArcGIS action.
3. Click Change connection on the left pane.
4. Click Add New.
5. Choose ArcGIS Online User Credentials in the dropdown and provide a meaningful connection name.
6. Sign in to your ArcGIS Organization.
7. Update all ArcGIS actions and triggers to use the newly created connection.
8. If other flows are using the same connection, update those as well and save each flow.
9. 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

1. Open the flow.
2. Open the action with error
3. Click change connection
4. Select a different connection
5. Re-select the original connection.
6. 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

1. 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.
2. Open Connections dialog
3. To find the connection associated with a flow click on 3 dots in front of the connection and click View Properties
4. Check the flow(s) using that connection and confirm it includes the flow you are fixing
5. Click Reconnect should open sign in dialog
6. 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

1. Open the flow
2. Under run history  click All Runs
3. Filter only failed runs using the dropdown on the top right corner.
4. 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. 

[RachelAbernethy]

Thank you so much @AkshayHarshe for the updates and support - I will check the flows in the environment we are working in today and share any feedback here.

Thanks
Rachel 

[ISP_graynic]

@AkshayHarshe our flows are not working again this morning and causing Authentication errors when running. This is with the ArcGIS Connection that was updated following the workaround instructions last week when things first broke. When I went to "re-connect" this time, it gave me a new notification/message that I hadn't seen before and after proceeding through that it re-connected and I was able to re-run it. I'm hoping this is the last and it doesn't lose connection again as we have several critical flows that keep breaking with Connector changes. 

[Jean-PhilippeVandal-Labrecque]

The ArcGIS connector authentication issue appears to be resolved and the API connection is now working. However, the Get attachment content action still fails, preventing the flow from processing and transferring attachments to SharePoint. Issue remains unresolved.

[erica_poisson]

I was able to use the "Switch account" option, which is now available when I look at the ArcGIS connector under the "Connections" menu. My ArcGIS token refresh flow then ran for the first time since last week. 

Hopefully this solves the issue. Do you know if this is a long-term fix, or if this issue will pop up again when Microsoft re-releases 2026.2? 

[TL2]

Ever since the roll back our connections have been terrible, they keep failing even after we switch accounts.

[Jamie_Leitch_CNF]

A new connection I created last week seems to be working, but when I create a new connection, the connection gets created but any flow that uses it produces the invalid token 498 error.

[MichaelPierceVAIDSP]

This morning, all connections went bad - refreshing them only keeps them active for a very short time - 10-15 minutes before failing again.

This is a train wreck - incredibly frusturated that this has been impacting our production systems for over a week now.

[Theisen]

@AkshayHarshe I am still not seeing this update in my current flows. I still see the same error message and when I create new flows with the arcgis triggers, I don't see half my layers (which v2 fixed). I only see layers up to ones that start with "F". Are there plans to re-instate the "My Content" and "My Organization" parameters?

No Reconnect option. Seems like all my flows using this connector are dead and need to be completely recreated. 

[JamesWheaton4]

These updates and roll backs keep making things worse. what are yall doing over there....stop it

[ISP_graynic]

We are getting this error now. We have several public safety flows that are broken and need to be running. Can ESRI dedicate additional resources to this?

Fetching data from www.arcgis.com failed. This is usually caused by an invalid authentication token that has expired. Please reauthenticate to continue. Error message: undefined 498: Invalid token. Upgrade

[Willie_C]

Yesterday's update seems to fix the issue for my GCC tenant. I can see the switch account option and flow were actually running late yesterday afternoon and I've been rerunning some of the flows which failed previously, and they all ran successfully without issues. 

[JamesWheaton4]

Also, can you please do these updates on a Monday or Tuesday instead of breaking everything before the weekend. 

[ISP_graynic]

Too add on top of all these issues, is anyone else not seeing their Webhooks in the"Settings" page for a survey on the Survey123 website? The flow is active and has active connections to this survey but the Webhooks section seems to have disappeared all of a sudden and I can't update the webhook settings?

[JamesWheaton4]

JacobMyers said it changed his webhook settings here: https://community.esri.com/t5/arcgis-connectors-for-power-automate-questions/power-automate-connecti... not sure if its related

[SharonUngerer_DNREC]

As of this morning this fix is no longer working. After I update the connection by adding a new one, publish, and go back to My Flows page I am hit with the error below: 

There's a problem that needs to be fixed to trigger this flow. To see more details, open the Flow Checker.  

I am using the ArcGIS - When a survey is submitted trigger.  I have the government suite of Office 365 and we use OKTA for IAM.  This flow is using an ArcGIS Online account using the same email/login as my Office 365 account. 

Essentially I am in some loop where I update the trigger and its fine but after i close the Edit screen for that flow the trigger is broken again. I can go back in and add a new one. But its broken as soon as I go back to my flows. I have 3 duplicated connections now because of this and flows actively failing. 

[ISP_graynic]

Created a new copy of the flow and re-connected the ArcGIS Connector which seems to bring a new webhook in and the Settings page is showing webhooks now. Not sure what that was about but with all the changes going on wouldn't be surprised if it was related. Thanks @JamesWheaton4!

[JacobMyers]

@JamesWheaton4 @ISP_graynic I might be wrong but this seems to be tied to the 404 error, where it completely breaks your webhook. It hasn’t happened to any of my flows yet, but it has happened to my colleague. When you fully create a new connection and redirect your triggers to that new connection, you’ll need to reconfigure your webhook settings back to their original state (for example, enabling triggers to fire on edits). This also forces users to download a new Survey update in Survey123.

[AkshayHarshe]

Thanks for all your comments. Let go through these scenarios and see what I can find. I am certain that this morning the Reconnect and Switch account buttons are available on my disconnected connections in my environment but fix is still not rolled out so. Clicking them will open up the sign in page which will authenticate and work. I would recommend waiting (if that is an option for you) until the fix is rolled out to avoid additional work (if any).  According to MS the global roll-out takes 2-3 days for urgent pipelines such as these.

[GIS_Admin]

Sent

[RachelAbernethy]

Thank you @AkshayHarshe. A colleague of mine updated her connections via the "Switch Account" option but the flows began to fail again after 20-30 minutes. I decided to hold off on any changes in my environment and will continue to wait until the fix is rolled out. It would be great to be kept up to date of any updates tomorrow or at the start of next week.

Thank you

Rachel 

[AkshayHarshe]

James, I understand you sentiment but given the scale of the impact this wasn't an option.

[NICK_COG]

After changing all of my connections the day this was posted, I am finding myself having to change the connection to any flow that I need to edit.

Any flow that I can leave as is, still seems to be sending emails up until 13 minutes ago. But I have just coincidentally had three requests come in for updated logic in some of our flows, and I cannot do anything until I cchangethe connection. Here is the error I am receiving on the brand new connection from earlier this last week.

Failed to retrieve dynamic outputs. As a result, this operation's outputs might not be visible in subsequent actions. Error details: The dynamic operation request to API 'arcgis' operation 'WebhookPayloadSchema' failed with status code 'Unauthorized'. This may indicate invalid input parameters. Error response: { "error": { ------- "message": "The response is not in a JSON format.", "innerError": "Cannot read server response." } }

[AkshayHarshe]

@SharonUngerer_DNREC I am certain that the fix isn't yet rolled out to North America. so you are probably experiencing the breakage that happened after MS's roll back.

[KevinBerger5]

Hopefully the June 2026 ArcGIS Online update will be tested with the updated Power Automate, so we all do not have to go through this again in another couple of weeks.

[TL2]

Looks like the "New" connections made after the release need to be refreshed every 30 minutes.  I have a flow that alerts me when the connection is down and that's my pattern.  We have many important flows so I have been refreshing every 30 min.  Hopefully we get the patch soon.

Oh well, these things happen.  Thanks for the consistent communication on the matter.  ESRI can buy me a beer at Dev Summit 27 for this headache.

[RachelAbernethy]

Thank you @AkshayHarshe and everyone else for your comments in the past day.

As a recap, we did change our connections last week so those broke again this week when the version was rolled back. We haven't made any changes again this week in the hope that another update might fix the connections we now have in place.

We have just created a new flow to check the version, based on the steps in the article above, and can confirm that we are still on 2026.1.  We're based in Ireland. 

We will check again on Monday but at that stage we will need to take some sort of action to get the environment back up and running again. 

[Theisen]

Could you share this flow that notifies you when your connection is down? That would be very useful. Thanks. 

[JacobMyers]

We updated our refresh flows to fire every 29 mins and send an email if the connection failed. Sadly it was not solving the issue and still failing - We even switched it to every 10 mins and still no luck 😞 Hopefully we all get a beer after this week of fun haha

[MichaelPierceVAIDSP]

Do you have any updates for us? My connections are dropping every hour despite being recreated/reauthenticated - across 3 tenants and 20+ flow - a system that keeps our CRM and Workforce in sync is a mess. Day 9 and we cant clean up this mess fully until we have a working pipeline again.

[JacobMyers]

Update! We switched it to every 5 mins and that seems to be the sweet spot for our environment  😎

[AkshayHarshe]

I am testing the Connection being dropped every  20 min - 1 hour so far my connections are working. I think this is related to the main issue as the token exchange mechanism hasn't changed. 

If you don't already have something like this set up. Maybe try following

1. Create a New flow on Recurrence to run every say 20 minutes
2. Add Get data from Feature layer action. Use the connection you have authenticated. Configure the action to return 1 or 2 records using "Result record count" option.
3. Repeat step 2 for every connection you want to authenticate. 

See if this helps.

I have updated the Main text for additional information. I will post another update soon. And I will have to source that beer from Microsoft! Lets name it MS I-PA

[KevinBerger5]

This does not work. The flow ended up failing after about 30 minutes. I even reduced the recurrence time to two minutes.

[AkshayHarshe]

Thanks for your comment. What is the error that you are getting? 

[MichaelPierceVAIDSP]

Within the first hour, it failed. We run enough transactions all day long that I was not convinced this was going to help. We even see cases where there are Successful results in between Failed ones. So the token issue seems to fade in and out. We're trying to lower the timer to 10 minutes, but again, we're running API calls almost non-stop all day long and see this issue.

[MeganHicks]

Hi Jacob, would you be able to share more about how you set up a flow to refresh the connection? This would be very useful for my organization too! 

[KevinBerger5]

Does the error even matter? As soon as refresh the connector it the flow works again. So, using the flow to refresh the connector does not seem to work.

[TL2]

I set up a Get Item Information to run every 2 minutes and it failed on the 15th run.

[AkshayHarshe]

@KevinBerger5 yes, the error matters for us, we can try and look at the telemetry to see compare that and see if there is a different issue than this one. 

[AkshayHarshe]

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.

[MitchellGrafstein]

---

@AkshayHarshe wrote:

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.

---

Does this mean that the rest of the regions are still waiting on the update and should continue to expect dropped connections?  Did your timed flow continue to keep your connection alive?  

[AkshayHarshe]

If this is intermittent like this this could still be related to existing issue at hand. The rollout hasn't been started to US regions yet. I can't say for sure but Power automate server must have load balancers to send load to different stations which could be the cause of intermittence. Unfortunately, test my flows are either broken or working. 

Once refresh token is issued by ArcGIS online it is valid for 2 weeks the connector just acts as a middle-man that routes these requests between Power Automate and ArcGIS Online. There is no reason for Power Automate loose the token(and connection) for 2 weeks once issued by ArcGIS Online. This is why it makes me think that it is still the same issue, and why I was asked to create a recurring flow like this could somehow circumvent any issues of dropped connection. Apologies if it hasn't worked for you.

[AkshayHarshe]

Microsoft l confirmed that these regions should see the update and I can confirm that for Canada. Unfortunately for folks experiencing this issue it appears to be the case until the update is rolled out to the US. I am monitoring this over the weekend and I will keep everyone posted. Please notify me in a DM if your connections are still doing this after the update roll out is complete.

Question for everyone: this happens even if you create a new connection or only for existing connection? what is the error that you get? I am trying to isolate issue of dropped connections to see if it is different than this so this info will surely help. My flows with different frequency and different connections are either working or failing.

[MichaelPierceVAIDSP]

The only thing that works is if I manually Switch Account every 15 minutes.

[rlarose1]

I'm having trouble keeping track of which connection is which at this point but the one that fails for sure every 30 minutes is my "named" connection that I created after things initially failed and before the roll back. It gives this error if I don't manually reauthenticate (using it in a flow doesn't work to refresh it):  Failed to retrieve dynamic inputs. Error details: 'The dynamic operation request to API 'arcgis' operation 'QueryFeaturesSchema' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: { "message": "Fetching data from www.arcgis.com failed. This is usually caused by an invalid authentication token that has expired. Please reauthenticate to continue. Error message: undefined 498: Invalid token.", "success": false }'

[AkshayHarshe]

@rlarose1 Thanks for sharing the error. I understand, I created an excel to keep track of all my connections and running tests. 

the one that fails for sure every 30 minutes is my "named" connection that I created after things initially failed and before the roll back. It gives this error if I don't manually reauthenticate (using it in a flow doesn't work to refresh it):  Failed to retrieve dynamic inputs

I believe when the Multi-auth was rolled back by MS, the older version is probably authenticating with a newer connection but failing to refresh the token.  All my flows created with the original workaround are no longer working. The best case scenario is that this gets resolved on its own. I can't be certain without testing in our main env after the update.

[Richard_Caprio]

Hello, just reaching out prior to the Monday morning start....

Without refreshing any existing ArcGIS Connections since the end of business on Friday, we are seeing flows successfully running today (Sunday 5PM New Jersey EST).

Any word from Microsoft regarding what may have been rolled out?

We will re-evaluate in the morning and can provide more details.

[AkshayHarshe]

Hello Everyone. First of all thank you for your patience. 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

1. Open the flow.
2. Open the action with error
3. Click change connection
4. Select a different connection
5. Re-select the original connection.
6. 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

1. 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.
2. Open Connections dialog
3. To find the connection associated with a flow click on 3 dots in front of the connection and click View Properties
4. Check the flow(s) using that connection and confirm it includes the flow you are fixing
5. Click Reconnect should open sign in dialog
6. 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

1. Open the flow
2. Under run history  click All Runs
3. Filter only failed runs using the dropdown on the top right corner.
4. 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. 

[ISP_graynic]

@AkshayHarshe thank you for your frequent updates on this issue, it was good to know ESRI was working on this from the start of the issue!

I re-connected our connections after the rollback from 2026.2 to 2026.1, and they seemed to have been working fine over the weekend so hopefully we are good to go now!

[Annie_K]

@AkshayHarshe Are there any defects in the Esri system that I can attach to an existing case that presents with these issues?

Thanks!

Annie K (Esri Support)