software asset management hosting - … · sam software asset management hosting sam for hosting...

SAMSOFTWARE ASSET MANAGEMENT

Hosting SAM for Hosting (SPLA)

engagement kit

HostingSAM for Hosting engagement kit

Table of Contents

Introduction 4

Planning 6

Data collection 8

Data analysis 15

Final recommendations 16

How to use this document

3

The SAM for Hosting (SPLA) engagement kit walks you through the complete cycle of an engagement with a Hoster. The kit begins with a general introduction describing what a SAM for Hosting engagement is and the stages involved to complete one. The rest of the kit focuses on how to proceed with each stage. This includes identifying which deliverables represent billable milestones at the end of each stage.

HostingIntroduction

Hosting providers that want to offer software services to their

customers and include software licenses as part of their

service offering should use Microsoft Service Provider License

Agreement (SPLA). SPLA is the only Microsoft Volume

Licensing program that enables Microsoft products to be used

for commercial hosting.

1

SAM for Hosting (SPLA) engagementA SAM for Hosting (SPLA) engagement gives a participating Hoster and Microsoft a comprehensive overview

and analysis of the Hoster’s reporting. For the Hoster, this helps enhance its SPLA reporting and better

understand SPLA licensing rules. In addition, it helps the Hoster minimize compliance risks.

With this engagement, a SAM Service Partner takes a full inventory of all Microsoft product deployments,

usage, and entitlements used by the Hoster. The discovery process includes the Hoster’s reporting from its

previous SPLA up until the start date of the SAM engagement. If the Hoster prefers, it can perform the

discovery process itself, in which case the SAM Service Partner would validate the results.

To acquire the necessary inventory information, the SAM Service Partner or Hoster uses third-party tools,

interviews with key customer stakeholders, and questionnaires, as well as other sources. Once done collecting

data, the SAM Service Partner analyzes the information and then provides recommendations to help the

Hoster get the maximum value from its SAM engagement.


Hoster benefits• Helps enhance SPLA licensing and reporting

• Offers a better understanding of SPLA licensing and reporting

• Provides insights into actual usage and consumption

• Ensures the right licenses to fit business needs

• Minimizes risks associated with non-compliance

• Reduces costs through improved operational efficiencies

• Helps manage reporting requirements

• Improves budget predictability

• Aligns IT, procurement, and management around organizational goals

1451 Research, Hosting and Cloud Study 2017 - The Digital Revolution, Powered by Cloud, 2017

2451 Research, Hosting and Cloud Study 2017 - The Digital Revolution, Powered by Cloud, 2017

33 percent of IT budgets go

towards hosting services1

Customers have embraced the cloud, but many are just getting started.

85% of customers are beyond the discovery phase, but less than 15% of

businesses have reached broad implementation2.

5

Planning

Identify Hoster’s needs and

goals

Gather information on

licensing, IT landscape, and

business organization

Confirm scope, process, and

deliverables

Arrange access and

resources

Data collection

Take inventory of hardware

and software assets and

licensing using tools,

questionnaires, and

stakeholder interviews

Gather information on

process and procedures

Data analysis

Review and validate all

collected data

Compare deployed assets to

entitlements, and usage to

reporting

Show entire IT estate to

Hoster

Map to an optimized

environment based on

Hoster’s goals

Final

recommendations

Discuss final

recommendations with

Hoster and engage in data-

driven discussions to ensure

Hoster’s business needs and

goals are met

HOW A SAM ENGAGEMENT WORKSEvery SAM engagement focuses on four phases:

SAM Services Incentive ProgramSAM for Hosting (SPLA) engagements are funded under the SAM Services Incentive Program, a worldwide

offering designed to help Microsoft partners, such as you, increase adoption of SAM best practices. By

participating in the program, you can engage with a Hoster or deepen existing relationships that can lead to

new sales and opportunities.

How to file for a SAM Services Incentive ProgramTo learn how to file for a SAM Services Incentive Program, visit Software Asset Management.

A SAM for Hosting (SPLA) engagement provides recommendations and best practices for taking license inventory

and reporting. The intent of the engagement is to help the Hoster maximize SAM for Hosting, minimize compliance

risks, and identify cost-saving opportunities.

Deliverables

Executive Overview Report

Licensing & Infrastructure

Optimization

Recommendations Report

Deliverables

Effective License Position

(ELP)

Deliverables

Raw data from information

collected concerning

hardware and software

