Execute Excel Script - Unauthorized

[gersontun]

Hello,

In order to accomplish a couple of things I cannot do directly in Power Automate, I started executing regular expressions using the "Run Excel Script" activity. It had been working fine, but on Monday it started to fail. This execution of the Excel script is inside of an "Apply to each" activity.

What I've done so far to try to fix it:

1. Removed default concurrency to the trigger, so I make sure this process is not executing multiple times in parallel.

2. Removed default concurrency of the "Apply to each" activity, to make sure the process is not trying to execute the script multiple times at the same time.

3. On the Run Excel Script, I've played with the Retry Policy, with no luck.

The issue persists.

The weirdest thing is that this issue might or might not happen on the same execution and within the apply to each.

The Error:

In the apply to each activity:

Execution number 5 failed, number 6 succeeded and number 8 failed again.. and so on.

Failed:

Succeeded:

Failed:

This is the configuration of the RunScriptPageNumber:

Hope anyone here can help!

UPDATE: Now that I am editing the flow, the issue started appearing on the top like this:

It seems like the file was not available or I didn't have permissions on the file.

The excel file is saved and closed, no one else is using it.

[mayanklk]

Tentative ETA?

[Yutao]

Update: we are still working with our partner teams to track down the issues and possible solutions. Based on the information we have collected so far, we suspect the issue might be related to this admin settings: SharePoint and OneDrive unmanaged device access controls for administrators - SharePoint in Microsof...

If possible, can you folks help to reach out to your SharePoint admins or tenant admins and check if the particular policy (block access from unmanaged devices) mentioned in the above article is turned on or off, or if they are aware of this policy at all?

Thanks again for your patience and support!

[mayanklk]

Lot of teams have started observing issues from 10 Jan'23. How come it is possible that policy is updated for each of them at same time. 

Also, we are able to view the script via SharePoint access but couldn't access it vis flow.

[himanshukukreti]

Facing the same issue since Yesterday. The run script action keep failing. with the below error

The dynamic operation request to API 'excelonlinebusiness' operation 'GetSingleScript' failed with status code 'Unauthorized'. This may indicate invalid input parameters.

[AnnR]

Same issue here since yesterday

[Muraligott]

We can see the scripts and was able to run them but when we try to run the flows which contains scripts this error is coming ..

[kinwong]

We checked with our tenant admins yesterday, the setting has no change, please see the attached screen shot.

[Yutao]

Thank you all for getting back with the admin settings info! It is super helpful for us to further investigate the problem.

Our hypothesis is that the failures might have something to do with this particular SharePoint admin setting. It seems that unfortunately Office Scripts would stop working if your SharePoint admin access control has turned on "Allow limited web-only access".

We are still working with our partner teams to identify why this suddenly started breaking Office Scripts. At the same time, since this is an organizational policy, please don't update it if you don't fully understand the consequences.

Also, just help to confirm our hypothesis, for folks whose scripts/flows are still working fine and are reading this, can you help to check your SharePoint admin policy and see what your setting is?

Thanks again for your support and patience!

[riverae]

Having the same issue today, I am able to run the script manually but not from the flow. @Yutao 

[ram_sathia]

@Yutao We have the same setting but still facing unauthorized while access office scripts from Power automate flow. These flows were just working fine couple of days ago

[Yutao]

Thanks for confirming, @ram_sathia ! Yes it seems if you have that policy "Allow limited, web-only access" turned on, your Office Script would stop working. But please don't alter that setting since that's your organizational policy.

[ram_sathia]

@Yutao strange as nothing changed recently and the flows were working just fine couple of days ago.

[Yutao]

@ram_sathia sorry for the frustration. That policy itself should not be the problem. I believe it must be something on our end and we really need to get to the bottom of it soon.

[Timmer2005]

I too am getting the same error. I have been trying to figure out what happened and then I found this thread. For me everything quit working with scripts through flow after I moved a file to a TEAMS files from my personal OneDrive files. I also am unable to use saved scripts in another file. When I click on use more scripts and select a script I own for a document I own, I keep getting error stating unauthorized. Thank you Microsoft for working on this to resolve as soon as possible. I know scripts has become a big part of our every day automation and I love it.

[Yutao]

Update: We have identified a potential fix. The rollout may take up to 24 hours to reach to all the regions. We will be closely monitoring the status and update back to the thread with any new information. Thank you all!

[Muraligott]

flows are working now.

[Captivebird]

It still doesn't work in China. Could you please let me know when it can be fixed? Thanks!

[lowbattery1997]

Same issue happens in this week 

Plz help deal with it soon!!! 

my flow is damaged 555555

[ram_sathia]

@Yutao We just tested one of the impacted flow and it ran successfully.  Can we get more details on what caused the issue?

[Yutao]

Update: As we haven't seen any failures of the same pattern in our logs in the past 12 hours, we believe the issue has been fully resolved now. If you are still experiencing the same authorization issue, please feel free to reach out.

Root cause: One of our dependencies made a change recently that turned out to be premature and introduced an unexpected side effect. This side effect had impacted how our service read the scripts from OneDrive for Business for users whose SharePoint admins have turned on the "Unmanaged devices" policy.

Fix: That premature change has been reverted.

We sincerely apologize for this outage and thank you for all your support and patience.