ServiceNow connector (Microsoft Entra ID User Login) prompting end users for manual connection setup instead of SSO

Yes, this is generally expected for the ServiceNow connector when Microsoft Entra ID User Login and end-user credentials are selected.

That authentication type creates a non-shareable connection. Each user must create their own connector connection, including supplying the ServiceNow instance name and resource URI, before signing in. Teams SSO authenticates the user to the Copilot Studio agent; it does not automatically create or configure the user’s ServiceNow connector connection.

Tenant-wide admin consent can prevent users from encountering an “Admin approval required” or consent error, but granting it does not normally replace the connector setup page with silent SSO.

Verify the following:

1. The ServiceNow resource app is configured as documented, and the Microsoft-owned ServiceNow Connector application ID has permission to access it.
2. The resource URI entered by users matches the identifier of the ServiceNow representative Entra application.
3. The token claim used by ServiceNow, such as UPN, matches the corresponding ServiceNow user field.
4. The agent uses Authenticate with Microsoft, is republished to Teams, and is tested in a Teams 1:1 chat.

Therefore, the manual connection page itself does not indicate missing admin consent. Investigate consent only if users receive an Entra consent or administrator-approval error after selecting Sign in.