deployments

Deliverables

Letter of Engagement

HostingIntroduction

https://partner.microsoft.com/en-US/Licensing/software-asset-management

A SAM for Hosting (SPLA) engagement helps a Hoster identify all of its licenses and software installations,

develop a strategic plan for hosting, and ensure the right policies and procedures are put in place to

effectively manage reporting and promote growth.

The first stage of such an engagement focuses on planning. Within this stage, you will achieve the following:

• Identify the Hoster’s needs and goals

• Gather information about the Hoster’s environment

• Discuss the project and arrange access and resources

Identify the Hoster’s needs and goalsPlanning begins by discussing goals and objectives with the Hoster. What you discover will help you define

scope and configure your inventory tool to get the necessary information to help identify technical readiness.

Questions to consider asking a Hoster to identify goals and objectives:

• What are your objectives from the engagement?

• What hosting delivery models are you using?

• What do you hope to achieve with the engagement?

• What is your timeline?

Gather information about the Hoster’s environmentYour first meeting with a Hoster concerns scoping its company, culture, licensing, and IT landscape to gain a

better understanding of its environment and needs.

The following categories can help you organize such information:

• Company profile: What does the hosting business model look like? What kind of hosted services are

provided to the end customers and what is the delivery model?

• Basic information: Get confirmation of the full set of Microsoft products offered to end customers

and compare it against the Hoster’s current product reporting and invoicing.

• Licensing information: Does the company have an existing SPLA agreement? If so, what is the

coverage and when does it expire? What do the license management processes and practices look

like?

• Infrastructure: Ask relevant questions regarding the Hoster’s environment to help you effectively

plan for data collection from infrastructure and stakeholder perspectives. Get a description of all

physical and virtual servers used to provide hosted services.

• Microsoft software: Get a description of all installations of Microsoft software products on all

physical servers and virtual machines used to offer hosted services.

Note: Before beginning your assessment, be sure to highlight the key deliverables of a SAM engagement so the

Hoster knows what to expect.

HostingStep 1: Planning

6


Discuss the project and arrange access and resourcesBased on the preliminary information you’ve gathered, you can create a full project plan. This plan will

contain an outline for data collection and analysis, a detailed list of deliverables, and a timeline with

deadlines. This will help establish the Hoster’s expectations and your accountability.

DeliverablesPrior to working with a Hoster, you will provide a Letter of Engagement explaining what to expect during your

SAM engagement. This letter must be provided as necessary Proof of Execution (PoE) in order for you to

collect payment.

The letter must include at a minimum:

• An explanation of the SAM engagement being performed, including a list of all Hoster deliverables.

• Scope of the engagement, including any scope limitations.

• Engagement activities and any associated requirements (locations, access, people).

• Dates and timelines.

• SAM Service Partner project team members and their relevant Microsoft Certified Professional (MCP)

credentials.

• A list of key Hoster contacts, including the Executive Sponsor. The list must include names, titles, email

addresses and roles in the SAM engagement process.

• Planned disclosure of engagement deliverables to Microsoft.

Letter of Engagement Explains what to expect during the SAM engagement.

7

HostingStep 1: Planning

HostingStep 2: Data collection

The objective of data collection is to secure a clear, documented, and shared understanding of the Hoster’s

complete server estate (physical and virtual), license management processes and practices, offerings and use of

Microsoft products, datacenters and domains. Within this stage, you’ll acquire a documented license

responsibility per environment (internal, dedicated, co-located, license mobility, SPLA) and for the whole scope

of the engagement. This will come prior to data analysis and formation of a report.

Data collection provides you with a foundation for all SAM recommendations and guidance about how a

Hoster can optimize SPLA reporting. If you collect the information from the Hoster with a questionnaire, you

must review the information provided by the Hoster and request clarification as needed. Completeness has to

be verified and license responsibility per deployment must be determined.

Take inventory of IT assets and licensingYou need to prepare for taking a full inventory of hardware and software deployments and licensing. This

assessment includes how the technology is being used and by whom. You can accomplish this through

inventory tools, questionnaires, and stakeholder interviews. Before you can move forward however, you must

first work with the Hoster to establish the following parameters:

• Choosing the right tool

• Defining the scope inventory

• Implementing an inventory tool

• Gathering data

• Determining license responsibility

• Conducting an onsite workshop

Choosing the right tool

When choosing the right inventory tool, keep in mind that each tool supplier has its own process framework, so

