All projects
Dynamics 365 (CRM)QatarProductionClient project — details kept high level

MSDF National e-Services Platform

Citizen e-services platform for Qatar’s Ministry of Social Development and Family, running in production. I built its integration service from scratch, developed platform APIs and request-workflow plugins, and worked on the portal.

  • ASP.NET Core
  • Dataverse
  • OIDC
  • Azure Service Bus
  • Power Automate

01 Overview

Project
MSDF National e-Services Platform
Country
Qatar
Role
Backend & Dynamics 365 developer — integration service, APIs, portal and plugins
Context
Client project · Initium Solutions
Environment
ASP.NET Core (.NET 8) · Dynamics 365 / Dataverse
Period
2025 — Present

02 Problem

Citizens apply online for social services, and each request moves through a multi-step workflow in Dynamics 365.

Deciding a request needs data from several government systems, and the platform has to react when those systems update it.

03 What I did

  • Built the integration service from scratch.
  • Developed platform APIs and worked on the citizen and staff portals.
  • Developed Dataverse plugins for request steps and status changes, with Custom Workflow Activities, Power Automate and Dynamics 365 customization.
  • National-ID sign-in (OpenID Connect) and integrations with government systems over REST, OAuth 2.0, webhooks and Azure Service Bus.
  • Background processing, notifications, digital wallet cards and QR-verifiable certificates.
  • Added request-level timing that logs every CRM call behind an API request, then fixed what it showed: caching rate-limited lookups, retry with backoff and batching in bulk jobs.

04 What the platform does

  • Online service requests

    Citizens apply for social services and follow each request through its workflow.

  • National identity

    Single sign-on with the national identity provider.

  • Connected government data

    Citizen data and request status exchanged with government systems.

  • Workflows & SLAs

    Multi-step request workflows and approvals in Dynamics 365, with working-hours due dates.

  • Notifications

    Portal and push notifications as requests progress.

  • Verifiable documents

    Certificates and digital cards that can be verified by QR code.

05 Screenshots

1 / 8 Citizen portal home — service categories and search

Public pages, captured from a development environment.

06 Architecture

  1. Channels

    • Citizen portal
    • Staff portal
    • Mobile apps
  2. Backend

    • E-services APIsASP.NET Core
    • Integration service
    • Background processing
  3. Platform

    • Dynamics 365 / DataversePlugins · workflows
    • Azure Service Bus
  4. External

    • National identity(External system)
    • Government systems(External system)
Simplified, high-level view.

07 Security

  • OpenID Connect sign-in with the national identity provider.
  • OAuth 2.0 between services.
  • Signed, time-limited links for downloadable passes.
  • Structured logging for traceability.

08 Technology

Backend

  • C#
  • .NET 8
  • ASP.NET Core Web API
  • Hosted Services

Dynamics 365

  • Dataverse
  • C# Plugins
  • Custom Workflow Activities
  • Power Automate
  • FetchXML

Integration

  • OpenID Connect
  • OAuth 2.0
  • REST
  • Webhooks
  • Azure Service Bus

Delivery

  • Firebase Cloud Messaging
  • Apple Wallet
  • Google Wallet
  • QR codes
  • Azure DevOps

09 Outcome

  • Platform in production; its launch was publicly announced by Initium Solutions.
  • Citizen requests connected end to end with government systems.
  • Slow requests can be traced to the exact CRM calls behind them, and bulk updates finish without rate-limit failures.

Work together

Have a backend, Dynamics 365 or enterprise integration project?