Edit query string and user identity mapping rules for Copilot connectors

Admins can now edit query string and user identity mapping rules directly in connector settings without opening a support ticket.

Details:

What changed: Query string parameters and user identity mapping rules are now editable after a connection is created. Admins can update them in the Microsoft 365 admin center under Settings > Search & intelligence > Data sources, then select the connection and edit its configuration. Previously, these values were fixed at connection setup and changing them required support intervention.

Why: Source systems change, teams re-scope projects, filters need tightening, and identity mappings drift as directory attributes are updated. Locking these rules at setup meant every adjustment became a support request, leaving connections stale or over-scoped in the interim.

Try this:

1. Go to the Microsoft 365 admin center > Settings > Search & intelligence > Data sources.
2. Select your connection (for example, Azure DevOps or ServiceNow) and open its configuration.
3. Update the query string or user identity mapping rule and save.
4. Confirm the change took effect on the next crawl and spot-check results for an affected user.

Why this matters: Access scope and content scope are now self-serve. Admins can correct a mis-scoped connection or a broken identity mapping in minutes instead of waiting on a support cycle.

Business impact: Faster remediation when a connection surfaces content to the wrong audience, fewer support tickets per connection, and configuration that keeps pace with changes in the source system—all of which support access-governance and compliance commitments.

Personal impact: You fix scoping and permission-mapping issues yourself, on your own schedule, instead of filing a ticket and waiting for someone else to make a change.