Organisations in Latvia under Microsoft pressure are usually measured not by a formal audit but by a partner-led SAM Engagement, where per-core counting of Windows Server and SQL Server — especially under VMware or Hyper-V — and the reuse of on-prem licences in Azure decide the number. This page covers the Microsoft climate in Latvia, the local legal context, and the firms that cover the pair, listed alphabetically with pros and cons, not ranked.
Published 17 October 2025 · Last reviewed 25 March 2026
Microsoft is among the most compliance-active publishers in Latvia, where Windows Server, SQL Server, Microsoft 365 and Azure run across banking and fintech, logistics and Baltic transit, ICT and shared-service centres, manufacturing, and the public sector. As elsewhere, most Microsoft pressure in Latvia arrives as a partner-led SAM Engagement measured against Microsoft’s entitlement records rather than a formal audit — but the true-up consequences are the same.
Latvian Microsoft reviews turn on the same traps as elsewhere: per-core licensing of Windows Server and SQL Server with a 16-core-per-server minimum, the expensive host-versus-virtual-machine question under VMware or Hyper-V, double-counting on-prem licences reused in Azure without decommissioning, and the user-versus-device split on Client Access Licences. Latvia’s EU-based GDPR regime and its civil-law contract tradition shape how deployment data is handled and how disputes are resolved.
The per-core, virtualization and Azure mechanics that decide the number — the same worldwide, enforced locally.
Windows Server and SQL Server are licensed per physical core with a 16-core minimum per server; core counting is the foundation of the number.
Licensing the physical host versus individual virtual machines under VMware or Hyper-V is the most common and most expensive Microsoft finding.
On-prem Windows Server and SQL licences re-used in Azure can be counted twice if the on-prem instance is not decommissioned or tracked.
Client Access Licences must match how the estate is actually used; the wrong user/device split is a recurring over- or under-licensing gap.
Microsoft pressure usually arrives as a partner-led SAM Engagement measured against Microsoft’s entitlement records, not a formal audit.
Findings convert into an Enterprise Agreement true-up; an independent Effective License Position changes that conversation.
Latvia is a civil-law jurisdiction whose general civil law is codified in the Civil Law (Civillikums), under which the general limitation period for claims is ten years, while claims arising from commercial transactions prescribe in three years under the Commercial Law (Komerclikums). These periods are subject throughout to the Microsoft agreement’s terms and its choice-of-law and jurisdiction clauses. Confirm the position for your specific contract with qualified Latvian counsel.
Data handover is governed by the GDPR together with the national Personal Data Processing Law (Fizisko personu datu apstrādes likums) and supervised by the Data State Inspectorate (Datu valsts inspekcija). Transferring deployment or employee-linked data to a non-EU reviewer raises lawful-basis and transfer questions, and Latvian organisations commonly insist on EU processing — a procedural lever over engagement scope and timing. Public-sector buyers procure under the EU-aligned Public Procurement Law, which sets expectations of transparent, documented process.
This page is general information about the Latvia legal and procurement environment and Microsoft’s audit practices, not legal advice for your situation. Microsoft’s program is described factually; figures are labelled indicative.
Listed alphabetically with balanced pros and cons — a directory, not a ranking.
Vendor- and tool-agnostic licensing boutique working across Microsoft, Oracle, SAP, Salesforce and IBM. Engagements run buyer-side, from compliance position through negotiation and ongoing optimization.
Independent Microsoft-licensing analyst firm and recognised authority on Microsoft licensing rules, roadmap and CAL/cloud mechanics.
Central- and Eastern-European SAM and audit-support boutique with its own SAM tooling, covering Adobe, IBM, Microsoft, Oracle, SAP and VMware.
Independent multi-vendor boutique covering the major publishers plus Tier-2 vendors, with a stated 100% impartial posture.
Buyer-side independent licensing advisory with one of the broadest multi-vendor footprints, covering Oracle, Microsoft, SAP, IBM, Broadcom, Salesforce, ServiceNow and Workday.
Independent Microsoft and Azure licensing voice covering SAM, SPLA and cloud cost, with no Microsoft partnership.
Independent IT-sourcing and negotiation advisory covering SAP, Microsoft, Oracle, Salesforce, ServiceNow and Workday, with a stated no-vendor-ties model.
DEMO — listings are compiled from public information and labelled demo until the verified registry is live. Firms are listed alphabetically, never ranked. Independence is shown as a pro; a reseller, Big-Four or vendor-side audit relationship is shown as a con — each a factual trade-off for you to weigh.
Microsoft findings in Latvia typically resolve as a negotiated true-up folded into an Enterprise Agreement renewal or a new cloud commitment rather than through litigation, since Microsoft prefers to convert exposure into forward spend. What moves the number is an independent Effective License Position computed before responding, challenging host-versus-VM assumptions on virtualised SQL Server, untangling Azure Hybrid Benefit double-counts, correcting the CAL user/device split, and timing the conversation against Microsoft’s quarter and fiscal year end (30 June). In the Latvian market, the EU-versus-non-EU data question is often a practical lever over the timetable as well as the scope of any SAM Engagement.
Indicative outcomes vary widely by estate and are not scored here: independent firms report meaningful reductions where virtualization and Azure reuse are reconstructed accurately, but any figure a firm cites is self-reported and indicative until independently verified.
Up to the Microsoft hub and the Latvia hub, across to sibling markets.
Not formally, but the financial outcome can be. A partner-led SAM Engagement measures your deployment against Microsoft’s entitlement records and converts gaps into a true-up, usually at renewal. An independent Effective License Position computed before you respond changes that conversation. This is information, not legal advice.
Usually SQL Server under virtualization — whether you license the physical host or individual virtual machines under VMware or Hyper-V is the single biggest swing — closely followed by double-counting on-prem Windows Server and SQL licences reused in Azure without decommissioning the on-prem instance.
The general limitation period under the Civil Law is ten years, while claims from commercial transactions prescribe in three years under the Commercial Law; Microsoft’s reach is also shaped by the agreement’s terms and its choice-of-law and jurisdiction clauses. Confirm the position for your specific contract with qualified Latvian counsel.
Only within the GDPR and the national Personal Data Processing Law, supervised by the Data State Inspectorate (Datu valsts inspekcija). Transferring deployment or employee-linked data outside the EU raises lawful-basis and transfer questions, and Latvian organisations often insist on EU processing — a procedural lever over engagement scope and timing.
No. Every firm covering Microsoft in Latvia is listed in neutral alphabetical order with balanced pros and cons, never a ranking or a recommendation.
Tell us your situation and we route your brief to firms covering Microsoft in Latvia. The directory and matching are free for buyers, no vendor ever sees your brief, and no firm is favoured over another.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.