Bulgarian organisations under a Microsoft licensing review are usually measured not by a formal audit but by a partner-led SAM Engagement, where per-core counting, SQL Server under virtualization and Azure Hybrid Benefit drive the number. This page covers the Microsoft licensing climate in Bulgaria, the local legal context, and the firms that support the pair, listed alphabetically with pros and cons, not ranked.
Published 9 December 2025 · Last reviewed 31 December 2025
Microsoft is among the most actively managed publishers in Bulgaria, where Windows Server, SQL Server, Microsoft 365 and Azure sit across financial services, telecoms, the fast-growing IT-outsourcing sector centred on Sofia, and the public sector. Heavy virtualization and hybrid-cloud adoption across those estates is what creates licensing exposure.
With roughly 62–63% of organisations reporting a software audit within any twelve-month period globally, and around 52% now bringing outside defense help, Bulgarian estates with large virtualised Windows and SQL footprints are squarely in scope. Microsoft pressure usually arrives as a partner-led SAM Engagement measured against Microsoft’s entitlement records rather than a formal audit, and the most expensive findings tend to come from SQL Server licensed at the virtual machine rather than the physical host, and from Azure Hybrid Benefit double-counting.
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.
Bulgaria is an EU member and a civil-law jurisdiction. Contract is governed by the Obligations and Contracts Act (Закон за задълженията и договорите), and the general limitation period is five years, with a shorter three-year period for certain claims including periodic payments — which can constrain how far back Microsoft reaches, subject always to the Microsoft Business and Services Agreement, the Product Terms and the agreement’s choice-of-law clause.
Data handover is governed by the GDPR together with Bulgaria’s Personal Data Protection Act and supervised by the Commission for Personal Data Protection. Transferring deployment or employee-linked data to a non-EU party raises lawful-basis and transfer questions a well-advised buyer can use to shape engagement scope and timing, and Bulgarian organisations commonly insist on EU processing. Public-sector buyers procure under EU public-procurement rules and the Public Procurement Act.
This page is general information about the Bulgaria 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.
ServiceNow-centric licensing and estate-reconciliation practice that also covers Salesforce, Oracle, Microsoft, SAP, IBM and Adobe. Reconciles entitlement against actual consumption ahead of renewals and reviews.
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.
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 Bulgaria typically resolve through a negotiated Enterprise Agreement true-up rather than litigation, with Microsoft preferring to convert a gap into expanded commitments at renewal. What moves the number is an independent Effective License Position, correctly licensing SQL Server at the host where appropriate, reconciling Azure Hybrid Benefit, matching User and Device CALs to actual use, and timing the conversation against Microsoft’s quarter and fiscal year end.
Indicative outcomes vary widely by estate and are not scored here: independent firms report meaningful reductions where an Effective License Position is rebuilt or a virtualization assertion is challenged, but any figure a firm cites is self-reported and indicative until independently verified.
Up to the Microsoft hub and the Bulgaria hub, across to sibling markets and services.
Not exactly. Most Microsoft licensing pressure in Bulgaria arrives as a partner-led SAM Engagement measured against Microsoft’s entitlement records, rather than a formal contractual audit — but the financial exposure can be similar, and the same evidence and counting discipline applies. This is information, not legal advice.
Typically SQL Server licensed at the virtual machine rather than the physical host under VMware or Hyper-V, followed by Azure Hybrid Benefit double-counting where on-prem licences are re-used in Azure without decommissioning the original instance. Per-core minimums and the User-versus-Device CAL split are common secondary gaps.
Microsoft’s contractual reach is shaped by the Microsoft Business and Services Agreement and the Product Terms, and by Bulgarian limitation rules — the general limitation period under the Obligations and Contracts Act is five years, with a three-year period for certain claims. The reviewed period depends on your agreement and its choice-of-law clause; confirm with qualified Bulgarian counsel.
Only within the GDPR and Bulgaria’s Personal Data Protection Act, supervised by the Commission for Personal Data Protection. Transferring deployment or employee-linked data outside the EU raises lawful-basis and transfer questions, and Bulgarian organisations often insist on EU processing — a procedural lever over scope and timing.
No. Every firm covering Microsoft in Bulgaria 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 Bulgaria. 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.