be sure to understand the way each tool works (don’t assume they all function the same way). Using multiple

tools helps you discover and analyze the data and provide a more complete view of a Hoster’s environment. In

some cases, the Hoster may already have an inventory tracking system or other tools may be able to augment

the types of data that the Hoster’s tools collect.

Some considerations when choosing or recommending an inventory tool include:

• What inventory tools are already deployed within the organization? What scope of the environment do

they cover? What data points are they capable of capturing and reporting?

• Will deploying an agent-less or agent-based tool be more effective?

• What are the strengths and weaknesses of the tools being considered? Will one or more of them collect

all required data points (i.e. hardware, software, virtualization details across a variety of hypervisors—

Hyper-V, VMware® and XenServer®—and more)?

• Is it optimal to deploy and monitor a tool remotely or on-premises?

• How will the tool(s) gather data from PCs, servers and mobile devices that connect to the network

remotely?

4



5

• If using an inventory tool that the Hoster already has in place, make sure it’s configured

correctly and can scan the full IT environment.

• Consider how the tool is licensed. The optimal tool will collect the right data and align with

the Hoster’s budget, whether the tool requires a license or subscription or is free.

Defining the scope of inventory

For any SAM engagement, collecting all relevant inventory and licensing data is a standard best practice. The

SAM for Hosting (SPLA) engagement provides a participating Hoster and Microsoft with a comprehensive

overview and analysis of the Hoster’s reporting during the Hoster’s current and previous SPLA up until the

start date of the SAM engagement. You must strive to ensure identifying and accurately representing in the

Established License Position (ELP) historical license positions including usage (servers, users, software), which

existed historically but does not exist in the current baseline position. Microsoft requires that you document

historical usage in a factual data-centric approach.

Implementing an inventory tool

The standard approach for deploying an inventory tool for a SAM for Hosting (SPLA) engagement includes:

• Define the scope of machines to be inventoried. The recommended scope would include a

description of Hoster’s datacenters, all physical servers providing hosted services and all virtual

machines deployed on all physical servers offering hosted services.

• Determine the scope of active devices that contain data to be collected. For Hosters running Active

Directory Domain Services (or Directories in the case of multiple, separate domains/forests), include

in scope all machines with Active Directory activity reported in the last 30 days (timeframe can be

adjusted according to Hoster’s circumstances).

• Prepare the environment for scanning and data collection. Attain a scan coverage of greater

than 90 percent of the devices in the scope, using either a combination of available tools or

iterative scans to continually increase coverage rates.

• Determine what additional data source can be used as the secondary data set to compare reporting

requirements. This is a standard SAM best practice used to validate licensing data gathered by the

inventory tool. If user counts for the secondary data set vary significantly from the server count, then

a problem most likely exists.

Agent-less tools

• Understand domain, network, firewall and other considerations that will affect a tool’s ability to

access various portions of a Hoster’s environment.

• Open firewalls, make firewall exceptions, deploy Group Policy Objects, open specific ports and take

other steps to ensure that the tool can access all targeted machines.

Keep in mind that agent-less tools typically need to be run multiple times, especially at different times of

the day and different days of the week, to catch the variety of users, shifts, time zones, and such.

5

Agent-based tools

• Ensure agents are communicating regularly so that data is fresh.

• Ensure agents are deployed to the scope of target machines.

• Get the right refresh schedule and agent coverage to collect data with a single snapshot

extraction that doesn’t require iterations.

• Ensure data cleanliness. The quality of the scan coverage is top priority, beginning with

Active Directory Domain Services.

• Run third-party tools when needed, in addition to Hoster-provided tools, to achieve proper cleansing.

• Work with the Hoster to ensure there is a repeatable cleansing process in place going forward.

Gathering data

When collecting information, consider taking the following actions:

1. Request that the Hoster explains its hosting service offerings.

2. Ask the Hoster to confirm the full set of Microsoft products offered to end customers. Compare the

results to the Hoster’s current product reporting (invoicing).

3. Ask relevant questions regarding the Hoster’s environment that enable you to effectively plan data

collection from an infrastructure and stakeholder perspective. By the end of this stage, you should

have a clear picture of:

• Environments

• Datacenters

• Number of servers (physical and virtual per environment)

• Deployment types

• Type of virtualization software in use

• Software inventory tools in use

• Operations management software in use

• Other affiliates providing hosting services

