Integration pages usually list logos. This one leads with direction, because that is the question that decides whether a connector fits how you work: does the work stay where your teams already do it and get read into the portfolio, or does PPM Express also write back into the tool?
The badge on each card is the direction. Where a capability is limited to a plan or needs configuration by our team, the card says so, because that is the kind of detail that should surface during evaluation rather than during implementation.
Work items, teams, iterations and area paths read into the portfolio, filtered by team, work item type, iteration or area path. On Ultra, mapped field values and parent-child hierarchy sync in both directions, and PPM Express can create work items in Azure DevOps. Two-way requires the PMO Aggregator extension, provisioned by PPM Express, and applies only to items you have explicitly linked. Azure DevOps Cloud only; Server is not supported.
Azure DevOps portfolio management
Two-way · UltraProgress, sprints and iterations with dates and counts, issue status, story points, effort and team members from assignees, plus additional field mapping and Key Dates. On Ultra, mapped fields sync in both directions on the same terms as Azure DevOps. Jira Cloud only; Server and Data Center are not supported.
Two-way · UltraProjects, tasks and custom fields read into the portfolio, with tasks importable as Key Dates. The task view in PPM Express is read-only, so edits are made in Project Online and picked up on the next sync. Project Online retires on 30 September 2026 and there is a documented migration path.
One-way into PPM ExpressProject and task data from Project for the Web, also sold as Planner Premium, with configurable field mapping, Key Dates and program linking. Read-only inside PPM Express.
One-way into PPM ExpressPlans, buckets and tasks with progress, timeline and status, team assignments and task counts by progress, feeding the portfolio roll-up. Read-only inside PPM Express.
One-way into PPM ExpressSchedules published from Project Desktop through the PPM Express Project Publisher add-in, with custom field mapping and .mpp tasks imported as tasks or Key Dates.
One-way into PPM ExpressSheets and rows with owners, dates and status, plus resource linking, progress mapping, additional field mapping and Key Dates. Read-only inside PPM Express.
Smartsheet portfolio management
One-way into PPM ExpressBoards, groups and items with owners, dates and status, with progress mapping, additional field mapping and Key Dates. Read-only inside PPM Express.
monday.com portfolio management
One-way into PPM ExpressResources synchronised from your Microsoft 365 directory, with field mapping between PPM Express resources and Entra ID attributes. Nothing is written back to the directory.
One-way into PPM ExpressThe exception to the pattern. No data is read from the group. Instead PPM Express can add the project manager as an owner of the linked group, and add resource-plan engagements as members of it.
Outbound onlyLink a PPM Express project, program or portfolio to a Teams channel to receive updates there. A notification surface rather than a data connector.
PPM Express for Microsoft Teams
No data syncRead and write projects, tasks, ideas, key dates and resources, with webhooks for outbound events. This is the route for any system without a built-in connector.
Read and writeA published connector for retrieving information about projects, ideas, tasks, key dates and resources, and for creating or updating them from inside a Microsoft 365 flow.
Read and writeA published app with triggers on create, update and delete for ideas, key dates, projects and tasks, and actions to create and update the same entities, including moving an idea to a new stage.
Read and writeThe 200+ report pack reads the portfolio for analysis, dashboards and executive reporting. A reporting route rather than a project-data connector.
ReportingHow these scores are produced. All nineteen platforms are measured against the same eighteen requirements, at the same 250-user scenario, using published vendor documentation only. The requirement set, the weightings, the three buyer scenarios, the evidence rules and the limitations are set out in full on the comparison methodology page.
Portfolio reporting on top of Jira, without changing how teams work.
Integrations
Roll Azure DevOps delivery into a portfolio leadership can read.
Integrations
Bring Planner work into portfolio-level visibility.
Integrations
Last updated 20 August 2026
Sync direction, plan requirements, what is read-only and what writes back.
Azure DevOps and Jira, on the Enterprise Ultra plan. Mapped field values and parent-child hierarchy sync in both directions, and PPM Express can create work items in Azure DevOps. Both require the PMO Aggregator extension, which our team provisions for your tenant, and both sync only the items you have explicitly linked. Every other connector reads into PPM Express and writes nothing back.
Not on the connected task pages. For Jira, Azure DevOps, Planner, Project Online, Project for the Web, Smartsheet and monday.com, the task view in PPM Express is for viewing only. You edit in the source tool and the change is picked up on the next sync. That is deliberate: one place to update the work, and no second version of the truth.
No. Both connectors are cloud only. Azure DevOps Server is not supported, and neither are Jira Server or Jira Data Center. If your teams are on a self-hosted instance, the Public API is the route, and it is worth raising early rather than during implementation.
Use the Public API, the Power Automate connector or the Zapier app. All three read and write projects, tasks, ideas, key dates and resources, so a system without a built-in connector can still push work into the portfolio. Webhooks cover the outbound direction.
Yes, and in a transformation programme it is normal. A single initiative can carry a predictive master schedule, an Azure DevOps engineering stream and a Planner workstream, with portfolio financials, risks and governance held in PPM Express above all of them.
No, and most customers do not. Nothing is migrated. Teams keep their boards, plans and sheets, and the portfolio layer reads from them. If a connector on this page turns out to be wrong or out of date, tell us and send the documentation that contradicts it.
.svg){kind=small}
