Omnia is an add-on that sits on top of SharePoint and charges its own per-user license for it. We show what standard Microsoft 365 already includes, what our web parts take over – and what you decide deliberately.
Profile
Initial assessment
Omnia stores in SharePoint and uses Microsoft Search/Copilot, but delivers a completely custom interface plus a governance, lifecycle, multilingual and notification layer. Most of it is feasible with standard SharePoint and web parts (news, pages, search, profiles, mandatory reads, announcements); replacing the custom UI, teamwork governance, integration engine, learning and frontline accounts without Entra are additional effort or third-party products.
Already in the standard
With our web parts
Custom or add-on module
Digital Touch estimate based on publicly documented features – not a vendor comparison, no guarantee. The free Replacement Check delivers the reliable assessment.
Reasons
License model: Subscription – price band by user count; one-off payment plus ongoing maintenance fee; costs slightly higher at the start, otherwise even. On standard Microsoft 365 this recurring license disappears entirely – you pay once for setup and web parts.
More complex to implement and administer; a suitable partner is essential; steep learning curve.
Many third-party integrations, but mostly one-way notifications; two-way features require OmniaFX/Integration Engine.
A fair look
Nobody replaces a system that can't do anything. That's why we take its strengths seriously – and show how we answer them with standard Microsoft 365.
| What Omnia does well | How we do it in Microsoft 365 |
|---|---|
| Own, consistent UI for employees, editors and admins (new UX end of 2025) with theming engine and “Business Profiles” for multi-brand | Web parts We check this in the Replacement Check – usually feasible with standard web parts and configuration |
| Excellent multilingual support (13 system languages, Variation Author with side-by-side, Azure translation, disclaimer) and accessibility checker on publishing | Web parts Multilingual web part with automatic translation (Digital Touch) |
| Strong knowledge/content management: official documents with multi-stage review cycles, governance hub (roadblocks, publishing dashboard, bulk changes), sign-off requests for mandatory reads | Standard SharePoint pages and libraries with metadata, versioning and approval; FAQ/glossary web part |
| Comprehensive search (quick/advanced/semantic) based on Microsoft Search with Copilot connectors and scoped “agents”; very good notification integration of third-party systems | Standard Microsoft Search across SharePoint, Teams and OneDrive; search center web part with filters (Digital Touch) |
Feature comparison
Every feature with its counterpart in SharePoint, Teams, Viva or our web part catalog.
| Feature in Omnia | Solution in standard Microsoft 365 | Classification |
|---|---|---|
| Targeted news with fixed/flexible templates, editor/author roles | Audience targeting (standard, Entra groups) plus topic subscription web part for self-service | With our web parts |
| AI text/image generation, mandatory AI checks (tone of voice), accessibility checker | Mandatory read and alert web part with read status (Digital Touch), push to Teams via Power Automate | With our web parts |
| News hub with calendar, reach/engagement analytics | Editorial calendar web part and news templates (Digital Touch); approvals with SharePoint approval | With our web parts |
| Multilingual support with Variation Author workflow | Multilingual web part with automatic translation (Digital Touch) | With our web parts |
| Multichannel: Teams, Viva Engage, Slack, email, LinkedIn/Facebook/X (advocacy) | News digest via email (standard) or newsletter web part with audiences (Digital Touch) | With our web parts |
| Digital signage (URL loop, PLAYipp) | Digital bulletin board by Digital Touch (add-on module) – intranet content automatically on screens | With our web parts |
| Announcements (banner) and sign-off requests (mandatory reads with reporting) | Mandatory read and alert web part with read status (Digital Touch), push to Teams via Power Automate | With our web parts |
| Communities (professional, social, ideation with Kanban) | Ideas web part with voting (Digital Touch) or Viva Engage questions | With our web parts |
| Praise / recognition wall | Kudos web part (Digital Touch) or Viva Engage Praise; points/leaderboards custom | With our web parts |
| Forms & surveys, quick polls | Microsoft Forms and Viva Pulse; survey web part (Digital Touch) | Standard Microsoft 365 |
| Onboarding portal, learning centre, offboarding, alumni | Viva Amplify (in the M365 plan) or onboarding portal from the web part package with Power Automate | With our web parts |
| Official documents, product catalogue, governance hub | Analytics and content governance web part, or Power BI on SharePoint usage data (Digital Touch) | With our web parts |
| Quick/advanced/semantic search, promoted results, search admin | Microsoft Search across SharePoint, Teams and OneDrive; search center web part with filters (Digital Touch) | Standard Microsoft 365 |
| Employee directory, profile cards, org chart | People search and org chart web part based on Entra ID (Digital Touch) | With our web parts |
| Notification panel with third-party system tabs, integration engine (Zendesk, Slack, HubSpot) | Power Apps / Adaptive Cards – custom per process (expenses, absences, bookings) | Custom / add-on module |
| Teamwork governance (Teams/site provisioning with directory) | Analytics and content governance web part, or Power BI on SharePoint usage data (Digital Touch) | With our web parts |
| Mobile app with flexible authentication, chat | Microsoft Teams chat, calls and meetings | Standard Microsoft 365 |
| Media bank, tutorial overlay | SharePoint pages and libraries with metadata, versioning and approval; FAQ/glossary web part | Standard Microsoft 365 |
An honest calculation
Not every feature needs to be rebuilt. In the end, many features are used by only a fraction of the workforce – we check that before any effort is spent.
Assess in the Replacement Check| Stays custom | Our approach |
|---|---|
| Multi-stage review/approval workflows and governance hub for official documents | Power Automate + dashboards |
| Teams/site provisioning with governance directory | Custom solution or third-party governance product |
| Notification aggregation from third-party systems (ServiceNow, Jira, Workday) in one panel | We check this in the Replacement Check: Power Platform, add-on module or deliberately leave it out. |
| Frontline accounts without Entra | HRIS import, QR self-registration, decentralized administration |
| Translation workflow with Variation Author and side-by-side editor, learning centre, advocacy sharing | Usually feasible as a small Power Platform solution; we clarify effort and value in the Replacement Check. |
Process
We go through Omnia feature by feature: what is standard, what web parts take over, what stays custom. Result: mapping, effort and license savings.
Information architecture, permissions and design in SharePoint – as a clickable prototype in your tenant, before the migration starts.
Pages, navigation and the right web parts from the catalog; custom building blocks are created with Power Platform or SPFx.
Take over content from Omnia, clean it up and reorganize it for the target audiences; the editorial team and departments are enabled.
Pilot group, communication, go-live – then the Omnia license expires and the intranet lives on in Teams and SharePoint.
References
License calculator
Enter your user count and price – the calculator shows your savings over 1, 3 and 5 years compared to a one-time replacement project.
FAQ
Pages, news and documents are exported, cleaned up and restructured in SharePoint. Not everything has to come along – the Replacement Check shows what users really need. We map permissions via Entra ID groups.
Only briefly: we plan the go-live so that your license's notice period is met. A parallel run of a few weeks for the pilot group is usually enough.
Typically three to six months from workshop to go-live, depending on content volume and custom building blocks. The first usable version is usually ready after a few weeks.
That is what our web parts with source code are for – no recurring license. Anything beyond that we build with Power Platform or deliberately leave out after consulting with you.
Digital Touch estimate based on publicly available product information (as of October 2026), not a third-party assessment. Omnia is a product of Omnia Digital Workplace; product and feature names are for orientation only. Digital Touch is not affiliated with the vendor.
In 60 minutes we go through your Omnia intranet and show what standard Microsoft 365 already includes, what our web parts take over and what the replacement costs.