How does a CIS built on Dynamics 365 and Azure work?
A CIS built on Dynamics 365 and Azure uses Microsoft’s cloud platform as its foundation, with utility-specific functions such as billing, contract management and meter-to-cash added on top. Dynamics 365 manages customer data and processes, while Azure provides hosting, security, integration and data services.
In practice, this means your CIS shares a common data model and user experience with other Microsoft tools. Customer service agents work in a familiar interface, finance teams can report in Power BI, and IT teams can extend the platform with standard Microsoft technologies rather than proprietary code.
A platform such as MECOMS 365 for customer information follows this model. It brings together customer management, billing and meter-to-cash in one environment, so the complex tariff and regulatory logic utilities need sits on a modern, widely supported foundation. The underlying technology stack is maintained centrally, which removes much of the patching and upgrade burden from your own team.
How does a Microsoft-based CIS compare with SAP IS-U?
A Microsoft-based CIS is typically a cloud-native, configuration-led platform, whereas SAP IS-U is a long-established on-premise or hosted system that often relies on heavy customisation. The key difference is agility: Microsoft-based platforms generally offer easier upgrades, lower infrastructure burden and faster change.
SAP IS-U has served utilities well for decades, but many organisations now face end-of-support timelines, ageing custom code and rising maintenance costs. A Microsoft-based CIS addresses these concerns in several ways:
- Upgrades: updates arrive continuously in the cloud, rather than through large, disruptive upgrade projects.
- Customisation: utility rules are configured within the platform, which reduces the bespoke code that makes legacy systems hard to change.
- Skills: Microsoft technologies are widely understood, so recruiting and training are usually easier than finding specialist legacy expertise.
- Integration: open APIs and native Azure services simplify connections to portals, payment platforms and analytics.
That said, a well-run SAP IS-U estate can still be the right choice for some organisations, particularly where deep SAP integration across finance and operations is a priority. The decision should rest on total cost of ownership over 10 to 15 years, not on upfront cost alone.
Can a Microsoft-based CIS scale to millions of customers?
Yes, a Microsoft-based CIS can scale to millions of customers because Azure provides elastic compute and storage that grow with demand. Utilities can add capacity for new customers, service lines or smart meter rollouts without buying and installing additional servers.
Scale in a CIS means more than customer numbers. Billing runs, interval data processing and customer portal traffic all create peaks. Cloud infrastructure lets you increase resources during heavy periods, such as month-end invoicing, and reduce them afterwards.
When evaluating any platform, ask for evidence of live deployments at a similar scale to your own. Our platform supports over 50 million end-customers across our client base, and our clients generate over one billion invoices each year. Reference customers of comparable size, including water and multi-utility organisations such as Waternet and its cloud journey, show how this works in practice.
What are the security and compliance advantages of Azure for utilities?
Azure gives utilities enterprise-grade security through encrypted data, role-based access controls, redundant data centres and continuous threat monitoring that few individual utilities could replicate on-premise. It also supports regulatory requirements such as GDPR through strong audit trails and configurable data protection controls.
Legacy CIS environments often struggle here. Older systems can lack modern encryption, granular audit logging and integration with current security monitoring tools, while unpatched software becomes an easy target. A cloud platform addresses this through:
- Automatic security updates applied centrally, without internal patch cycles.
- Geographic failover and automated backups that support disaster recovery.
- Identity and access management through Microsoft Entra, supporting least-privilege access.
- Detailed audit trails that help demonstrate compliance to regulators.
Security remains a shared responsibility, so your organisation still needs sound governance, access policies and staff awareness. Our status as a premium Microsoft ISV partner, described on our Microsoft partnership page, also means the platform is aligned with Microsoft’s own roadmap and security standards.
How does a Microsoft-based CIS support smart meter and IoT data?
A Microsoft-based CIS supports smart meter and IoT data by connecting to metering systems through open APIs and standard protocols, then using Azure services to ingest, validate and process large volumes of readings. This feeds accurate billing, consumption insight and grid operations from a single data flow.
Smart meters can generate thousands of readings per month, and a utility may manage millions of devices. Validation rules flag unusual consumption, meter faults and potential tampering before bills are issued, which reduces errors and speeds up the meter-to-cash cycle.
Dedicated meter data management capability within the same platform avoids the data gaps that appear when billing and meter data live in separate systems. It also enables time-of-use tariffs, net metering for prosumers and demand response programmes. Beyond meters, IoT sensors for leak detection or outage notification can be added over time, since Azure is built for this kind of data.
What does migrating to a Microsoft-based CIS involve?
Migrating to a Microsoft-based CIS involves planning the migration strategy, cleansing and mapping data, configuring billing rules, integrating surrounding systems, testing, and cutting over to the new platform. Projects typically run from 6 to 18 months, depending on complexity, data volumes and the number of integrations.
A typical migration follows these stages:
- Strategy and discovery: define scope, tariffs, processes and the target architecture.
- Data migration: clean, map and validate customer, contract and billing history from the legacy system.
- Configuration and integration: set up tariffs and workflows, and connect payment, metering and finance systems.
- Testing: run parallel and regression billing to confirm accuracy before go-live.
- Cutover and support: switch over, keep the legacy system accessible in read-only mode for a period, and provide hypercare.
Data quality is the most common source of delay, so start cleansing early. Strong change management matters just as much: involve staff in selection, train them thoroughly and expect a learning curve of several months. Organisations such as Waterbedrijf Groningen illustrate how a structured approach supports a smooth move to the cloud.
When is a Microsoft-based CIS the right choice?
A Microsoft-based CIS is the right choice when you want to retire an ageing platform, move to the cloud, reduce maintenance costs and improve customer experience, without sacrificing utility-specific billing depth. It suits energy suppliers, integrated utilities, grid operators and water or heat companies facing a replacement decision.
It is particularly strong if any of the following apply:
- You are planning an SAP IS-U replacement or a wider utility cloud migration.
- Your current system cannot support self-service portals, real-time data or large smart meter rollouts.
- You already use Microsoft tools and want a consistent, integrated environment.
- You need to adapt quickly to regulatory and market change through configuration rather than custom development.
It may be less suitable if you require complete on-premise data sovereignty or have deeply embedded processes that cannot be reconsidered. Before deciding, assess vendor stability, support depth, training and proven delivery in your segment. The needs of energy suppliers differ from those of grid operators or water utilities, so look for demonstrable experience in your own market.
Hoe Ferranti helpt met uw Microsoft-based utility CIS
Ferranti helpt energie- en nutsbedrijven bij het moderniseren of vervangen van verouderde CIS-, billing- en meterdata-omgevingen met MECOMS 365, een platform gebouwd op Microsoft Dynamics 365 en Azure. Wij begeleiden de volledige transformatie, van strategie tot ondersteuning na go-live.
Dit kunt u van ons verwachten:
- Migratiestrategie: een duidelijk plan dat past bij uw bestaande landschap en risicoprofiel.
- Datamigratie: opschoning, mapping en validatie van klant-, contract- en factuurgegevens.
- Implementatie: configuratie van tarieven, processen en integraties via onze implementatiediensten.
- Testen en cutover: grondige regressietests zodat uw facturatie vanaf dag één klopt.
- Doorlopende ondersteuning: blijvende optimalisatie en support na livegang.
Ontdek de volledige MECOMS 365-oplossingen en bespreek uw situatie met onze specialisten. Neem vandaag nog contact met ons op voor een vrijblijvend gesprek over uw migratietraject.
Veelgestelde vragen
How do I get started evaluating a Microsoft-based CIS for my utility?
Start by documenting your current pain points, tariff complexity, number of customers and meters, and key integrations (payments, finance, metering, portals). Use this to build a requirements list and shortlist vendors with proven deployments in your segment, whether energy supply, water or multi-utility. Then request a scripted demo using your own billing scenarios, and ask for reference calls with customers of similar size.
What should I include in a business case when replacing SAP IS-U or another legacy CIS?
Model total cost of ownership over 10 to 15 years rather than comparing upfront costs only. Include licences, infrastructure and hosting, internal support staff, upgrade projects, custom code maintenance and the cost of delayed change requests. Also quantify benefits such as faster billing cycles, fewer billing errors, lower call volumes through self-service and quicker time-to-market for new tariffs.
What are the most common mistakes utilities make during a CIS migration?
The most frequent mistakes are starting data cleansing too late, trying to replicate every legacy customisation instead of rethinking processes, and underinvesting in change management and training. Skipping thorough parallel billing runs before go-live is another costly error. Mitigate these by starting data quality work in the first weeks, challenging every custom requirement and involving business users in testing from the start.
How can I keep the cloud costs of a Azure-based CIS under control?
Ask your vendor how infrastructure is sized and billed, and whether capacity scales down after peaks such as month-end invoicing. Set up cost monitoring and budgets in Azure, and review usage regularly, particularly data storage and interval data processing from smart meters. Agree on data retention and archiving policies early so that old meter data does not drive unnecessary storage costs.
What if my organisation has strict data sovereignty or residency requirements?
Azure lets you choose the region where data is hosted, which often satisfies national or EU data residency rules, including GDPR requirements. Confirm with your vendor which Azure regions are supported and how backups and failover are handled. If your regulator or policy demands full on-premise control, a cloud CIS may not be a fit, so clarify this with your legal and compliance teams before shortlisting.
How do I prepare my team for the change to a new CIS platform?
Identify change champions in billing, customer service and IT early, and involve them in selection, configuration workshops and user acceptance testing. Plan role-based training before go-live and refresher sessions afterwards, as it usually takes several months for teams to become fully productive. Communicate the benefits clearly, such as a familiar Microsoft interface and fewer manual workarounds, to build buy-in.
Can I phase the move to a Microsoft-based CIS instead of replacing everything at once?
Yes, many utilities phase their migration by customer segment, commodity (for example, water first, then energy) or business unit, which reduces risk and lets teams learn from each wave. Another approach is to start with meter data management or customer engagement capabilities while the legacy billing engine remains in place. Work with your implementation partner to define a roadmap that balances risk, cost and the end-of-support dates of your current system.
Gerelateerde artikelen
- What is the ROI of moving to a cloud utility CIS?
- What tasks can AI agents handle at an energy supplier?
- 6 ways AI agents help utility employees work smarter, not harder
- Why are legacy systems still so common in the utility industry?
- 5 advantages of running utility operations on a cloud-based platform
- Is Microsoft Dynamics 365 suitable as a billing platform for utilities?
- 6 steps to modernizing meter data management at a utility company
- Which validation rules are important for accurate energy billing?
- How do you choose the right utility billing software in 2026?
- What are the steps in the meter-to-cash process at energy companies?
- How does a CIS support multi-channel customer communication?
- What trends are shaping the future of CIS systems in the energy sector?
- How does a CIS support self-service portals for energy customers?
- How does a CIS manage customer contracts and tariffs?
- How does a CIS support an energy company's digital transformation?