• Microsoft products and versions in use and features enabled

• How servers and software are provisioned, decommissioned, and tracked

• Dates when each server was put into production

• How the company manages user access

4. Obtain additional support documents from the Hoster. This may include but not be restricted to:

• Licensing entitlement documentationo Reportingo Invoiceso License transfers o License mobility agreements

• Written communications from Microsoft in regards to special agreements

• Any non-standard agreement or amendment that the Hoster believes is agreed to with

Microsoft


5

• Accepted evidence, including, but not limited to:

o End customer contractso Itemized invoiceso End customer license verification forms

(In the event that sufficient evidence can’t be provided by the Hoster, you must work with the

Hoster to get formal declaration from end customers to confirm license responsibility matches

that described by the Hoster).

In the event that full coverage isn’t feasible, a sample percentage coverage can be agreed upon

with the responsible Microsoft SAM Engagement Manager.

• Deployment documents

o Fixed asset register

• Third-party tools

o Proof of concept for internal tools that the Hoster may suggest be used as part of data

gatheringo The output data that will be supplied from any proposed third-party toolo Verification of tools for completeness, accuracy, and integrity

If you’re collecting the information from the Hoster through a questionnaire, you must review the

information provided by the Hoster and request clarification as needed. You must then verify completeness.

Determining license responsibility

You can determine license responsibility per deployment by taking the following actions:

• Investigate Active Directory domains and trusts to ensure all are addressed throughout the process

• Establish datacenter to domain mappings

• Establish server to datacenter mappings

• Establish end customer to server mappings

• Cross-reference all domains and servers through multiple data sources

• Review historical invoicing to identify end customers who may have left Hoster and/or address gaps

in technical historical data

• Establish the environment structure (SPLA, internal, co-located, dedicated)

• Establish and document license responsibility for each environment, noting restrictions based on the

understanding of each specific environment from the above exercise (e.g. license responsibility lies

with the Hoster for the operating system layer in a shared hosting environment)

For operating system environments to which the Hoster has no access (e.g. “black boxes”), the Hoster

shall either ask the respective customers to grant temporary access to such environments to allow data

collection, run the scripts to collect the data themselves or – with Microsoft’s prior approval – obtain

written customer declarations listing Microsoft products deployed with installation dates. If unlicensed

software installations are found in such environments the disputed deployments will be presented in a

separate appendix for resolution between the end customer and the Hoster for licensing via SPLA or

another appropriate VL program in advance of finalization of the engagement.


5

Conducting onsite workshops

Be sure to set up an onsite workshop. The purpose is to gather information (or alternatively oversee the

administrator or representative of the Hoster doing so) by receiving responses from representatives of the

Hoster, performing scans of the infrastructure with scanning tools, analyzing Active Directory, and reviewing

system properties, information, and documentation provided by the Hoster (log files etc.). Scanning of the

Hoster’s infrastructure with the scanning tool is mandatory for successful completion of the engagement.

The Hoster must ensure that the system administrator is present during the onsite workshop and has

administration access to the entire environment/infrastructure (physical and virtual).

Sufficient access needs to be confirmed prior to the onsite workshop. During the onsite workshop the

following information will be collected:

Datacenters. A description of the Hoster’s datacenters (how many and their locations)

Physical servers. A description of all physical servers used for hosted services, including the following

information:

• Name of each server (names shall be changed to anonymous if linked to confidential

information)

• The datacenter location for each server (if the Hoster has several datacenters)

• Indication of whether the server is dedicated to one customer or shared (multi-tenant)

• Deployment date for each physical server

• Number of physical processors on each physical server

• Number of physical cores on each physical server

• Description of server clusters, which servers are included in which cluster, high

availability/load balancing enablement, and so on. For example, if virtual machines on the

server are configured to move among physical host servers in the cluster to optimize nodes

performance

• Description of which hypervisor types are used for virtualization

Virtual machines. A description of all virtual machines deployed on all physical servers used for hosted

services, including the following information:

• Name of each virtual machine (names shall be changed to anonymous if linked to

confidential information)

• Indication of each virtual machine deployment (i.e. which physical server)

• Indication of the number of virtual processors/virtual cores assigned to each virtual machine

and the history of changes (if any)

• Indication of the date of deployment for each virtual machine

• Indication of whether the server is dedicated to one customer or shared (multi-tenant)

Microsoft software. Get a description of all installations of Microsoft software products on all physical

