I've built this flow several months ago that has been working reliably for most users until this morning. The flow is triggered from a PowerApps which then executes a stored procedure in SQL and then takes that data and populates a Word Template (there's a lot more going on there but that's the short version). It's at this step where I get the error message:
Solved! Go to Solution.
Thank you @v-bofeng-msft for your help. I'm not able to use the Run Only Users as this is triggered by a PowerApp button. Through some more testing on our end we discovered it was related to a recent change in our Multi Factor Authentication (MFA) which explains why it was only affecting some of the users. As the token expires and they are forced to reauthenticate, users are now able to run the process without issue.
For testing purposes in case others run across this issue, having the user try to open the PowerApp and run the flow while in private/incognito mode let us narrow down that the issue had to deal with MFA.
Hi @BegeNCSU :
4XX errors are usually due to authorization issues, I have two solutions for your reference:
Solution1:Share the template file with your users.
Solution2:Let users use your credentials to use this action.For example:
1\my flow
2\Add all users as run-only users
All users will use designated credentials to access Word Online
In addition ,if the problem can not be solved,please consider creating a support ticket.
Best Regards,
Bof
Thank you @v-bofeng-msft for your help. I'm not able to use the Run Only Users as this is triggered by a PowerApp button. Through some more testing on our end we discovered it was related to a recent change in our Multi Factor Authentication (MFA) which explains why it was only affecting some of the users. As the token expires and they are forced to reauthenticate, users are now able to run the process without issue.
For testing purposes in case others run across this issue, having the user try to open the PowerApp and run the flow while in private/incognito mode let us narrow down that the issue had to deal with MFA.
User | Count |
---|---|
5 | |
5 | |
4 | |
2 | |
2 |