Many organizations have an abundance of information, but employees cannot easily find, trust, or use it. Documents live across Teams, SharePoint, Outlook, old Confluence spaces, and network folders. Processes are known but not consistently followed. Multilingual versions exist but rarely align.
The problem is not the lack of documentation; it’s that knowledge does not appear where work happens. This is exactly the issue Carla O’Dell and Cindy Hubert highlighted in The New Edge in Knowledge: knowledge management systems fail when they force employees to leave their workflow and manually search through disconnected repositories.
Their insight has only become more relevant in 2025, especially for organizations relying heavily on Microsoft 365.
Steps to Improve Knowledge Management in Microsoft 365
In this article, we explore how modern enterprises can finally solve this problem by embedding knowledge directly into Microsoft 365 workflows and how Rocketta supports this transformation with Easy Wiki, AI-powered knowledge agents, lifecycle automation, and multilingual content management.
Why Traditional Knowledge Systems Fail Inside Microsoft 365
Microsoft 365 has become the central workspace for many organizations. Teams is where people communicate. SharePoint is where documents live. Outlook carries discussions forward. Planner, OneDrive, and Power Automate orchestrate daily work.
However, even in this unified ecosystem, knowledge often remains fragmented across:
- outdated Confluence spaces
- Teams chats
- random SharePoint libraries
- personal folders
- legacy intranets
- duplicated multilingual versions
Employees spend too much time trying to answer basic questions:
Where is the latest SOP?
Which document is the correct version?
Do we have the German version of this policy?
Which template should I use?
This creates slow decision-making, inconsistent processes, compliance risk, and daily frustration. The core issue is exactly what O’Dell and Hubert described: if knowledge sits outside the workflow, people avoid it.
What O’Dell & Hubert Can Teach Us About Microsoft 365 Today
In The New Edge in Knowledge, O’Dell and Hubert emphasize that knowledge must be embedded directly into the systems where work occurs. When employees must switch tools, search manually, or navigate complicated repositories, adoption drops, even if the content quality is excellent.
They share a powerful example of a call center where agents were required to open a separate knowledge portal during customer calls. Because this broke their flow, they rarely used it. After the company embedded troubleshooting information directly into the CRM interface, everything changed:
- call handling time decreased
- quality improved
- employee confidence increased
- adoption happened naturally
The improvement had nothing to do with more technology. It happened because knowledge became part of the workflow. This idea — simple, practical, and proven — is exactly what modern knowledge management in Microsoft 365 must achieve.
A Modern Parallel: A Real Rocketta Customer Example
One of our European clients, a manufacturing company operating in six languages, faced a similar challenge. Their processes, SOPs, and checklists were technically well documented, mostly in Confluence and PDF formats, but workers couldn’t find or trust the correct version.
They routinely asked colleagues, searched for email threads, or consulted outdated PDFs stored locally.
Here’s what changed after moving to Rocketta Easy Wiki and introducing embedded knowledge access:
- The AI-based knowledge agent allowed employees to ask questions directly in Teams (“Show me the latest SOP for machine X”).
- The SharePoint Translator kept all language versions synchronized.
- Easy Wiki templates created a uniform structure for SOPs, work instructions, and quality guidelines.
- Power Automate managed review cycles and ensured content was always up to date.
Instead of jumping between systems, employees found information inside the tools they already use. The impact mirrored the CRM example from the book: smoother workflows, fewer errors, and significantly faster access to critical knowledge.
Why Many Microsoft 365 Organizations Move Away from Confluence
Confluence remains a strong documentation platform, but for companies fully committed to Microsoft 365, it increasingly becomes:
- an extra platform
- an extra search index
- an extra governance layer
- an extra cost
Licensing grows quickly as companies expand. Integration with Microsoft Teams is limited. Permissions differ from SharePoint, creating confusion. Multilingual content becomes difficult to control.
This is why many companies search for Europe-based Confluence alternatives and transition to a SharePoint intranet wiki as a unified, compliant, and cost-effective foundation.
Rocketta supports this transition by rebuilding content structure, taxonomy, navigation, and workflows in a way that fits Microsoft 365 instead of fighting it.
Embedding Knowledge in Microsoft 365: From Concept to Practice
To apply the principles from O’Dell & Hubert effectively, knowledge must appear directly in:
- Teams
- Outlook
- SharePoint pages
- CRM systems
- Project plans
- Power Automate flows
This is where Rocketta’s platform becomes essential. Instead of creating yet another tool, Rocketta enhances the existing Microsoft 365 ecosystem to deliver knowledge when and where it is needed.
Let’s break down how each component contributes.
How Rocketta Enables Embedded Knowledge in Microsoft 365
Easy Wiki: A Structured, Searchable SharePoint Wiki
Easy Wiki turns SharePoint into a true knowledge base with:
- standardized page templates
- metadata and taxonomy
- clear content hierarchy
- automatic table of contents
- SharePoint breadcrumb navigation
- cross-department hubs
- ownership tracking
This ensures knowledge is structured, consistent, and easy to navigate — something standard SharePoint rarely achieves on its own.
Lifecycle Automation with Power Automate
Knowledge becomes unreliable when it is not maintained. Rocketta solves this with automated:
- review reminders
- expiry notifications
- approval workflows
- audit-ready version control
This keeps information current without imposing manual administrative tasks on teams.
SharePoint Translator: Multilingual Content Without the Overhead
Multilingual documentation is one of the most common pain points for global organizations.
Instead of managing separate copies, the SharePoint Translator lets authors:
- write content once
- generate synchronized language versions
- maintain aligned metadata
- keep all translations updated automatically
This eliminates the fragmentation that most multilingual wiki systems produce.
By the way, here you can test out Rocketta’s SharePoint translator for free.
AI-Based Knowledge Agents in Teams and Outlook
Rocketta’s AI assistant brings knowledge directly into employees’ daily tools.
It allows users to:
- ask questions in natural language
- get summaries of long documents
- retrieve templates instantly
- navigate multilingual content
- find SOPs or policies by topic instead of file name
It uses only internal, approved SharePoint content, ensuring accuracy, security, and compliance — essential for regulated industries.
This is exactly the kind of embedded knowledge experience O’Dell and Hubert envisioned.
Comparison Table: Traditional vs. Embedded Knowledge in Microsoft 365
Why Embedded Knowledge Outperforms Traditional KM (SEO-Friendly Comparison)
| Dimension | Traditional KM Tools (e.g., Confluence) | Embedded Knowledge in Microsoft 365 (Rocketta) |
| Where employees find knowledge | In a separate portal | Directly in Teams, SharePoint, Outlook |
| Search | Multiple search engines | Microsoft Search + AI augmentation |
| Content structure | Flat spaces, inconsistent | Structured SharePoint intranet wiki |
| Navigation | Manual | SharePoint breadcrumb navigation |
| Multilingual content | Independent versions | Synced by SharePoint Translator |
| Lifecycle management | Manual maintenance | Automated review & expiry workflows |
| Governance | Separate rules | Native Microsoft Purview governance |
| Cost | Additional licensing | Included in Microsoft 365 |
| Scalability | Limited for large enterprises | Designed for thousands of users |
| User adoption | Depends on training | Embedded in daily workflows |
What This Means for Modern Organizations
Companies don’t need another wiki or collaboration tool. They need a knowledge environment that:
- fits naturally into Microsoft 365
- reduces friction
- supports multilingual teams
- ensures compliance
- stays current
- provides intelligent answers
- scales across departments and countries
- replaces duplicated Confluence and legacy tools
- becomes invisible in the best sense — always there when needed
Embedding knowledge, rather than storing it, is the defining difference. This is how organizations reduce operational risk, increase efficiency, and create a single source of truth without forcing employees to change their behavior.
Conclusion: Knowledge Works When It Becomes Part of the Work
The most effective knowledge systems do not require employees to go hunting for information. They deliver the right content at the right moment, inside the tools people already use — Teams, Outlook, and SharePoint. This is what Rocketta helps organizations achieve. By combining a structured SharePoint intranet wiki, lifecycle automation, multilingual synchronization, and AI-based knowledge agents, Rocketta brings the principles from The New Edge in Knowledge into the Microsoft 365 era.
Knowledge becomes accessible, trusted, multilingual, and always up to date — not because people work harder, but because the system supports them in the flow of work.