servers and virtual machines used for hosted services, including the following information:

• Product name including version

• Indication of where the software product is installed: on which physical server (if deployed on

a physical layer) or virtual machine (if deployed in a virtual machine)

• Date when each software product was installed

• License type: SPLA, end customer’s VL license (specify use of License Mobility through

Software Assurance), MSDN, SQL as part of SAP etc.


5

• If the product is licensed per Subscriber Access License (SAL) such as Office, Skype, Exchange,

SharePoint, Dynamics, SQL per SAL etc.)

• Whether Hoster has a policy in place to identify and control the users/devices?

• How many users can access the software product as of the date of the assessment?

• Which license types are assigned to which users (basic, enterprise etc.)?

• Are there any group policies or software (e.g. AppLocker) restricting access of users to

software products?

• What is the historical user/device count to identify the number of licenses needed in each

month for the period of scope as defined in the Description section?

• If the software product is included as part of licenses for another software product (e.g. SQL

for System Center)

• Other information necessary to determine license count

Non-access to virtual machines. A Hoster may not retain access to all hosted environments licensed

through SPLA. You must work with the Hoster to attain the necessary information to verify compliance. You

also must support the Hoster in informing end customers of their obligations to provide such information.

In exceptional scenarios, you may accept an end customer declaration of software deployments with end

customer executive confirmation. Any instances where you can’t reasonably verify software deployments

must be documented within the Executive Summary deliverable.

end customer licensed deployments. You need to represent all hosted deployments as licensable on

SPLA unless otherwise evidenced by the Hoster through an end customer contract or end customer

declaration. The Hoster must be given the appropriate time to secure such evidence before the report is

considered final. Some Microsoft software hosted in a multi-tenant environment may be licensed with the

Microsoft License Mobility Program. All non-licensed mobility deployments must be represented in the

report as SPLA.

Uninstalled software products. Any software uninstalled after the inspection has started (meaning the

date of the Letter of Engagement) will be recorded as deployed in the report. You must also investigate and

report in this section if the Hoster has been hosting Microsoft software before it had a valid Microsoft

agreement in place to permit such hosting.

Historical license position. Try to identify the historical license position including usage (servers, users,

software), which doesn’t exist in the current baseline license position. Microsoft will presume that any

unreported use began upon commencement of each end user relationship with the Hoster, unless the

Hoster reasonably demonstrates a different scope and duration. Microsoft therefore requires you to

document historical usage in a factual data-centric approach including how the historical license position

was calculated. Include this information within the ELP.

The following data points should be used to calculate historical usage

• User creation date

• Software installation date

• First invoice date

• End-user relationship start date

o Customer contract start date

o Customer service start date

o SPLA agreement start date


5

DeliverablesAt the conclusion of this stage, you’ll create a set of reports that summarize your findings including the

following:

The Hoster will have time to review and validate the preliminary reports and make final adjustments.

Raw dataProvides details of all the data gathered about hardware and software

deployment during this stage.

• Server creation date

o Active Directory

a) Where enabled use; when-created to current date

b) Where disabled use; when-created to when-changed

o VMware

o Invoicing records

In the event the Hoster hosted Microsoft software under the definition of the Software Services provision

prior to any SPLA agreement, it’s expected that the SAM partner notifies Microsoft (the responsible

Microsoft SAM Engagement Manager) that such usage has been identified and agree on the scope of

handling this historical look back.


HostingStep 3: Data analysis

4

After gathering all of the information, you analyze it and prepare a report. The report will contain your

analysis along with any deliverables. The Established License Position (ELP) deliverable will contain per-

product comparisons for each month of actual software deployments and reported licenses. If needed, you

can request clarifications from the Hoster for the information gathered during the onsite meeting. You

should also outline any limitations that may influence the reliability of the information in the report.

For data analysis, you want to focus on achieving the following:

• Reviewing and validating all collected data

• Comparing actual usage and consumption to reporting

• Mapping to an optimized environment based on the Hoster’s goals

One key benefit of a SAM engagement is that it gives you a clear picture of a Hoster’s entire IT landscape,

which you can then share with them. This includes an accurate view of all of a Hoster’s license entitlements

and reporting requirements. By understanding these entitlements, you can help the Hoster identify over-

and under-reporting so that it can purchase and report any necessary additions to bridge licensing gaps.

DeliverablesThe SAM for Hosting data must be reviewed and agreed upon with the Hoster as an accurate point-in-time

