What Hyland announced
Hyland announced the launch on November 3, 2026. The integration brings Hyland-managed content into Teams. Users can search for, view, manage, share and capture governed content without leaving the collaboration workspace. It connects Teams to supported OnBase and Nuxeo repositories.
IT Brief UK's report describes the same launch. It frames the product as aimed at organisations in regulated industries that use OnBase or Nuxeo repositories.
The features, as the vendor describes them:
- Search: Users can search Hyland content directly from Teams chats and channels and work with documents inside the collaboration platform.
- Link sharing: Users can share links to repository content instead of creating unmanaged copies. IT Brief says source files stay in the governed repository. Hyland's wording is that repository governance and security "remain fully in place."
- Capture: Content shared in Teams conversations can be imported into Hyland repositories for long-term management and retention.
- Association: Content can be related to specific Teams conversations, making relevant information easier to locate later.
Deployment: what admins need to know
The announcement says administrators configure the entire integration through the Hyland Content Innovation Cloud (CIC) and obtain the Teams app package needed for rollout. In practice, this is a tenant-level deployment that IT admins run. It isn't a feature that appears for every Teams user.
On availability, Hyland says the product is available now to existing Hyland customers using Microsoft Teams as a primary collaboration workspace.
A Hyland Connect community post adds scope. The initial release supports OnBase and Nuxeo repositories, and the integration is designed to support additional Hyland repositories in future. Alfresco customers shouldn't assume they're covered yet.
The CIC link matters because of Hyland's federation layer. Hyland's Q4 2025 release notes say Content Federation Service is now available in Hyland Content Innovation Cloud. They say it can connect Hyland OnBase (on-premises or in the Hyland Cloud), Alfresco, Nuxeo and/or SharePoint 365 to the Content Innovation Cloud. That is context I'm drawing from Hyland's earlier documentation. It doesn't confirm exactly how the Teams product uses the service. Admins should check Hyland's current product guide for the exact version, licensing, tenant and region requirements before planning a rollout. I couldn't verify those requirements from the material available here, so I haven't listed them.
The use cases Hyland offers
Hyland gives three scenarios. They are vendor illustrations, not verified customer deployments.
| Sector | Scenario described |
|---|---|
| Banking | Staff preparing for a commercial customer meeting, chasing missing loan documents or investigating suspected check fraud retrieve governed OnBase content from Teams. |
| Insurance | A claims team imports photos, estimates and adjuster reports from a claim channel into the claim's document type. Hyland says this triggers the relevant claims workflow. |
| HR | Resumes and offer documents shared in a recruiting channel are captured into a governed HR document type, not left in chat or a personal drive. |
Hyland sums up the pattern this way: the conversation happens in Teams, but the content, workflow, compliance and governance stay in Hyland's platform.
Why this matters for Microsoft 365 admins
Teams is good at making files multiply. Someone drops a PDF into a channel, someone else uploads a revised copy, and the "authoritative" version quietly becomes a matter of opinion. Records managers know this problem well. Hyland's release describes it as content sprawl, duplicate storage, manual capture steps, and governance gaps.
The product tackles it in two directions. It brings repository content to the user, so people have less reason to download and re-upload. It also gives them a route to push collaboration artifacts back into the repository. Done well, that is a reasonable architecture for organisations that already run OnBase or Nuxeo.
Caveats
- Vendor claims, not measurements. Neither source offers independent data on time saved, reduced duplication or improved compliance. IT Brief's account tracks Hyland's announcement closely and doesn't amount to independent testing.
- "No migration" has limits. Hyland says the integration needs no migration, no duplicate repositories, and no rebuilt workflows. That describes the content and workflows. It doesn't mean there is no configuration, licensing or Teams app deployment work.
- Governance isn't automatic. Nothing in the supplied material says every file in Teams becomes governed, or that linking a conversation applies a retention policy. Capture is an action users or workflows take. Policy still depends on how the organisation configures its repository.
- Microsoft's role is an endorsement. Jacquelyn Crowhurst, Microsoft's chief architect for the Americas enterprise partner solution, is quoted saying the product brings trusted, governed enterprise content into the flow of work. That is a partner quote. It doesn't make this a Microsoft-built product or a security assessment.
- Pricing and rollout details are missing. Neither source states pricing, supported regions or a deployment timeline.
What to do next
- Confirm you run a supported OnBase or Nuxeo repository and that your Hyland licensing covers the integration.
- Check Hyland's documentation for Microsoft 365 tenant type and regional support.
- Ask your Teams admins how app packages get approved and deployed in your tenant, and whether your app policies allow custom or partner apps.
- Pilot with one records-heavy team, such as claims or recruiting, and see whether import and association match your retention rules.
- Review who can import content into repositories, because capture creates records.
For regulated shops already invested in Hyland, this is a practical convenience. For everyone else, it's a useful example of how ECM vendors are meeting users inside Teams.