HILOP / Engineering

A native .NET console with deliberate provider boundaries.

HILOP is a layered .NET WPF application that keeps provider-specific behavior behind explicit contracts while preserving PowerShell where Microsoft or customer automation makes it the correct execution surface.

Current implementation

Profiles, providers, workflows, reports, and audit are first-class product surfaces.

The native console now includes runtime profiles, conditional provider setup, Graph SDK integration, live Active Directory read/write support, Exchange PowerShell provider boundaries, schema-backed AD Reports, JSON workflow definitions, licensing, and a durable local audit trail.

HILOP branding and theme editor with live preview.
Runtime branding is profile-driven with live preview and reset support.
Provider contracts

External system details stop at the boundary.

The application works through HILOP-owned models and capabilities. Active Directory, Graph, Exchange, simulator, device, and extension providers translate source-specific behavior into predictable application contracts.

  • Active Directory live reads, writes, schema discovery, reporting, and account edits
  • Microsoft Graph SDK integration with profile-selected cloud endpoints
  • Exchange PowerShell where Microsoft makes PowerShell the supported management path
  • Simulator-backed workflows and reports for local validation
Automation boundary

Workflow actions extend the platform without changing the core.

Workflow JSON can define forms, validations, variables, confirmation behavior, native actions, PowerShell actions, REST calls, delays, approvals, conditions, email, and browser launches.

  • One workflow engine supports onboarding, offboarding, transfers, and restructuring
  • Each workflow is saved as its own JSON file under ProgramData
  • Advanced behavior remains editable in code view
  • Action results are returned through the HILOP audit and result model

Architecture

Layered by responsibility.

The WPF presentation layer calls application services, which operate on domain models and provider capabilities. Providers communicate with customer systems or approved extension points.

01WPF UIOperator experience
02ApplicationOrchestration
03DomainCanonical models
04ProvidersAD · Graph · Exchange
05SystemsCustomer systems

Accepted PowerShell use

Exchange and hybrid sync use PowerShell intentionally.

Exchange recipient administration and hybrid synchronization remain PowerShell-backed because those are the supported operational surfaces. HILOP treats them as provider or utility execution paths rather than as unmanaged application logic.

Operational detail

Read setup, provider, workflow, report, and troubleshooting guidance.

Open Knowledgebase