reflection of the Hoster’s current IT environment of hosted services. Based on the inputs and data

collection, you will complete the following required analysis:

• Reconciliation analysis between license entitlements and deployment data, including the

application of license benefit and optimization rules (upgrades, downgrades, promotions,

etc.).

• Aggregation and review of data from stakeholder interviews, noting any information that

was either unavailable or challenging for the Hoster to gather.

Established License Position

(ELP)

Provides details related to license entitlements and reporting

requirements based on deployments, usage and consumption.


HostingStep 4: Final

recommendations

10

Final resultsAt the conclusion of the SAM engagement, you will sit down with the Hoster and go over a detailed set of

reports that provide the following information:

• Recommendations

• Next steps

RecommendationsRecommendations come from your generated reports and cover a wide variety of topics. Points to keep

in mind include the following:

a. Report Windows Server Datacenter instead of Windows Server Standard due to the large

number of virtual machines deployed on a host server or high availability enabled to reduce

license costs.

b. Report SQL per SAL instead of SQL per core if the number of users is small and the Hoster

can control the users accessing the software to reduce license costs.

c. Report less expensive software editions (if the Hoster requires less functionality).

d. Consider implementation of SAM tools to manage reporting needs.

e. Provide the Hoster with insights into actual customer usage and consumption.

f. Provide the Hoster with guidance to contractual obligations and recommendations for end

customer contracts.

g. Provide the Hoster with education on license mobility requirements.

h. If applicable, offer additional engagements on datacenter security (SAM Cybersecurity

engagement).

i. If applicable, offer consulting on CSP migration and/or migration from Hosted Exchange to

Exchange Online or Office 365 and others (if needed, provide contact to Microsoft for follow-

up).

j. Help the Hoster establish a precise and reliable practice for software and license inventory to

be able to track what software is installed and what licenses need to be reported as well as to

keep complete and accurate historical information. Establishing standard practices can help

reduce waste, avoid unnecessary costs and business risks and streamline the entire

organization.

Next stepsUpon completion of the engagement, deliver the report to the Hoster and ask the Hoster to submit any

comments to the report within 10 calendar days from receipt as well as provide approval of the report. You

should consider valid comments from the Hoster and update the report if necessary. At the end of the 10

days, the report will be considered final and will be submitted by you to Microsoft.


HostingStep 4: final recommendations

9

DeliverablesAt the end of the engagement, you will provide the Hoster with the following set of deliverables:

Executive Overview Report Contains an executive summary, summary of project background

and scope, engagement results, recommendations and next steps

Licensing and Infrastructure

Optimization Recommendations

Report

Contains an analysis on how to optimize your infrastructure,

improve operational efficiencies and manage your reporting

requirements

Microsoft Deployment, Usage

and Entitlement Analysis Reports

Provides the Effective License Position (ELP) spreadsheet (NOTE:

Defined in “Deliverables to Microsoft” section below)

You must notify the Microsoft SAM Engagement Manager when the Proof of Execution is uploaded into

the required system as designated by Microsoft. Proof of Execution includes the Letter of Engagement as

well as the following deliverables due upon the completion of the SAM engagement:

• Effective License Position (ELP)

• Licensing and Infrastructure Optimization Recommendations Report

• Letter of Confirmation (Only applicable for Hoster countries listed below)

o Required: China

o Advised: India, Malaysia, Indonesia, the Philippines and Vietnam.

The Letter of Confirmation should be drafted after completion of the SAM Engagement. It requires

Hoster chop (stamp) or email from Hoster corporate domain confirming provision of SAM

Engagement.

The Letter of Confirmation must also include the following statement: “This is to confirm Microsoft

SAM Service Partner <insert Partner Name> has implemented SAM service <insert SAM

Engagement Type> to Hoster <insert Hoster name>.”

All additional deliverables due to the Hoster as listed above must be available to Microsoft upon request.

Rates and engagement levels Rates by (physical) server count can be found in the SAM Incentive Rates and Level Workbook located at:

http://aka.ms/samincentives

Rates: SAM INCENTIVE RATES tab

Levels: SAM INCENTIVE LEVEL tab

SAM resources

SAM Services Program

Incentive Guidehttp://aka.ms/SAMIncentiveGuide

http://aka.ms/samincentives

http://aka.ms/SAMIncentiveGuide

software asset management hosting - … · sam software asset management hosting sam for hosting...

Documents