power automate error with microsoft forms

[Anonymous]

Hi, at my job we use a microsoft forms with power automate to submit details regarding new hire and term details for employees to send auto email to the IT vendor we use to create 365 account or terminate it if our employee leaves.

all of a sudden the power automate does not function we use the template "notify me when a student completes a quiz" for this.

it has worked compltely fine, and nothing has been changed...

we receive this error.

UnauthorizedAccess to CDB. Inner Message: {"error":{"code":"OperationForbidden","message":"Unauthorized Access","innerError":{"code":"UnauthorizedAccess"}}}

any ideas???

[gabibalaban]

Hi @Anonymous ,

Please check which user connection is used in Forms trigger. My first thought is that the user don't have rights to edit the Forms. 

[Anonymous]

I have tried select both ytsu who is the original owner of the power automate flow.

and myself being selected. either one of us selected does not work

I have to see if she is the owner of the micorosft form as well... 

This automation worked with me just until this past week.

Error happens at 2nd step "Get Response Details"

Other error is similar to the original one.

{
  "error": {
    "code": "707",
    "message": "UnauthorizedAccess to CDB. Inner Message: {\"error\":{\"code\":\"OperationForbidden\",\"message\":\"Unauthorized Access\",\"innerError\":{\"code\":\"UnauthorizedAccess\"}}}",
    "@ms.form.error.type": "ExpectedFailure",
    "@ms.form.error.customizedMessage": null
  }
}

[Mari]

Hi @Anonymous What happens if the affected user account tries to access the form from MS Forms directly?

[cspears]

Has this issue been resolved? I am encountering the exact same issue.

[colinharvey]

Also having this issue, connections are known to work and the shared Forms tied to the Flow are missing from the app.

[PatCarriere]

Looks like an outtage or a bug, because it's happening to me too since this morning only. I'm using this since more than a year without any modifications from me.

[Anonymous]

I am also experiencing this exact issue starting today. 

[sarah612]

I also had this error on Monday, but since I've had some successful flow runs. I suspect it was a glitch on Microsoft's end.

[chrishawker]

Has anyone fixed this issue?
Im having the same thing happen to me and havent seen a thread with a fix yet.