Power Automate: The credentials for this connection do not have access to. Please try using a different location or account

In this Power Automate tutorial, we will see how to fix this error: ‘The credentials for this connection do not have access to‘, please try using a different location or account’.

Recently, when I was creating a connection with the File system actions in Power Automate, I came across an error ‘the credentials for this connection do not have access to ”, please try using a different location or account’. The error states that the credentials are incorrect, so an authentication issue is occurring’.

Power Automate The credentials for this connection do not have access to

So, in this Power Automate tutorial, we will see how to solve File system connection errors.

The credentials for this connection do not have access to ”, please try using a different location or account in Power Automate

Here we are creating an Automated cloud flow that we will trigger automatically when a file is uploaded to the folder, and then it gets created in the local drive using the Create File action -File system.

To use the File system action we have installed and configured an On-premises data gateway. Then, we need to create the connection for the File system action in Power Automate like the below:

Power automate File system credential error

Once I created the connection, I used the Create file action from the File system in Power Automate flow.

See also  Power bi date format (Various examples)

Below, you can see my flow:

The credentials for this connection do not have access to. Please try using a different location or account

When I ran this flow by uploading a file in the Folder, I came across File system-action error 403: “The credentials for this connection do not have access to ”, please try using a different location or account’

The credentials for this connection do not have access to. Please try using a different location or account

In the next section, we will see why this error came and how we can fix this File system credential error

Solution- ‘The credentials for this connection do not have access to ”, please try using a different location or account’ in Power Automate

Here first, let’s understand why we face this error in the Power Automate File system connection error.

This connection error will come when you provide the wrong Username, password, and gateway. We must check these 3 parameters are correct.

Now, let’s understand where I have made the mistake. In my case, I have provided the correct username and gateway, but while providing the password, I am providing the pin (pin I am logging in with my desktop). I should provide the password.

As my desktop is running with Windows 11 Pro, you can also check other OS in the same way. Check whether you are providing the PIN to log in or a password to log in to the Desktop.

For this, navigate to the settings option of the desktop and then navigate to the Accounts ->Sign-in option. Here, you can check this option ‘For improved security, only Windows Hellow Sign-in Microsoft accounts on this device (Recommended)’ under additional settings is toggled off or not.

Problem connecting to File System in Power automate

If this option is not toggled off, then you are using PIN to log in, so toggled off, then close that window and open it once more. You can see the Password option is enabled.

Problem connecting to File System in Flow

Expand the option, and you can see the Change button; from here, change the password and provide the same password while configuring the connection.

Problem connecting to File System in Microsoft Power automate

Now, if I run the flow, my flow runs successfully without a File system connection error.

Problem connecting to File System actions in Microsoft Power automate

This is how I have resolved my file system connection error in Power Automate.

See also  Power bi create a date table - Complete tutorial

Conclusion

In this Power Automate tutorial, we saw how we can fix the File system connection error: The credentials for this connection do not have access to ”, please try using a different location or account.

You may also like:

>