Top 5 Dynamics 365 Customer Portal Solutions Compared (2026)

Every product on this list will show a customer their own open cases. That capability stopped being a differentiator years ago, which is why feature grids have become close to useless for this decision.

What has not converged is the price of doing it. For roughly 400 external users signing in each month, the published figures from the vendors who publish one run from about $399 to about $800 to $1,500 and up. The spread is not explained by capability. It is explained by what each vendor decided to meter, and by where your data has to sit before any of it works.

The five Dynamics 365 customer portal options below are ordered by how close each product sits to the Dynamics data it serves, starting with Microsoft's own option. It is not a ranking.

What actually separates these products

Four questions do more to narrow a Dynamics 365 customer portal shortlist than any feature matrix, and you can answer all four before booking a demo.

Where the record has to live. Most of these products read from Dataverse. If the information your customers want is already there as cases, accounts, orders or custom tables, that is a non-issue. If it lives in Business Central, in Finance and Operations, or in a line-of-business system nobody has connected yet, then the portal decision is downstream of a data decision, and choosing the portal first is how projects lose a quarter.

What the meter counts. This is the axis that produces the price spread above. Microsoft counts external people who authenticate, per website, per month. Third-party products tend to count a user band, a partner account, or an enabled module. None of these is inherently better. They simply reward different shapes of external population, and the shape you should model is your busiest month rather than your average one.

Who owns it in year two. A portal is not a project that ends. Someone has to publish content, adjust permissions when the sales team invents a new record type, and test the thing twice a year when a platform wave lands. Whether that person needs Power Platform skill, CMS skill, or nothing beyond the vendor's configuration screens is a staffing decision disguised as a product decision.

What leaving costs. Ask where the page definitions and access rules physically live. Rules expressed as Dataverse table permissions stay with you when the front end changes. Rules expressed inside a vendor's builder do not, and that is true of every third-party option here, including ours.

1. Microsoft Power Pages

Power Pages is the platform's own answer, and the descendant of Adxstudio and Power Apps portals. It builds external-facing sites directly on Dataverse, with portal users stored as contact records and record visibility governed by table permissions attached to web roles.

• Access rules live in Dataverse as table permissions, so they survive a front-end change

• Portal users are contact records, which keeps external identity in the same place as the rest of your customer data

• External identity providers are supported through OpenID Connect and related protocols

• Business Central data is reachable through Dataverse virtual tables, so the boundary is not absolute

Where it excels: organizations already fluent in the Power Platform, with the data in Dataverse and an admin who is comfortable with table permissions and Liquid templates.

Limitations: the content management layer is lighter than a real CMS, and building anything past the standard templates draws on Power Platform skill you either have or must hire. Cost is driven by your customers' sign-in behavior rather than your own headcount, and a customer portal plus a partner portal counts as two websites with two meters, even when some of the same people use both.

Pricing: $200 per month per website for a capacity pack of 100 authenticated users, and $75 per month per website for a pack of 500 anonymous users, paid yearly, per Microsoft's published pricing page.

Best for: Dataverse-native organizations with in-house Power Platform capability and a predictable external user count.

2. Portal Connector by Sylogist

Portal Connector is the option for organizations that want a genuine content management system in front of Dynamics rather than a page builder. It runs on Progress Sitefinity and is sold as a subscription hosted in Sylogist's own Azure tenant, listed and directly purchasable on Microsoft AppSource since September 2025.

• Full Sitefinity CMS capability for content-heavy portals, not a template gallery

• Widget-based configuration over Dynamics records, including create and update operations

• Works with Dynamics deployed in the cloud, on a local server, or through a third-party host

• Backed by Sylogist, a publicly traded software group, with infrastructure specialists included in the subscription

Where it excels: the case Microsoft cannot serve at all, which is Dynamics 365 running on-premises. It is also the strongest fit when the portal is as much a marketing site as a self-service tool, because that is what a CMS is for.

Limitations: Dynamics only, with no path to a second CRM if your group acquires one. The CMS advantage carries a matching skill requirement, since someone on the team has to know Sitefinity. The subscription covers one production site, so multi-site rollouts cost more. Sylogist does not publish a list price.

Pricing: quoted through the AppSource listing. No public list price is published on the product site.

Best for: mid-market and enterprise Dynamics organizations with heavy content needs, or any organization running Dynamics 365 on-premises.

3. CRMJetty

CRMJetty sells a portal layer that connects to Dynamics 365 and to three other CRMs, with a flat fee replacing per-user or per-login metering. Disclosure before you read further: this is our product, and the section is written to the same structure and roughly the same length as the four around it.

• Flat pricing to 500 users, with no per-login charge, capacity pack, or overage fee

• No-code page builder with role-based access and live data widgets over Dynamics entities

• Multisite support from a single admin panel, which matters when customer and partner audiences are separate

