The tenant already does most of this
A separate content platform arrives with its own notification center, its own reporting store, its own automation engine and its own user list. Each one is a thing to run, secure and explain. Components stored as SharePoint items reach the surfaces the organization already operates instead.
The substrate question is settled before this one starts
Where the components live, whose identity governs them and which audit log records them are architecture questions, answered on Built on SharePoint and DITA on SharePoint. This page is about what happens next: where the review lands, where the reporting runs, what automates the routine steps, and what other systems can read.
The pattern is the same in every case. The component is a SharePoint item, so anything in Microsoft 365 that can act on a SharePoint item can act on a component, and nothing has to be copied out first.
Six places the content shows up without a second application
None of these is a DitaExchange feature in the usual sense. They are the Microsoft 365 services the organization already licenses, pointed at content that is finally in a shape they can act on.
Microsoft Teams
Dx5 is available as a Microsoft Teams app, so content work is discoverable where the team already talks about it. Review and approval tasks arrive as Teams notifications rather than in a queue somebody has to remember to open.
Outlook and Exchange email
Tasks route through Outlook and the Exchange mailbox the organization already runs, and through Planner where it is used. There is no separate workflow inbox, which is the difference between a reviewer taking part and a reviewer being chased.
Power BI
Business intelligence reporting runs on the SharePoint data directly through Power BI. No export step, and no second reporting store to keep in sync, so a dashboard showing approval throughput or translation backlog reads the same records an auditor would.
Power Automate
The flows run on the customer's own SharePoint and Power Automate, using the automation platform the organization already builds with. A team that automates approvals elsewhere in the tenant automates content approvals the same way.
Two APIs, not a new one
Two machine-to-machine surfaces the tenant can already reach: SharePoint's own API, and the Dx5 API, whose REST endpoints expose components, maps and assemblies to downstream consumers such as supplier portals and in-app help systems.
Line-of-business applications
Applications already running in the tenant can read approved components through those endpoints instead of holding their own copy of the text. When the component changes, what the application shows changes with it.
Single sign-on is not the same thing as native identity
An IT reviewer does not ask whether a platform supports single sign-on. They ask how many user lists the organization will be maintaining afterward.
Most credible enterprise platforms authenticate against Microsoft Entra ID. That is single sign-on, and it means one fewer password, not one fewer user list. With native identity the access control is Entra ID and SharePoint permissions directly: no separate user model to provision, none to deprovision when somebody leaves, and conditional access rules that apply unchanged. That is the difference IT review cares about, and it is why the surfaces above need no configuration.
The trade is a narrower integration footprint than a cloud-native CCMS. Where the requirement is the broadest third-party reach, across translation-memory ecosystems and niche regulatory submission tools, or where documentation is tightly coupled to PLM, ERP or CAD systems, that is a different shortlist and Bluestream is built for it. The Microsoft Graph API and the connector ecosystem have narrowed that gap substantially, and it is not closed.
Frequently asked questions
Which Microsoft 365 and SharePoint deployments does this work on?
SharePoint Online as part of Microsoft 365, and SharePoint Server on-premise from 2019 including Subscription Edition. National-cloud Microsoft 365 tenants (US Government, China operated by 21Vianet, Germany) go through the SharePoint Online path, air-gapped deployments through SharePoint Server, and hybrid topologies are supported for staged moves to cloud.
Does reporting need a data export?
No. Power BI reports run against the SharePoint data directly, so there is no export step and no second reporting store to keep in sync. The content, its approval records and its version history are SharePoint items, which is what makes them reportable without a copy.
What can other systems read, and how?
Through two APIs: the SharePoint API, and the Dx5 API, which exposes components, maps and assemblies as REST endpoints. That is how supplier portals, in-app help systems, partner integrations and line-of-business applications consume approved content. They read the approved component rather than a copy of a document, so the answer they show changes when the component changes.
Does this mean DitaExchange integrates with everything?
No, and the honest version is worth stating. A cloud-native CCMS may have a wider third-party integration footprint than a tenant-hosted approach, particularly across translation-memory ecosystems and niche submission tools. The gap has narrowed with the Microsoft Graph API and the connector ecosystem, but it is not zero. If your documentation is tightly coupled to PLM, ERP or CAD systems and that coupling is the priority, a vendor built around industrial systems fits better.
Does any content sit outside our tenant?
No. The components, the maps and the metadata are items in the customer's own SharePoint, so there is no DitaExchange-side repository holding a copy, no second audit log and no separate user model. That is also why the surfaces above need no synchronization: they are reading the same items, under the same permissions.
Bring the integration question to the demo
The useful version of this conversation is specific. Name the report your content team is asked for every month, and the application in your tenant that needs to read approved text. Those two answers size the work.
