On October 20, 2026, CAS, a division of the American Chemical Society, announced CAS Connections in Microsoft Copilot. The connector gives Copilot customers access to the CAS Content Collection and CAS Newton, its agentic AI built for science. CAS and Microsoft developed it with pharmaceutical, life sciences and chemical organizations in mind.
For non-chemists, this is also a clear example of how Microsoft is building out the Copilot connector ecosystem. Specialist, licensed data sources are now being plugged into Word, Teams and PowerPoint, instead of living in separate search portals.
What the connector does
CAS describes three example workflows. These are vendor-supplied scenarios. The announcement reports no measured results or independent testing.
- Word: A chemist drafting the experimental section of a report can confirm a compound's CAS Registry Number and structure. They can check reaction conditions and reagent availability against CAS records, and cite the source while writing.
- Teams: An intellectual property analyst can check whether a substance appears in the patent literature.
- PowerPoint: A business development analyst preparing a licensing briefing can add patent landscape information that traces back to CAS content.
R&D World's reporting adds that the connector is listed in the Microsoft Marketplace with Microsoft as publisher and no listed price. A missing price tag does not mean the content is free, as the licensing section below explains.
Microsoft's own connector gallery lists it under Health and life sciences. The gallery describes it as a way to search the CAS Content Collection and look up chemical substances. That wording is narrower than the press release's workflow examples. It's a sensible reminder to test what the connector actually returns in your tenant before promising users the full demo.
Federated, not synced
For IT administrators, the key detail is the connector type. Microsoft's federated connectors overview lists CAS Connections among its federated connectors in the Health and life sciences category.
Microsoft's documentation draws a clear line between the two connector models:
- Organizations can either index external data with synced connectors or connect to data in real time with federated connectors.
- Microsoft's overview says synced connectors index data into Microsoft Graph, while federated connectors fetch content live with no indexing.
- Federated connectors operate at the user level. Each user connects with their own credentials, not admin credentials.
- Microsoft says federated connectors don't copy or store data in Microsoft 365. The source system remains the system of record.
In practice, CAS's database is not being bulk-loaded into your tenant. Copilot queries CAS at runtime under the signed-in user's identity. "No copying or storing" describes the connector model. It should not be read as "nothing is sent anywhere during a query." Copilot still has to pass the request to the connector.
Licensing: the part that decides who gets it
Two separate licenses are involved.
- CAS subscription. CAS's product page says access through CAS Connections is governed by an organization's CAS subscriptions. It also says the content available through a given integration depends on those subscriptions and on the partner platform's configuration. Not every Copilot user gets the whole collection.
- Microsoft 365 Copilot. Microsoft's prerequisites page says federated connectors need a Microsoft 365 Copilot add-on license for every user who queries the source. Microsoft 365 E7 also qualifies. Microsoft 365 alone doesn't enable them. Copilot Studio licenses and Microsoft 365 Copilot pay-as-you-go don't support federated connectors either.
If a pilot group has Copilot Studio-only licensing, plan for this gap before you start.
What admins control
Microsoft's documentation covers the following controls. These are framework-level features, not details specific to CAS.
- Agent and plugin access. Under Agents > Settings > Agent and plugin access in the Microsoft 365 admin center, admins choose whether to allow connectors by publisher type. Microsoft-built federated connectors are available by default when Allow agents and plugins built by Microsoft is selected and the user falls within User access. The CAS listing shows Microsoft as publisher, which suggests it would follow that default path. Verify this in your own tenant.
- Per-connector management. Admins manage connectors under Copilot connectors > Your connections. They can enable or disable a connector at tenant level, or limit it to specific users or Microsoft Entra ID groups through staged rollout.
- User access ceiling. The User access setting sets the maximum population. Connector-level staging can't extend beyond it.
- Auditing. Microsoft says admins can audit federated connector activity in Microsoft Purview. Retention and configuration depend on your own setup.
What users see
Microsoft's documented flow, which applies to federated connectors generally, runs as follows:
- An admin enables the connector.
- In Copilot Chat, the user goes to Settings > Sources, selects the data source and chooses Connect.
- The user signs in to the source with their own credentials.
- The user returns to Copilot and writes a prompt that names the data source and gives relevant detail, such as a compound or project.
Microsoft says users can find federated sources in the Sources menu in the Researcher agent and in deep research mode in Microsoft 365 Copilot chat. It adds that Copilot Chat offers them where available.
Write actions: no evidence for CAS
Microsoft's framework allows federated connectors to create, update or delete data when the publisher exposes such tools. Those actions require user approval. Nothing in the available CAS material says the CAS connector offers write operations. A reference database is a natural read-only fit, but that is an inference. Don't tell users otherwise.
Context: CAS's AI push
R&D World places the connector in a run of CAS announcements this year. CAS launched CAS Newton in April, then CAS Connections in June. CAS launched CAS Connections with several initial collaborators in June 2026. Beyond Microsoft, the framework targets electronic lab notebooks, laboratory information management systems, discovery platforms and enterprise AI.
A separate September 29, 2026 CAS release announced a collaboration with Novartis Biomedical Research. It covers searchable access to proprietary reaction data alongside more than 160 million scientist-curated reactions. It also covers a custom discovery platform built on SciFinder architecture. It is not part of the Copilot connector.
R&D World also notes that Elsevier's Reaxys, a rival chemistry database, offers MCP, API and flat-file integration under a separate license. That suggests MCP is becoming a common route for scientific content into AI assistants.
How much to trust the claims
Several claims here are the vendors' own positions:
- CAS calls its collection authoritative and its Newton answers cited and verifiable.
- Microsoft's Chantrelle Nielsen said customers need AI they can trust, grounded in reliable scientific information.
- CAS says researchers can work more efficiently and make better-informed decisions.
The available sources don't show accuracy rates, customer deployments, time savings or a staged rollout schedule beyond the October 20 availability announcement. For consequential decisions, such as freedom-to-operate analysis or reaction safety, users should check any generated answer against the underlying CAS records. Citations help with that, but they don't replace the check.
Practical checklist
- Confirm which users hold Microsoft 365 Copilot add-on or E7 licenses.
- Check with your CAS account team what your subscription exposes through partner integrations.
- Review Agent and plugin access and User access settings in the admin center.
- Pilot with an Entra group through staged rollout.
- Confirm Purview audit coverage meets your compliance needs.
- Tell users that they sign in with their own credentials and that results depend on their CAS entitlements.
The connector's value will depend on how well it answers real queries under real subscriptions, and CAS hasn't published anything on that yet.