ATMIC SYSTEMICSRequest a consultation
Menu
HomeAbout Us
Solutions All solutions
Cloud ServicesMicrosoft AzureAmazon Web ServicesMicrosoft 365 & Office 365Google WorkspaceEnterprise Mobility + SecurityCloud scenarios
Cyber SecurityUnified Threat ManagementAnti-Spam SolutionsData Loss PreventionEndpoint Detection & ResponseEnterprise Endpoint SecuritySSL & TLS Certificates
IT InfrastructureEnterprise Server SolutionsStorage ServicesBackup & Data ProtectionDisaster RecoveryVirtualizationInfrastructure scenarios
End-User ComputingData Security & ProtectionDesktop Deployment & ManagementIT Consultancy ServicesPrinters & PeripheralsVDI & Thin ClientsDesktops, Laptops & Workstations
Software Licensing Licensing overviewMicrosoftAdobeVMware by BroadcomCitrixCorelAutodeskRed HatSUSE Linux
Resources Resources overviewInsightsIllustrative scenarios
Careers Career opportunitiesCurrent openingsInternships
Contact UsRequest a consultation

Microsoft licensing

Microsoft licensing

Plan Microsoft cloud subscriptions, desktop software and server licensing around real users, devices, workloads and administration needs.

Request a licensing quote
RequirementMetricTermLifecycleMicrosoft

Licensing overview

Map the requirement before comparing offers.

Microsoft licensing spans productivity services, desktop operating systems, cloud PCs, server software, databases and development tools. The right starting point is not a product name: it is a record of who needs access, which devices and workloads are involved, where services will run and which security or compliance capabilities are genuinely required.

Microsoft 365 Business plans, Microsoft 365 enterprise plans and Office 365 enterprise plans coexist. Their included applications, security capabilities and commercial rules are not interchangeable. Microsoft Teams packaging can also vary by plan, geography and purchase route, so every quotation should identify the exact stock-keeping unit and inclusions rather than relying on a familiar suite name.

Atmic can help organise requirements and prepare a licensing request for Microsoft 365, Office 365, Windows, Windows Server, SQL Server, Windows 365 and related Microsoft software. Advice is based on the information supplied and the current Microsoft terms applicable to the proposed purchase; it does not imply Microsoft partner or reseller status.

Relevant software areas

What teams commonly evaluate.

  • Microsoft 365 Business and enterprise subscriptions for productivity, identity, device management and security
  • Office 365 enterprise plans where cloud productivity services are required without the broader Microsoft 365 bundle
  • Windows 11 business editions and Windows 365 Cloud PC options
  • Windows Server, access licences and virtualisation-related licensing considerations
  • SQL Server editions and deployment models for physical, virtual and cloud workloads
  • Project, Visio, Power Platform, developer tools and other role-specific products

Typical business uses

Where the requirement starts.

  • Standardising business email, Office applications and collaboration for a growing workforce
  • Selecting identity, endpoint management and information-protection capabilities for managed devices
  • Licensing a physical or virtual Windows Server estate with appropriate user or device access
  • Reviewing subscriptions before renewal, a merger, a tenant consolidation or a change in working model
  • Separating always-on requirements from project-based or specialist software needs

Commercial and technical considerations

Details that can change the right quotation.

Users, devices and identities

Record employees, shared accounts, frontline users, contractors, service identities and device ownership. A licence assigned to a person is not automatically a substitute for every device-based or server-access requirement.

Plan composition

Compare the exact service plan and add-ons. Desktop applications, mailbox features, archiving, endpoint management, advanced identity, security and compliance capabilities differ across Microsoft 365 and Office 365 offers.

Server and workload metrics

Windows Server and SQL Server can introduce core, server, user, device and virtualisation considerations. Hardware inventory and the proposed virtual-machine layout should be reviewed before quantities are estimated.

Existing rights and agreements

Document current subscriptions, perpetual licences, Software Assurance, cloud commitments and purchase channels. Upgrade, mobility, hybrid or transfer rights should never be assumed without checking the applicable terms.

Operational ownership

Licensing is only one part of the decision. Tenant administration, joiner-mover-leaver processes, security configuration, data retention and support responsibility need named owners.

Discovery checklist

Information to gather before requesting a quote.

  • Which Microsoft services and applications are required by each user group?
  • Are desktop applications needed, and on how many or what kinds of devices?
  • Which identity, device-management, information-protection and compliance controls are in scope?
  • What physical processors, cores, virtual machines and server workloads must be licensed?
  • What licences, subscriptions, agreements and tenant assets already exist?
  • Are Teams, telephony, Project, Visio, Power BI or other add-ons required?
  • What renewal date, deployment sequence and support boundary must the quotation reflect?

Renewal and lifecycle planning

Treat renewal as a decision point.

  • Maintain a licence register tied to people, devices, servers, tenants and renewal dates.
  • Reclaim assignable subscriptions promptly when roles change or staff leave, subject to current reassignment rules.
  • Review service usage and add-ons before renewal rather than simply repeating the previous quantity.
  • Recheck product terms when architecture, hardware, virtualisation, external access or purchase programme changes.
  • Keep order confirmations, agreement records and deployment evidence together for future reconciliation.
Important

Product packaging, availability, metrics and terms can change. Final recommendations and quotations should be checked against the vendor’s current official product terms for the selected region and purchasing channel. No partner, reseller or authorisation status is implied on this website.

Licensing FAQ

Questions worth resolving early.

Are Microsoft 365 and Office 365 the same?

No. Office 365 enterprise plans centre on cloud productivity services, while Microsoft 365 plans can combine those services with Windows, identity, device-management and security capabilities. Exact inclusions vary by plan, and both product families remain relevant to requirements discussions.

Is Microsoft Teams included with every Microsoft 365 plan?

Do not assume so. Teams availability and packaging can differ by plan, geography and transaction channel. A quotation should state whether Teams is included, excluded or supplied through a separate offer.

Can one Microsoft 365 subscription be shared by several employees?

Named-user services are generally assigned to an individual account. Shared devices, shared mailboxes and frontline scenarios have separate rules and should be designed explicitly rather than handled by sharing credentials.

Do Microsoft 365 subscriptions cover Windows Server or SQL Server?

Generally not as a blanket entitlement. Server products have their own editions, metrics and access requirements. The design should identify the server product, version, hardware, virtualisation and users or devices that connect to it.

What should we provide for a Microsoft licensing quote?

Provide user groups, required applications and security features, device types, server and virtual-machine inventory, current agreements, tenant details, location, preferred term and renewal deadline. Atmic can then prepare a structured request for current options.

Microsoft

Prepare a better licensing request.

Share the users, devices, workloads, deployment model, current entitlement and renewal date.

Request a licensing quote