Microsoft Flow - SharePoint Connection - Unauthorized?

[davidlist87]

I have recently built a flow the gets all MS Form responses and puts it into a SharePoint List.

After heaps of testing and countless successful flows it all of a sudden decides to make the connection to SharePoint "Unauthorized".

The funny this is it is only intermittent. Most of the time failing but some times running fine.

I have tried the following;

• Deleting and creating a new connection.
• Copying the flows.

I did recently change some the view setting in the list but I'm sure this would not explain this failure. 

Oh and I am the owner of the SharePoint site.

I'm a little lost without any information regarding the failure.

Any Ideas?

[andrew_blubase]

I am experiencing this same issue today. Two different user accounts, both with site collection admin access to the SharePoint site.

I can create a connection to the site I require when creating the Flow. However, when testing/running the Flow, the Unauthorized message appears but with no further details. Deleting and re-creating, or just adding new connections makes no difference.

Editing the Flow exposes the error: Some of the connections are not authorized yet. If you just created a workflow from a template, please add the authorized connections to your workflow before saving.

Will attempt to contact Microsoft Support.

EDIT: This is occurring on multiple tenants

[Anonymous]

We have been experiencing the exact same issue for several days now.  

[martinav]

Finally! Someone else reports this issue.  I have been having these authority errors all week.  Tickets to MS support have not yet resolved or explained the issue.  This particular flow has been working perfectly for months.  Now it has issue.  Ref: SR number 119043023002044 

[Anonymous]

My organization is seeing the same and have raised a ticket with Flow support and through MS admin center - no response yet. Most Flows are fixed now except one or two. This seems like an outage to me that I am very suprised that they have not acknolged that fact or placed the 365 Power platform in the Service Health yet. Microsoft we need to be alerted to the fact about outages as many business critical functions run on theses!!!

[martinav]

@Anonymous ,

When you say most of  your flows are "fixed", what do you mean?  Was something done to them that made the problem go away?  Or, did the problem just go away for a moment?  That happened to me yesterday when MS was on the phone with me.  We were messing around with a couple of flows, and they started working again.  I asked what they did to make them work, and they couldnt answer.  I think they just started working, but not as a result of the playing around with them.  That was confirmed today due to the same flows failing in the same manner once again.  

It seems like the problem comes in "waves".  Some flows fail 100% for a period of time, then start working again.  Others have the issue just now and then.  Some dont have an issue.  

I see this as completely an outage issue.  I will not consider this manner closed until I see NO errors of this type for a week.

[Anonymous]

@martinavexperiencing the same.

[beardmask]

I am also experiencing this issue.  I have gone Flow crazy creating all of these new features for our SharePoint implementation.  I guess it's good I haven't told anyone so they are none the wiser to these new Flows.

[Anonymous]

Microsoft says: “the issue you are experiencing is due to an unexpected defect surfaced on our end  which caused service outage System. We regret the inconvenience caused. Our product team is actively working on the fix. We will reach out to you to confirm resolution once the issue is fixed. Our sincere apology for the delay and inconvenience caused by this outage. Please send the flow run and url and also screenshot. “

So you may want to contact them through Flow support to provide the url information?

[martinav]

@beardmask ,

Myself, and I'm sure others will agree, this will not be the last issue like this.  I have been seeing about one issue a month that has taken down some or all of my users.  Issues like this tend to stick around a few days, then get resolved.  The frequence of these issues is degrading the confidence of my users.  I am VERY concerned that their appetite for giving grace for these issues will end shortly.  It was acceptable to a degree during my development... but these issues are not development issues, but core issues with the system.  These do not seem to be things that can be eliminated by technique.  If reliability does not improve QUICKLY... We may find ourselves ditching this solution completely.  

[davidlist87]

Thanks very much for the update @Anonymous

[davidlist87]

I have to say I am getting increasingly frustrated with this bug.

The intermmittent failures causing massive headaches to our operations. The only real insight that I can currently attain is that it only seems to happening to the "Sharepoint" Connector. 

[davidlist87]

It apprears Microsoft Flow team are well aware of the issue. Screen shot from the Flow - Support page:

[martinav]

@davidlist87 ,

I feel your pain.  My users are starting to raise concern.  This is not good, and this is definetely putting this development in jeapardy.  If there are enough interruptions, they will pull the plug on this fast.  This is the second issue with big downtime that has occurred in the last month.  I really need some consolation from Microsoft about these issues, or this is going to come to an end.  I cannot personally stand behind it either.  Its also my reputation on the line here.  I'm supposed to deliver this system, and I am also responsible for its effectiveness.

Good luck, David.  I hope for both of our sakes that these issues workout quickly and decrease in frequency.

[andrew_blubase]

No additional updates from Microsoft for me, but both tenants that were having issues yesterday now appear to be working currently.

What about everyone else?

[Anonymous]

Still having issues, here. Have a support item out to Microsoft, but no response yet.

[andrew_blubase]

Does anyone see Flow or PowerApps listed in the Service Health listing in the Office 365 admin center?

I find it strange that they list pretty much everything else but not these two. Granted you can see the support issue on the Flow support site, but this isn't tenant specific.

My support ticket just says engineer assigned and will call you soon. 

[Anonymous]

I have been rerunning the flows that failed in our environment, and so far they are all running successfully.

[Anonymous]

Resolved for my organizations and re-submitting Flow runs are working again. Also from Microsoft saying it is resolved:

"Hope you are doing well today.

So there was an outage for the SharePoint Connection and that might be the reason for the issue you are facing with the SharePoint Action card, Today we have received an update from our Product team that the issue has been fixed and the SharePoint connection should work fine.

Please re-test the flow in which you are having the issue and let us know the result, if the issue still persist we can have a call and troubleshoot the issue."

[Anonymous]

Still broken for me when I try running the "Request Sign-Off" built-in Flow from within a SharePoint library:

The specified delegated auth resource could not be connected to or returned an invalid response and so cannot be applied to the flow. Resource: '{"accessDefinition":{"sharePointBasePermissions":[{"high":0,"low":15}]},"delegationSource":{"delegationService":"SharePoint","contractVersion":"2017-12-01"},"delegatedAuthResource":{"resourceCollection":"https://mytenant.sharepoint.com/sites/mysite","resourceId":"guid-of-the-sp-library"}}'