SaaS Platform For Legal Management

Leobit conducted a comprehensive technical assessment of the LMS API and supporting components. The audit confirmed that the system was generally maintainable and built with reasonable code quality, but also revealed a high number of medium- and high-priority risks that could block future growth.

The most significant risks included security vulnerabilities, insufficient logging and observability, and a lack of project-level automated testing beyond end-to-end scenarios. These gaps posed increasing operational and compliance risks as the platform was planned to scale. The audit also identified several structural and technology-level concerns that required strategic decisions rather than immediate fixes.

Listing the product on Azure Marketplace introduced a hard technical requirement. The LMS needs to support Azure Entra ID authentication via OAuth. The existing authentication model was based on ASP.NET Forms, which was not compatible with marketplace requirements or authentication best-practices. Beyond Azure Marketplace, the customer also needed an identity solution flexible enough to support SaaS, on-premises deployments, Social Media Sign-in and future self-service onboarding of hundreds of organizations while staying cost-efficient.

Leobit conducted a global analysis of identity providers and concluded that Microsoft Entra ID alone would not fully meet the customer’s long-term goals. Instead, Leobit recommended introducing a dedicated OAuth2-compliant identity provider capable of integrating with Azure Entra ID, supporting other enterprise SSO scenarios, and fulfilling other client requirements. This approach will enable the platform to remain compatible with the Microsoft Marketplace while avoiding the restrictions of Microsoft Entra ID.

Regional expansion introduced variability in how the product would be sold and used. Different markets and firm sizes required different feature sets and pricing models. The existing licensing approach was largely manual and tightly coupled to internal processes. This created friction for both the customer’s team and end users.

The operational model for onboarding customers did not scale with growth. Manual account creation, subscription handling, and role configuration consumed a disproportionate amount of maintenance effort. Leobit identified that a significant portion of engineering and support time was spent on basic user and role management rather than product innovation.

By introducing automated onboarding, OAuth-based identity flows, and customer-managed role setup, the proposed solution reduced manual operational effort by nearly 100% in this area. This allowed the customer’s team to refocus on product development and market expansion.

The technical audit showed that while the platform was stable and maintainable, several aspects of the technology stack posed medium-term risks if left unaddressed. The system was built on .NET Framework 4.7.2, a version that remains supported but is no longer actively evolving. In addition, the use of Entity Framework EDMX models introduced a long-term maintenance concern. Model-first approach is no longer being actively supported by Microsoft and is increasingly incompatible with newer tooling and development practices.

The audit also identified opportunities for Architectural improvements: decoupling business logic from infrastructure concerns, modularization, testability, and Clean Architecture principles.

Rather than recommending a risky, large-scale rewrite, Leobit proposed an incremental modernization strategy. In the short term, this included upgrading all projects to the latest supported .NET Framework version, and updating Nuget dependencies to reduce immediate technical risk, recommendations on security and observability improvements, which can bring fast results at low effort.
In parallel, Leobit outlined a long-term plan to migrate the product to modern .NET, aligning with Microsoft’s current and future development direction.

Following the technical audit and strategic discussions, the customer made a deliberate decision to move beyond incremental modernization and instead perform a full rewrite of the platform using a modern technology stack. The goal was to eliminate accumulated technical constraints and establish a foundation that could support long-term growth, enterprise requirements, and regional expansion without compromise.

Leobit worked closely with the customer to define a new target architecture aligned with modern .NET practices and hybrid cloud principles. This architecture was designed from the ground up to support scalability, security, and flexibility, while remaining simple enough to evolve as business needs change.

As part of this effort, Leobit set up a complete deployment pipeline and cloud infrastructure on Microsoft Azure. This included defining environments, automating builds and deployments, and ensuring repeatable, reliable releases across development, staging, and production.