Organisations in Georgia — the country in the South Caucasus — under Microsoft pressure are usually measured not by a formal audit but by a partner-led SAM Engagement, where the 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 Georgia, the local legal context, and the firms that cover the pair, listed alphabetically with pros and cons, not ranked.
Published 19 February 2026 · Last reviewed 2 March 2026
Microsoft is among the most compliance-active publishers in Georgia, where Windows Server, SQL Server, Microsoft 365 and Azure run across a fast-growing banking and fintech sector, IT and business-process outsourcing centres in Tbilisi, logistics and energy, and a digitalising public sector. As elsewhere, most Microsoft pressure in Georgia 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.
Georgian 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. Georgia’s civil-law contracting culture and its new personal-data regime 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.
Georgia is a civil-law jurisdiction whose contracts are governed by the Civil Code of Georgia. The Code sets a general limitation period of ten years, with a shorter three-year period applying to many contractual claims (Article 129), 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 Georgian counsel.
Data handover is governed by the Law of Georgia on Personal Data Protection, substantially modernised by the law that took effect on 1 March 2024 and supervised by the Personal Data Protection Service. Although Georgia is not an EU member, it has an EU Association Agreement and its data law draws on European standards, so transferring deployment or employee-linked data to an overseas reviewer raises lawful-basis and transfer questions — a procedural lever over engagement scope and timing. Public-sector buyers procure through the State Procurement Agency under the Law on Public Procurement, which sets expectations of transparent, documented process.
This page is general information about the Georgia 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 licensing practice covering IBM, Microsoft, Oracle, SAP and Tier-2 publishers, with a stated 100% impartial, buyer-side model.
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 Georgia 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 Georgian market, the newer data-protection regime and the role of the State Procurement Agency in public-sector deals can both affect engagement timing.
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 Georgia 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 Civil Code sets a general limitation period of ten years, with a shorter three-year period for many contractual claims, but 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 Georgian counsel.
Under the Law of Georgia on Personal Data Protection (modernised effective March 2024) and supervised by the Personal Data Protection Service. Transferring deployment or employee-linked data to an overseas reviewer raises lawful-basis and transfer questions — a procedural lever over engagement scope and timing.
No. Every firm covering Microsoft in Georgia 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 Georgia. The directory and matching are free for buyers, no vendor ever sees your brief, and no firm is recommended over another.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.