Hi Damian,
What you're seeing is expected behavior with the standard ServiceNow connector in Copilot Studio.
The built-in ServiceNow connector uses the OAuth 2.0 Authorization Code flow, which requires an interactive sign-in. Even when using a dedicated service account, the connector redirects to ServiceNow's oauth_login.do page to authenticate the user session and obtain an authorization code. Because this flow is designed for delegated user access, it does not support silently authenticating with a non-interactive service account through the out-of-the-box connector configuration.
If your requirement is true machine-to-machine (service-to-service) authentication with no user interaction, you'll need to use an alternative integration approach rather than the standard ServiceNow connector.
Common alternatives are:
Option 1: Use a Power Automate Cloud Flow with an HTTP Action
Create a Power Automate cloud flow that can be called from Copilot Studio.
Use the HTTP action to call the ServiceNow REST APIs.
Handle authentication in the background by obtaining an access token from ServiceNow and then calling the required endpoints.
Option 2: Build a Custom Connector
Create a Custom Connector that wraps the required ServiceNow REST APIs.
Configure authentication based on the OAuth capabilities supported by both your Power Platform environment and ServiceNow configuration.
Use the connector from Copilot Studio instead of the standard ServiceNow connector.
To summarize:
Standard ServiceNow connector → Interactive login required (Authorization Code flow).
Silent service account integration → Use an alternative integration pattern such as a Power Automate cloud flow or a Custom Connector designed for service-to-service communication.
I hope this helps clarify the platform behavior and gives you a clear path forward.
Please mark this answer as Helpful if it resolves your question. 🙂
