Customer sign-in
Azure AD B2C for secure user management on Hydrajaws and Verify Auto.
Cloud
Azure development services for apps that need identity, data and CI in one place
Azure SQL, Blob Storage, Azure DevOps and Azure AD B2C behind .NET apps. We have shipped three published builds on Azure, from UK inspection to premium automotive.
3Published builds on Azure
1 May 2025Azure AD B2C closed to new customers
60 daysWarranty on the Digital Testing Platform
2 daysTo quote a change request on that build
What we build
What we build on Azure
Azure SQL and Blob Storage
Jobs and results in Azure SQL, photos and certificates in Blob Storage.
Pipelines on Azure DevOps
Workflows streamlined so branching and merging stopped slowing releases.
Power BI reporting
Dashboards that sit on the same data as the app.
Architecture
Where Azure sits in a build
An Azure build for a safety-testing app
Clients
Xamarin and .NET appFree and paid versions
Angular web UIDashboards and reports
Identity
Azure AD B2CSign-in and permissions
Cloud
AzureScalable infrastructure
KTC SDKDigital torque readings
Delivery
Azure DevOpsCI/CD pipelines
From Hydrajaws, a UK maker of portable pull testers.
Identity
Customer sign-in on Azure is changing
Azure AD B2C and its successor
Used on Hydrajaws and Verify Auto
Azure AD B2C
- No longer available to buy for new customers since 1 May 2025
- Current customers can keep using it
Microsoft recommends
Microsoft Entra External ID
- Named by Microsoft for new customer identity projects
- Where new features are being built
Source: Microsoft Azure AD B2C FAQ, checked 29 October 2026.
Builds
The three builds
Statutory inspection, United Kingdom
Work-at-height anchor and torque platform
ASP.NET Core with Azure SQL and Azure Blob Storage, fixed price per phase.
70%Faster reporting cycle
Construction safety testing, United Kingdom
Hydrajaws Limited
Azure, Azure DevOps and Azure AD B2C under a Xamarin, .NET and Angular app.
500%Surge in potential clients
Automotive safety, premium brand
Verify Auto
A premium safety-testing app on Azure, with sign-in handled by Azure AD B2C.
3Azure services in the stack
Fit check
When Azure is the right call
Pick Azure when
- Your team already runs Microsoft 365, .NET or SQL Server
- You need sign-in, storage and pipelines from one vendor
- Field or mobile apps sync to a .NET API
Look elsewhere when
- Your data and your team already sit on AWS
- You want to avoid committing to a single cloud
- The product is a static site
Related: .NET, AWS, Xamarin and .NET MAUI, and the construction and automotive sectors.
Stack
What Azure usually ships with
.NETAngular
ReactXamarin
Docker
KubernetesFAQs
What buyers ask first
Is Azure AD B2C still available?
Microsoft stopped selling it to new customers on 1 May 2025. Current customers can keep using it, and Microsoft recommends Microsoft Entra External ID for new customer identity projects. We used Azure AD B2C on Hydrajaws and Verify Auto and can scope a move for those apps.
Should we pick Azure or AWS?
The choice follows where your team, data and licences already are. We have shipped three published builds on Azure and three on AWS.
Can you repair a broken environment?
Yes. On Hydrajaws we rebuilt the development and production environments after the previous owner left no documentation.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us what you run on Azure today
Thirty minutes on your subscriptions, pipelines and sign-in. No sales pitch.