The CSP and SPLA programs cover different but related ways of using Microsoft’s technologies. CSP is primarily intended for providing and managing Microsoft cloud subscriptions for individual customers. SPLA enables a service provider to use eligible Microsoft software when delivering hosted applications, infrastructure, and other software services to end users.
This combination allows us to integrate Microsoft solutions into a broader service for managing the IT environment. The customer thus obtains not only the appropriate licenses or subscriptions, but also assistance with selection, implementation, configuration, management, and support.
What we offer as a partner
We help customers plan, implement, and manage Microsoft cloud services and licenses for hosted environments.
Advisory on license selection: we review user, application, and infrastructure requirements and propose an appropriate subscription or licensing model. We consider the number of users, required functionality, how the services will be used, and the expected growth of the environment.
Subscription setup: we arrange orders for Microsoft cloud services and assist with assigning licenses to users. The scope of subscriptions can be adjusted to organizational changes and the actual needs of individual teams.
Implementation and migration: we assist with environment setup, configuration of users, domains, identities, and security policies, and with the transition from existing systems to the Microsoft cloud.
Environment management: we monitor service health, perform agreed administrative tasks, support subscription changes, and provide support to users and administrators.
Licensing of hosted services: under the SPLA program we ensure appropriate licensing of eligible Microsoft server products that we use to deliver services for customers in our infrastructure.
When selecting a solution, we consider who uses the software, where it runs, who manages the infrastructure, and how the service is accessed by end users. This reduces the risk of incorrect licensing and helps the customer choose a model that matches the service’s technical design.
Microsoft Cloud Solution Provider
The Microsoft CSP program enables partners to provide customers with Microsoft cloud services and related support services. The partnership involves managing subscriptions, licenses, and the customer relationship via the Microsoft Partner Center.
Through CSP we can provide customers with services such as Microsoft 365, Microsoft Azure, Dynamics 365, Microsoft Power Platform, and other eligible Microsoft offers. The exact availability of specific products, plans, and subscription terms depends on Microsoft’s current catalog for the given market.
Microsoft 365
Microsoft 365 combines services for productivity, communication, collaboration, device management, identity protection, and data security. The feature set depends on the selected plan and may include services such as Exchange Online, Microsoft Teams, SharePoint Online, OneDrive, as well as Microsoft 365 desktop and web applications.
We help customers select plans that fit their users and security requirements. During implementation we can handle user account setup, domain connection, license assignment, baseline security configurations, and the migration of email and data from the existing environment.
License management allows adding user seats to existing subscriptions and ordering new services. Changes, cancellations, and reductions in license counts are subject to the terms of each subscription, its term length, and Microsoft’s rules under the new commerce model.
Microsoft Azure
Microsoft Azure provides compute, networking, data, and other cloud services. Customers can use it to host virtual servers, applications, databases, backups, development environments, and other IT solutions.
When planning an Azure environment, we take into account required performance, availability, security, connectivity, and expected consumption. The solution can include virtual networks, virtual machines, storage systems, identity management, monitoring, and other services required for the specific workload.
Because a significant portion of Azure services is billed based on consumption, regular usage monitoring is important. Proper rightsizing of resources, shutting down unnecessary systems, setting budgets, and tracking costs help prevent unexpected increases in monthly spend.
Dynamics 365 and Power Platform
Dynamics 365 brings together business applications for areas such as sales, customer service, finance, operations, and other organizational functions. Microsoft Power Platform includes tools for building business applications, process automation, analytics, and creating business solutions with little or no traditional coding.
Available licenses depend on the application, user type, and usage. Before implementation it is therefore necessary to define which business capabilities users actually need and which data, processes, and integrations will be included in the solution.
Subscription and user management
Microsoft Partner Center enables partners to manage customer relationships and their subscriptions. A partner can order a new subscription for a customer, add licenses to an existing subscription, and view offers and information required to provide support.
Subscriptions can have different terms and billing methods. For a given offer, monthly, annual, or longer terms may be available, with payment options varying by product and Microsoft’s conditions. The selected term can affect price, flexibility, and the options for reduction or cancellation of a subscription.
Before ordering, we therefore assess the customer’s actual needs, the expected number of users, and the required level of flexibility. A longer-term subscription may be appropriate for steady users, whereas for temporary projects or rapidly changing teams it makes sense to consider more flexible options where available for the chosen product.
Security and access management
Using Microsoft cloud services requires proper management of identities and administrative privileges. Misconfigured accounts, overly broad permissions, or insufficiently protected access can increase the risk of environment compromise.
When setting up services we therefore pay particular attention to admin accounts, multi-factor authentication, permissions assignment, and the separation of user and administrative roles. The final scope of settings depends on the selected licenses, the Microsoft environment, and the agreed scope of management.
Partner access to the customer’s environment must be established in a controlled manner and only to the extent necessary to deliver the agreed services. Microsoft uses mechanisms for managing partner administrative relationships that enable fine-grained role definition and time-bound access.
Microsoft Services Provider License Agreement
The Microsoft SPLA program is intended for service providers and software solution providers who want to use eligible Microsoft products to deliver software services to their customers.
A software service is a solution in which the customer directly or indirectly accesses Microsoft software managed by the service provider. This can include hosting business applications, virtual servers, remote desktops, databases, web solutions, and other managed IT environments.
SPLA is not a traditional purchase of perpetual licenses for the customer. License rights are tied to the service provider, who uses the software to deliver services to end users. The customer uses the software as part of a hosted or managed service and typically does not obtain a perpetual license for the product.
Licensing of hosted infrastructure
SPLA is used for eligible Microsoft server and other products listed in the current Microsoft Service Provider Use Rights documents. Frequently used products may include Windows Server, Microsoft SQL Server, remote access licenses, and other products needed to run hosted solutions.
Each product has its own rules and licensing metrics. Licensing can depend on processor cores, number of users, devices, connections, or other criteria. Therefore, the rules for one product cannot automatically be applied to another.
In a hosted server environment, it is necessary to consider the physical and virtual infrastructure, the number and type of processors, the placement of virtual machines, how users access the environment, and any use of shared infrastructure for multiple customers.
Windows Server
In hosted environments, Windows Server is used as the operating system for virtual and physical servers. It can run business applications, web services, file systems, directory services, and other infrastructure components.
The licensing model depends on the product edition, the physical infrastructure, and the number of cores. In virtualized environments, it is also necessary to account for rights to run individual instances of the operating system and the distribution of workloads across hosts.
SPLA allows us to include the use of eligible Windows Server editions in the hosted service. The customer thus uses the server environment as an integral part of the service, while the provider is responsible for license reporting and compliance.
Microsoft SQL Server
Microsoft SQL Server is used to run relational databases and applications that require Microsoft’s data platform. In a hosted environment, the database can be dedicated to a single customer or be part of a broader managed application service.
Licensing depends on the selected edition, the technical architecture, and the applicable licensing metric. In some scenarios, it is based on the number of cores; in others, on user or device access, if such options are still available for the product and program.
Before implementation, we assess the expected workload, required availability, database sizes, and licensing requirements. This allows us to select the appropriate edition and architecture and avoid licensing capacity the solution does not need.
Remote desktops and applications
SPLA can also be used for services where users remotely access desktops or applications running on the provider’s infrastructure. Such an environment is suitable for centrally running business applications, working from remote locations, and using programs the organization does not wish to install on every individual device.
In addition to the underlying server operating system, the necessary remote access rights and any additional Microsoft products must be correctly licensed. The licensing model depends on the access method, number of users, and the software included.
Monthly usage reporting
One important characteristic of the SPLA program is usage reporting. In line with contractual terms, the provider must track license usage and report it regularly to the authorized partner or to Microsoft.
Billing is based on reported usage and the applicable prices for each period. This enables aligning license counts to actual service usage, but it requires the provider to keep accurate records of installed and used Microsoft products.
For the customer, this means the costs of Microsoft software can be included in the monthly bill for the hosted service. The level of cost may change if compute resources, number of users, number of accesses, or the amount of software used increase.
The difference between CSP and SPLA
CSP and SPLA are not interchangeable programs. CSP is used primarily for subscriptions to Microsoft cloud services tied to an individual customer’s environment. SPLA is used when the provider uses Microsoft software to deliver a hosted software or infrastructure service to its end users.
With Microsoft 365, the customer typically receives user licenses for services delivered by Microsoft. Under SPLA, the customer uses a service that the provider delivers and manages on its own or rented infrastructure.
A given solution can include both programs. For example, an organization can use Microsoft 365 through CSP while also using, in the provider’s hosted environment, a business application based on Windows Server and Microsoft SQL Server and licensed via SPLA.
The right choice depends on the technical architecture, ownership and management of the infrastructure, the type of software, and how end users access it.
Why Humanfrog
We do not treat Microsoft licensing in isolation from the IT environment in which it is used. We help customers align licensing with the real requirements of users, applications, servers, security, and operations.
For cloud services, we can take care of subscriptions, initial configuration, migration, user management, and ongoing support. For hosted services, we incorporate SPLA into an end-to-end service across infrastructure, operating systems, databases, monitoring, and technical support.
This approach enables the customer to obtain Microsoft technologies together with expert support and management. The goal is transparent licensing, effective use of the subscribed services, and an IT environment tailored to the organization’s actual needs.
Let's talk about your project.
