Technology consulting & managed services
thenar builds Azure platforms, identity systems, and production software, and operates them as a managed service.
Technologies we work in
Microsoft Azure
Microsoft Entra ID
HashiCorp Terraform
Kubernetes
Red Hat Ansible
GitHub
.NET
PythonOperating principle
Technology decisions should hold up in production.
We design and build Azure environments, from the landing zone and network architecture through migration. Infrastructure is defined in Terraform and governed with Azure Policy.
02Identity architecture on Microsoft Entra ID, including Conditional Access, privileged access management, and access governance. We map controls to frameworks such as NIST SP 800-53.
03Delivery platforms on GitHub Actions and Azure DevOps pipelines, Azure Kubernetes Service with Helm and Argo CD, and observability with OpenTelemetry and Grafana. We build these platforms and operate them.
04Legacy applications are modernized in stages, with functionality moving into .NET and Python services while the existing system remains in production. Integration with Dynamics 365 and SAP is part of the same practice.
05AI systems that work with enterprise data, using Azure AI Search for retrieval and Azure OpenAI and Anthropic Claude for orchestration. Every build includes evaluation sets, access controls, and human approval gates.
06We operate technology environments under managed services agreements. The scope runs from monitoring and alert triage through Microsoft 365 and Intune administration to ITIL-aligned incident and change management.
Engineering discipline
Deployment, access control, telemetry, and failure handling are settled during design and delivered with the system.
Before a platform ships, it has a defined path to production, a named owner, alerting that has been tested, and a documented rollback procedure.
Designs are reviewed with the team that will build them.
Module boundaries, deployment order, and operating assumptions are written down before build starts.
Build includes the path to production.
Pipelines, environments, and access controls are built alongside the application and exercised before cutover.
Operating experience feeds the backlog.
Incident reviews and operational cost shape what is built and changed next.
01
Cloud & infrastructure
Shared Terraform modules and Azure Policy now define how an industrial manufacturer builds and governs its Azure subscriptions.
Outcome
A new business unit now lands on the platform in days rather than the quarter it once took. Every infrastructure change reaches the platform team as a pull request, and Azure Policy reports drift from the security baseline the day it happens.
02
Identity & security
After an identity rebuild on Entra Privileged Identity Management and Conditional Access, a state public health agency grants administrative access only when it is requested, approved, and time-limited.
Outcome
Standing privileged access is down from 41 accounts to three break-glass accounts held in escrow. When an assessment asks who holds privileged access and why, the agency answers from its own Entra ID Governance exports. Microsoft Sentinel alerts on any activation outside a change window.
03
AI engineering
An assistant built on Azure AI Search and Azure OpenAI answers a midstream energy operator's on-call questions with citations. Retrieval is trimmed to the documents each requester is cleared to read.
Outcome
On-call engineers start with the assistant and follow its citations into the source documents. The eval set catches grounding regressions before a change ships. Production actions still require a person's approval before they run.
In a large environment, a change to identity, networking, or a shared platform touches systems owned by other teams.
Public-sector engagements are designed around the evidence an assessment will require.
Growing organizations reach a point where infrastructure practices built for a smaller team no longer hold.
