This usually isn’t an issue from the Power Apps side — it’s almost always related to ServiceNow configuration, especially when using Basic Authentication.
Even if the username and password are correct, ServiceNow will reject the connection if a few things aren’t set properly.
First, make sure Basic Auth is actually allowed in your ServiceNow instance. In many environments it’s disabled by default for security reasons. Check this in ServiceNow:
-
Go to System Properties → Security
-
Ensure “Allow Basic Authentication” is enabled
-
Also confirm there’s no policy blocking REST authentication
Second, the ServiceNow user you’re using must have the correct roles. At minimum, the account should have:
Without these, authentication may succeed internally but still fail through APIs.
Third, if your ServiceNow instance has MFA enabled, Basic Authentication will not work with the normal password. In that case, you must generate an API token / application password in ServiceNow and use that instead of your login password. This is one of the most common reasons the connector keeps deleting itself with “user not authenticated”.
Also double-check the instance URL — only enter the instance name, not the full URL.
For example:
✅ dev12345
❌ https://dev12345.service-now.com
Finally, if your ServiceNow team has restricted outbound integrations, confirm that REST API access is allowed and not limited to IP whitelisting.