• ISO 27001 and ISO 9001 certified, with single sign-on and a mobile app for portal users

Where it excels: external populations that are large, growing, or seasonal, where a per-authenticated-user meter produces a bill nobody budgeted for. It also fits groups running more than one CRM, since the same flat rate applies across Dynamics 365, Salesforce, SugarCRM and SuiteCRM.

Limitations: past 500 users, and for multi-CRM arrangements, pricing moves to a quote, so the predictability has a ceiling you have to negotiate. Public review volume is thin next to the Microsoft-native option, which makes independent peer validation harder to find. There is no self-serve trial, so a proof of concept starts with a scheduled demo. Page definitions and access rules live in our builder rather than in Dataverse, which is the same exit cost every third-party option on this list carries.

Pricing: $399 per month for up to 500 users, flat, at the same rate across all four supported CRMs. Enterprise and multi-CRM tiers are quoted.

Best for: mid-market organizations with a few hundred to a few thousand external users who want the monthly figure to stop moving.

4. Magentrix

Magentrix began as a partner relationship management platform and extended into customer portals, and its design still reflects that origin. Rather than mapping fields between systems, it mirrors your CRM schema and record identity, and writes go to the CRM first so your validations and triggers run before anything syncs back.

• Mirrored data model and record identity, which removes field-mapping maintenance

• Deal registration, partner pipeline, learning management and co-branding for channel programs

• Case management, ticket deflection, knowledge base and community forums on the customer side

• Connects to Microsoft Dynamics, Salesforce and HubSpot, with a REST API for anything else

Where it excels: organizations whose external population is a channel rather than a customer base, where deal registration and partner enablement are the actual requirement and customer self-service is secondary.

Limitations: the published tiers are shaped around partner programs, so the entry price is steep if all you need is customer self-service. The mirrored model means a copy of your schema and records lives on Magentrix infrastructure, which is a data residency conversation in regulated sectors. Hosting is in Canada.

Pricing: Essential at $1,500 per month covering 100 partner users or 10 partner accounts, Advanced at $3,000 per month covering 150 partner users or 20 partner accounts, and an Unlimited tier at custom pricing.

Best for: Dynamics organizations running a formal channel program where partner management is the primary job.

5. Simova Business Portals

Simova sits in a different place from everything above it, because it does not use Dataverse at all. Business Portals is a Business Central extension that serves customer and vendor portals directly from Business Central through web services, with no duplicate storage and reports generated at the moment of download.

• Reads live from Business Central rather than holding a synced copy

• External users need no Business Central license

• Customer and vendor portals with different datasets per audience

• Configured from inside Business Central and hosted on Azure, with a 30-day trial on AppSource

Where it excels: distributors, wholesalers and service organizations whose orders, invoices and statements have always lived in Business Central and were never going to be moved into Dataverse to satisfy a portal project.

Limitations: Business Central only, so it does nothing for Sales, Customer Service or any other Dataverse-side application. The vendor is German, prices in euros, and its customer base is concentrated in Europe. Licensing is per module plus key users, so the real cost depends on how many modules you enable. Running a Business Central version outside mainstream support adds an extended lifecycle fee of €49.99 per month.

Pricing: €599 per month plus €49.99 per key user, billed monthly, or €569.05 per month plus €47.49 per key user on annual billing. External web users are unlimited at any tier.

Best for: Business Central organizations that want customer or vendor self-service without first building a synchronization layer into Dataverse.

How to choose

Work through these in order. A Dynamics 365 customer portal shortlist narrows faster than you expect.

If your data is in Business Central and staying there, the shortlist is Simova or a Power Pages site built on virtual tables. Nothing else on this page addresses that boundary directly, and choosing a Dataverse-first product will surface an integration project you did not budget for.

If your external population is under about 150 people and stable, Power Pages is likely to be the cheaper answer, because one or two capacity packs cost less than any flat fee here. Per-user metering is a good deal when the user count is small. Model the peak month, not the average.

If your external population is large, growing, or seasonal, run the arithmetic before you shortlist anything. Four hundred authenticated users against a $200 per hundred meter is $800 a month per site, and a second portal is a second meter. Whether a flat fee beats that is a calculation, not an argument.

If your requirement is really a channel program, you are comparing partner relationship management platforms, not customer portals, and the evaluation criteria change. Deal registration and partner enablement depth matter more than page building.

If Dynamics 365 runs on-premises, Power Pages is not an option and the shortlist gets very short.

If nobody will own the portal after go-live, stop. Content decays, permissions drift, and platform waves land twice a year. A portal without a named owner underperforms its business case no matter which of these products you buy.

The honest summary is that four of these five are the right answer for somebody, and the wrong answer for most people. Answer the four questions in the second section, in writing, before the first demo. The shortlist writes itself, and it will be shorter than five.