Case study

Replacing Power Pages with a Dataverse portal built on Umbraco

A self-service portal for around 14,000 business customers, rebuilt so it can be tested and changed safely.

Client
Southern Communications Group
Sector
Business telecoms
Role
Architect and developer
Period
2026 · in delivery

The situation

Southern Communications Group's business customers manage their phone lines, mobiles and broadband through a self-service portal: usage alerts, orders, invoices, access for their own staff, and service requests such as ceasing a line or swapping a SIM.

The portal had been built on Microsoft Power Pages over SCG's Dynamics 365 platform. It had grown to 260 web pages, 37 forms and 69 lists, with custom JavaScript on 23 pages, and around 14,000 people sign in to it across more than 12,000 customer accounts.

Elephas has worked with SCG since 2018 — first with 2 Circles, before it became part of the group — including the quote-to-order apps its sales teams use alongside Dynamics 365.

What we did

  • Kept Dynamics 365 as the system of record: the portal stores no customer data of its own
  • Built a configurable grid and form engine, so pages, forms and Dataverse queries are set up in the CMS rather than hard-coded
  • Encrypted query and form definitions on the server, so the browser cannot change which records are read or written
  • Wrote tooling that reads the live Power Pages configuration from Dataverse and compares it with the new portal, so parity is checked rather than assumed
  • Covered the portal with 575 unit tests and Playwright browser tests
  • Planned a cutover where rollback is a DNS change, because both portals share the same Dataverse

The outcome

~14,000customer logins
87pages configured in the CMS
154Dataverse queries
575unit tests

The new portal is functionally complete and preparing for go-live. It was delivered with AI coding agents under close review, and the test suite also checks that the project documentation still matches the code.

When a portal outgrows Power Pages

Power Pages is a sensible choice for a straightforward portal. Once a portal carries this much custom behaviour, a conventional .NET application over the same Dataverse data is easier to test, version and change with confidence.

Dynamics stays exactly where it is. Only the front end changes.

Read about Dynamics 365 & Power Platform →

Technology we used

.NET 10 Umbraco 17 Dataverse SDK FetchXML Dynamics 365 Power BI Embedded xUnit Playwright Claude & AI agents

Tell us about your project

A free first conversation. No salespeople — you talk directly to the developer.

Get in touch