Microsoft is expanding the reach of Microsoft 365 Copilot with a new capability that could make it much easier for employees to find information scattered across different workplace applications. The company is introducing self-serve Copilot connectors, allowing users to securely connect supported external data sources, including Jira Cloud and Confluence Cloud, using their existing credentials and permissions.
The change is particularly significant for organizations where important information lives outside Microsoft 365. Instead of switching between Microsoft Teams, SharePoint, Jira, Confluence and other work applications, employees will be able to make eligible external content discoverable through Microsoft 365 Copilot and Microsoft Search.
The worldwide rollout is scheduled to begin in late August 2026, with Public Preview expected to finish by mid-September. General Availability will follow, beginning in mid-September and expected to reach completion by mid-October 2026.
What Are Self-Serve Copilot Connectors?
Self-serve sync Copilot connectors are designed to let individual users connect supported third-party work services to Microsoft 365 Copilot themselves.
The key difference is that users do not receive additional permissions simply by connecting a service. Instead, the connector works with the user’s existing credentials and access rights.
For example, imagine an employee who regularly works with Jira Cloud. Their projects, tickets, discussions and documentation may contain valuable information, but that content is normally separated from the Microsoft 365 environment.
With a supported self-serve connector, the employee can connect Jira using their own credentials. Content they are already authorized to access can then be synchronized and made discoverable through Microsoft 365 Copilot and Microsoft Search.
The same concept applies to services such as Confluence Cloud.
This creates a more connected search and discovery experience without requiring users to manually copy information between applications.
Why This Matters for Microsoft 365 Copilot Users
One of the biggest challenges in modern workplaces is not a lack of information. It is the difficulty of finding the right information at the right time.
Employees may have customer information in one application, technical documentation in another, project updates somewhere else and company resources inside Microsoft 365. Moving between these systems can slow down even relatively simple tasks.
Self-serve connectors are intended to reduce that friction.
Rather than asking, “Which application contains that information?”, employees can increasingly use Microsoft 365 Copilot or Microsoft Search as a starting point for discovery.
For knowledge workers, this could mean less context switching and fewer interruptions during the workday.
A developer might find relevant project information from Jira. A technical writer could locate documentation stored in Confluence. A project manager could discover information from connected work sources without repeatedly navigating between separate applications.
The broader goal is to make Copilot more useful as a workplace information layer.
Security Still Depends on Existing Permissions
Perhaps the most important aspect of this update is the permissions model.
Users connect supported external sources using their own credentials and permissions. In practical terms, the connector is not intended to give a user access to information they could not already access in the connected service.
That distinction is critical for enterprise deployments.
Organizations adopting AI-powered search and productivity tools need to understand not only what information can be discovered, but also who can discover it. The self-serve connector model is designed around existing user permissions, while administrators retain controls over connector availability.
However, organizations should still review their third-party applications, permissions structures and governance policies before enabling the feature broadly.
AI search can make existing information significantly easier to discover. That is valuable when permissions are configured correctly, but it also makes good identity and access management practices increasingly important.
Administrators Remain in Control
Although the new capability is designed to be self-service for users, Microsoft is not removing administrative governance.
Administrators can review and manage the connectors available through the Microsoft 365 admin center.
Organizations can decide whether individual connectors should be enabled or disabled. They can also stage availability for specific Microsoft Entra ID groups.
This gives IT teams several ways to approach deployment.
A company could choose to make a connector available across the organization. Another organization might first test the capability with a small group of employees before expanding access.
This staged approach may be particularly useful for enterprises with strict security, compliance or data-governance requirements.
It also gives administrators an opportunity to understand how users interact with connected data before making the feature widely available.
Jira and Confluence Are Important Examples
The inclusion of Jira Cloud and Confluence Cloud highlights one of the practical use cases for self-serve connectors.
Many technology organizations use Jira for issue and project tracking while relying on Confluence for documentation and knowledge management. Microsoft 365 may contain a separate collection of emails, documents, meetings and collaboration data.
Employees therefore have to work across several information ecosystems.
Connecting these sources to Microsoft 365 Copilot could make it easier to discover information across those environments.
Consider a project manager preparing for a status meeting. Instead of manually searching Jira for open issues and then switching to Confluence for technical documentation, they may be able to use Copilot to help locate relevant information from connected sources.
The value is not simply “more data in Copilot.” The real benefit is potentially less time spent searching for information.
Microsoft Search Gets More Important Too
The update is not limited to Copilot Chat.
Connected content can also become discoverable through Microsoft Search.
That matters because not every employee interaction with workplace information begins with an AI prompt. Traditional search remains an important part of how people navigate enterprise information.
By bringing eligible external content into the discovery experience, Microsoft is effectively making Microsoft Search and Copilot more useful as centralized entry points to workplace knowledge.
This could become increasingly important as organizations use more SaaS applications.
The modern workplace is rarely built around a single platform. Employees may use Microsoft 365 alongside Salesforce, Jira, Confluence, ServiceNow and numerous other specialized tools.
The more fragmented the technology environment becomes, the more valuable unified discovery can be.
When Is the Feature Rolling Out?
Microsoft has outlined a two-stage worldwide rollout.
Public Preview is scheduled to begin in late August 2026 and is expected to be completed by mid-September 2026.
General Availability is then scheduled to begin in mid-September 2026, with the worldwide rollout expected to finish by mid-October 2026.
Because rollout timing can vary between organizations and tenants, administrators should monitor the Microsoft 365 admin center for availability and configuration options.
What Organizations Should Do Now
Microsoft says there is no immediate action required, but organizations should use the rollout window as an opportunity to prepare.
IT and security teams should first review the available connectors and determine whether they fit the organization’s security, compliance and governance requirements.
The next step is deciding how broadly connectors should be made available.
For example, an organization might:
- Enable selected connectors for everyone.
- Disable connectors that are not approved.
- Pilot connectors with specific Microsoft Entra ID groups.
- Communicate the feature to employees who would benefit from it.
- Monitor connector adoption and usage after deployment.
This approach allows organizations to treat self-serve connectors as a governed technology rollout rather than simply another Copilot feature.
Compliance and Governance Considerations
The introduction of third-party integrations naturally raises compliance questions.
Organizations should understand what external services are being connected, what information users can access within those services and how existing permissions are structured.
Because users can connect external sources with their own credentials, identity management remains an important part of the overall security picture.
Administrators should also consider internal policies around third-party applications, data classification and information discovery.
The good news is that Microsoft provides administrative controls for managing connector availability. Organizations can use these controls to determine which connectors users can access and whether availability should be limited to particular Microsoft Entra ID groups.
In other words, self-service does not have to mean uncontrolled.
A Step Toward a More Connected Copilot
Microsoft’s self-serve Copilot connectors represent a broader shift in how workplace AI assistants are expected to operate.
The future of enterprise AI is unlikely to depend solely on information stored inside one platform. Employees expect AI tools to help them work with the information they already use, regardless of which business application contains it.
By allowing users to securely connect supported external sources while maintaining administrative controls, Microsoft is attempting to balance convenience with organizational governance.
For employees, the biggest attraction is straightforward: find information without constantly switching applications.
For IT teams, the challenge will be ensuring that convenience does not come at the expense of security, compliance or appropriate access controls.
As the feature rolls out worldwide through September and October 2026, organizations using Microsoft 365 Copilot should watch the Microsoft 365 admin center, review available connectors and decide how the capability fits into their existing governance strategy.
The self-serve model could ultimately make Microsoft 365 Copilot more useful not because it replaces every workplace application, but because it makes information from those applications easier to discover.
For organizations already investing in Copilot, that could be an important step toward turning AI from a standalone assistant into a more connected gateway to workplace knowledge.
Extra posts:
Microsoft 365 Copilot Pages Are Moving to OneDrive: What Organizations Need to Know 
From Chaos to Clarity Governance Tips for Organizations Rolling Out Microsoft 365 Copilot 
Microsoft Pauses Rollout of Copilot-Powered SharePoint Page Authoring: What Organizations Need to Know 
Microsoft Makes Copilot Easier to Try: Free 30-Day Microsoft 365 Copilot Trial Arrives for SMBs Without Payment Details 
Microsoft 365, Copilot & Copilot Studio News 
Microsoft Edge Gets Smarter: Microsoft 365 Copilot Brings Contextual Answers to Tabs, Documents and YouTube