Non-production EnvironmentSAM Engagement Kit

SAMSOFTWARE ASSET MANAGEMENT

B

Non-production EnvironmentSAM Engagement Kit

Table of Contents

Introduction 1

Inventory Tool Implementation Guidance 5

Interpretation of Inventory Data 10

Deployment Considerations 12

Licensing Considerations 15

SAM Policies 23

This document was created in October 2014 with minor updates in June 2016.

SAM SOFTWARE ASSET MANAGEMENT

1

Non-production environment licensing and optimization are complex challenges that many customers need to work through. To maintain a healthy asset management system and realize maximum value from their investment, customers need to be able to understand what defines their non-production environment, who is accessing that environment, and how the software running in that environment is licensed.

Software Asset Management (SAM) provides customers with valuable insights into their software assets. A Non-production SAM Engagement can help customers work through business and licensing challenges that are raised when organizations create custom software or operate any type of lab environment that must be differentiated from production. Microsoft has developed this kit to provide guidance, tips, and best practices on how customers can use SAM to optimize their non-production environments. It’s important to understand that non-production environments can be found at customers of all types, not just customers developing custom software.

Challenges OpportunitiesModern non-production environments can be complex, dynamic, or ever-changing, which makes it difficult for an organization to:

• Understand how non-production systems are deployed, developed, tested, decommissioned, and rebuilt through the application development cycle.

• Get a clear picture of the organization’s software footprint.

• Understand the licensing subscriptions available.

• Understand who needs to be licensed.

Implement SAM best practices to help the customer:

• Understand the difference between non-production and production environments.

• Understand common licensing mistakes, such as purchasing or renewing more subscriptions than necessary, under- or over-licensing users from development teams, or not taking advantage of new version rights.

• Manage their licensing subscription needs.

• Protect developer licenses from product key leakage within and outside of the organization.

Defining Non-production versus Production EnvironmentsTo understand what the customer may fairly believe is a non-production environment, you must first rule it out as a production environment. Then, and only then, should you begin to assess whether all of the users accessing the software products in that environment are properly licensed to do so. Production Environment has a new contractual definition in the October, 2014 PUR: “Production Environment means any Physical or Virtual OSE (Operating System Environment) running a production workload or accessing production data, or any Physical OSE hosting one or more Virtual OSEs running production workloads or accessing production data.”

A production environment is defined as an environment that is accessed by end users of an application (such as an Internet Web site) and that is used for more than acceptance testing and feedback of that application. Some scenarios that constitute production environments include:

• Environments that connect to a production database.

• Environments that support disaster-recovery or backup for a production environment.

• Environments that are used for production at least some of the time, such as a server that is rotated into production during peak periods of activity.

Non-production EnvironmentIntroduction

2

Non-production Environment

Non-production environments are used exclusively for purposes other than production. Examples include: Application Development: where software application developers develop code.QA/Testing Environments: where developers, dedicated testers, or other non-business users test new code and applications (which may or may not have been developed by the customer). Staging Environments: if truly isolated from production data and environments, this is where the team deploys tested and validated codes and apps to prove the deployment before a final deployment to production.If you are unsure whether or not a physical server or operating system environment should be considered production, apply the following test: can the customer permanently migrate this environment offline – including any data that it is consuming – without impacting end users? If the answer is “no,” then you should treat the environment in question as production.Understanding the licensing footprint in a non-production environment requires working closely with the customer to obtain the correct information. It is essential to gather a broad set of data and customer-supplied reports, as well as to learn from the customer how they manage and define each of the following: • Development• Testing

• Staging• User Acceptance Test (UAT)

• Other Lab Environments• Production Environments

Important Update to Microsoft Developer Tools Use RightsAn update to the Microsoft Product Use Rights (PUR) in October 2014 updated the developer tools use rights. The update allows developers to run virtual machines (VMs) dedicated to development/test workloads side by side with VMs dedicated to production workloads on the same host hardware. Prior to this change, customers were required to run development/test workloads licensed under Microsoft developer tools licenses on host hardware dedicated to development/test use. This update redefines the word “environment” to mean “operating system environment” rather than physical hardware. This means that existing MSDN software terms now allow Virtual Machines (VM) used for development and test purposes to be run alongside those used for production on a common host, as long as each VM is used exclusively for one or the other.The change makes it easier and less costly for customers to run hybrid development/testing/production environments in order to consolidate servers and move workloads freely within their data center (a trending usage case that otherwise requires full production licenses).Historically, a “production environment” referred to an environment defined by physical hardware. It included the physical hardware as well as any guest virtual machines running on the hardware. The October 2014 PUR introduces an updated definition that excludes virtual machines that are dedicated to development/test use. Only physical hosts running production workloads or hosting guest virtual machines running production workloads, or virtual machines running production workloads are “production environments.” A virtual machine running a development/test workload on a physical host that also supports virtual machines running production workloads will be licensable under a developer tool license such as MDSN. Note 1: Whether or not the deployment is production or non-production, when System Center Configuration Manager (SCCM) manages and secures an OSE (physical or virtual), a production license is required for that use of SCCM.Note 2: Office Professional acquired via MSDN may be used in a production environment. However, as of October 1, 2012, new and renewing Visual Studio Ultimate with MSDN and Visual Studio Premium with MSDN subscribers may no longer use Visio Premium or Project Professional in production.

Introduction

If you are unsure whether or not a physical server or operating system environment should be considered production, apply the following test:

❶ can the customer permanently migrate this environment offline including any data that it is consuming?

❷ without impacting end users?

If the answer is “no,” then you should treat the environment in question as production.

3

Non-production EnvironmentIntroduction

Objectives of the EngagementWorking collaboratively with the customer, you have the opportunity to help them develop a solid understanding of developer tools licensing and to empower them to improve the health of their development tools asset management system in the future.

Partner Benefits• A Non-production Environment SAM Engagement

has the potential to be one step towards a larger customer opportunity.

• Increase customer satisfaction by helping your customers solve critical business challenges.

• Expand your business and solution offerings by increasing your expertise and skill level.

• Become a valued strategic advisor.

Customer Benefits• Increased understanding of how Developer Tools

licensing works and the best ways to receive value from their licensing investments.

• Achieve control of licensing management as well as reduced costs through operational efficiencies.

• Increase standardization, gain insights into company assets, and improve internal licensing communication.

• Establish a solid foundation for achieving future organizational objectives as well as minimization of non-compliance risk.

Non-production Environments Engagement Kit ComponentsThe Non-production Environments SAM Engagement Partner Kit includes:

Customer-Facing Presentation DeckPresentation to support customer conversations about how SAM can help customers implement or optimize non-production licensing.

Inventory Tool Implementation GuidanceGuidance in determining inventory tool requirements and best practices for tool implementation.

Data Interpretation and Technical RequirementsAdvice on interpreting inventory tool data and technical considerations.

Deployment ConsiderationsOverview of what to consider when deploying non-production solutions.

Licensing ConsiderationsLicensing guidance including what to consider and the licensing implications in non-production environments.

SAM PoliciesSAM policy and procedure guidance for a successful SAM program involving non-production environments.

Use the kit as a resource for successful SAM engagements. You’ll find guidance, best practices, tips and tricks, and more. Resource links are listed for more detailed information on specific topics.

SAM Services IncentiveThe SAM Services Incentive Program is a worldwide offering. It is designed to increase customer adoption of SAM best practices while simultaneously providing Gold SAM Competency partners with opportunities to engage with new customers or deepen existing customer relationships through value-added SAM engagements. The Non-production Environments SAM Engagement is eligible for funding through the SAM Services Incentive Program as of January 2015.

4

Non-production EnvironmentIntroduction

ResourcesMicrosoft Partner Network: SAMmspartner.microsoft.com/en/us/pages/licensing/software-asset-management.aspx

Update to Developer Tools Use Rightsmicrosoft.com/licensing/about-licensing/product-licensing.aspx

Microsoft Partner Network - Development platformhttps://partner.microsoft.com/en-us/solutions/development-platform

SAM Partner Playbookhttps://assets.microsoft.com/en-us/SAM-Services-Partner-Playbook.zip

SAM SOFTWARE ASSET MANAGEMENT

5

Inventory Tool Implementation Guidance

Non-production Environment

In order to understand the customer’s deployment footprint in non-production environments it is essential to perform a broad scan of both production and non-production environments. This includes working closely with the customer to obtain additional reports and data, such as MSDN usage reports, Active Directory data, and HR records for a complete picture of usage and deployments. This will help enable the partner to cross reference log in counts on machines and to get a better picture of who is engaged in the either of the environments.

Your most important source is your customer. Customer conversations are key to an effective SAM engagement, and should help provide the insights you need to fully understand the customer’s non-production environments. Examples of questions to ask your customer to get valuable information are included later in this document.

Choose the Right Tool for Scanning Non-production and Production EnvironmentsWhen choosing the right inventory tool, keep in mind that each tool supplier has its own process framework. Be sure to understand the way each tool works—don’t assume they all function the same way. Using multiple tools helps to triangulate the data and provide a more robust view of a customer’s environment. Also, while in some cases the customer may already have an inventory tracking system, other tools may be able to augment the types of data the customer’s tool collects, as there are many data collection solutions for different customer environments.

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?

• In deploying additional tools, will an agent-less or agent-based tool be more effective? Consider the effort to deploy and the likelihood of successful data collection.

• What are the strengths and weaknesses of the tools being considered? Will one or more of the tools being used collect all required data points—hardware/software, virtualization details across a variety of hypervisors (Hyper-V, VMware, XenServer), SQL Server Instance/database details, etc.?

• Work with the customer to determine if it is optimal to deploy and monitor a tool remotely or on-premises.

• Consider scalability and remote workers. How will the tool gather data from PCs, servers, and mobile devices that remotely connect to the network?

• When using an inventory tool or system the customer already has in place to collect primary deployment and usage data, ensure that the customer’s tool is configured accurately and it is scanning the full IT environment.

• When determining the best tool for the customer’s needs, consider how the inventory tool is licensed as well. The optimal tool will collect the right amount of data and align with their budget, regardless of whether or not the inventory tool is a perpetual license, a subscription license, or free.

As you are obtaining inventory data through the chosen discovery tool, talk with IT Professionals and other key stakeholders to get additional critical information needed to supplement other inputs. At a minimum, find out the answers to these

6

questions:

Do you engage in software development and testing on-site?

Have you used external consultants during the current licensing agreement term?

How do the developers test their software?

How many Microsoft platform/.NET developers?

How many IT pros, Architects, PMs, Testers, Database Administrators and non-Microsoft developers access non-production servers running Microsoft software?

How many of those users are interacting with non-production Lync, Exchange, SharePoint, BizTalk and Dynamics servers?

Do they access the development environment?

Are they licensed under your agreements or the 3rd party’s?

If licensed by the 3rd party, can you provide documentation of this?

Is this consistent across all divisions of your company?

Which types of roles manage testing?

Who is overseeing moving software projects through development, testing, Staging User Acceptance Testing to production cycle?

How do you manage decommissioned servers?

The following are examples of reports and data sources, which can be supplied by the customer to cross-reference data obtained through the inventory:

Active Directory Records Query AD to define the scope of active users and clients to capture in the hardware/software inventory datasets.

HR DataHR employee records can be a valuable secondary source for active user counts, and can be leveraged to map users to different profiles if an organization’s licensing varies across different profiles. This requires working closely with an organization to understand what HR systems, reports, etc. are available and how data can be provided to facilitate the profile mappings.

Anti-Virus SoftwareAnti-virus software can be useful in providing the second set of data to compare license counts. For example, the anti-virus installation count should be similar to the number of Office device counts.

Server ReportsEnsure that server reports, regardless of the tool(s) leveraged, provide all necessary metrics — hardware specs (processor and core counts), host and guest mappings, VM movement details, software inventory (including edition specificity, which is sometimes lacking from tools), and detailed data on particular products (i.e., SQL Server editions, clustering, instance/DB details, etc.) in order to fully assess the relevant licensing positions.

LicensingMicrosoft licensing agreement information and contracts, including amendments, approvals for upgrade and downgrade rights, etc.

Non-production EnvironmentInventory Tool Implementation Guidance

7

Inventory Tool Implementation To understand your customer’s non-production environment and help them optimize their non-production licenses, conduct a broad inventory scan. Some of the areas to uncover for a broad inventory scan include:

Determine the scope of active devices that contain data to be collected. For customers running Active Directory Domain Services (or Directories in the case of multiple separate domains), include in scope all machines with active directory activity reported in the last 30 days at a minimum (the time frame can be increased according to customer circumstances). In fact, for non-production environments, licensing is required for the peak usage reached for a given product SKU since the customer’s last license reconciliation. This is called the high water mark. Although discovery tools cannot necessarily identify peak usage, data from the inventory can be used with other evidence, like MSDN reports provided by the customer and interviews with key customer personnel such as IT Professionals and project leads, to triangulate what the high water mark has been.

Prepare the environment for scanning and data collection. Attain a scan coverage of at least 90% 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 license counts. This is a standard SAM best practice and is important to validate licensing data gathered by the inventory tool. If user counts for the secondary data set vary significantly from the server and client counts, then a problem most likely exists. This is also useful in identifying any ghost servers or clients.

Ensure the scope of devices includes production and non-production servers and clients for a Non-production Environment SAM engagement. Include machine and domain names in the inventory reports. Identify servers labeled as development that may be running in production.

Identify workstations and servers used by Microsoft Developer Network (MSDN) subscribers. Facilitate the identification of devices covered by MSDN subscriptions by employing various methods such as determining preferred user for devices, linking last logged-on user to devices, or by soliciting feedback from customer personnel that have an MSDN subscription. This step should be completed as early as possible in the data collection phase of a Non-production SAM engagement.

For any product running on environments identified as non-production, ensure that any discovery tool output includes the following:

• All users accessing these servers along with the feature sets they have accessed.

• List of users, sites, membership, and time stamp details where applicable.

• Comparison of users to devices where Project professional and MSDN subscriptions respectively have been allocated in order to avoid double counting.

Tailor your approach depending on the organization’s user/device profiles. For example, non-Windows clients (i.e., Macs, netbooks, etc.), mobile devices, work group machines, thin clients, etc. not managed via AD should be identified through alternative sources.

Make sure to look carefully at product editions to determine if the customer is using higher or lower product editions than they have purchased. Remember that the customer cannot use the latest product versions if MSDN has expired.

Tailor your approach depending on the organization’s user/device profiles. Check mobile, remote, and vendor users to identify outsourced development team members as an additional data point to determine if this set of users is properly licensed for what is being used by them. If testing mobile applications, ensure that all software involved in that process is accounted for.

Non-production EnvironmentInventory Tool Implementation Guidance

Ensure the scope of devices includes production and non-production servers and clients for a Non-production Environment SAM engagement.

8

Agentless ToolsAgentless inventory tools mean that an agent does not reside on the local machine and deployment commonly does not require administrative access to machines. If using an agentless tool:

• Understand domain, network, firewall, and other considerations that will affect a tool’s ability to access various portions of a customer’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.

• Agentless tools typically need to be run multiple times, especially at different times of the day and days of the week, to capture variables such as users, shifts, and time zones. It is recommended to run the tool multiple times over a period of 30 days.

Agent-Based ToolsAgent-based tools means that a central system monitors and collects the inventory results from remote agents which are deployed on networked desktops, servers, laptops, or any other networked device. If using an agent-based tool:

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

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

• With the right refresh schedule and agent coverage, data collection from an agent-based tool should be a single snapshot extraction with no iterations necessary.

• Cleansing data is an important part of data analysis to remove incorrect data. Data is considered clean if it is relatively error-free. Focus on ensuring data cleanliness — the quality of the scan coverage is the top priority, beginning with active directory domain services.

- Run third-party tools in addition to customer-provided tools to achieve proper cleansing.

- As a best practice, work with the customer to ensure there is a repeatable cleansing process in place going forward.

Tips and Tricks• Send a detailed questionnaire to the customer in advance that

includes, at a minimum, the questions provided in the Inventory Tool Implementation Guidance section of this document

• Get admin rights lined up ahead of time.

• Understand when license subscriptions were purchased and installed since specific product use rights vary by date.

• Appoint one person to be the admin and gate keeper for server capacity planning and licensing subscription management.

• Document each server and record physical host details since these impact license metrics.

• Ensure all servers have been inventoried. Recommend the removal of any older decommissioned servers as necessary.

Non-production EnvironmentInventory Tool Implementation Guidance

Appoint one person to be the admin and gate keeper for server capacity planning and licensing subscription management.

9

• Naming conventions are important. Ask your customer what naming conventions they have in place. Look to server names to help identify their function. Recommend customer implementation of a consistent naming convention as a best practice.

- Example of how to name a server: IRedDSQL001

› I (first letter of company name)

› Red (domain)

› D (dev. server)

› SQL001 (standard)

- The only letter that would change in the name of a production server is the third bullet. The letter “D” would be replaced by a “P” for production or by a “U” for UAT, and so forth.

• Associating servers to a development property, test property, UAT property or production property simplifies the identification of servers. This enables operations to provide reports that will show which server is assigned to each property.

• Understand how multiplexing impacts server licensing, when customers use hardware or software to pool connections, reroute information, or reduce the number of devices or users that directly access or use a product.

ResourcesImproving SAM Engagement Accuracy for MSDN, Visual Studio and Dev Test Environmentshttps://assets.microsoft.com/en-us/improving_sam_engagement_accuracy_msdn_visual-studio_test_environment.pptx

Microsoft SAM Tools Overview https://www.microsoft.com/en-us/sam/tools.aspx

Microsoft System Center Service Manager http://technet.microsoft.com/en-us/library/hh305220.aspx

Microsoft System Center Configuration Manager http://technet.microsoft.com/en-us/library/gg682129.aspx

Windows Intune https://www.microsoft.com/en-us/cloud-platform/microsoft-intune

Non-production EnvironmentInventory Tool Implementation Guidance

Naming conventions are important. Ask your customer what naming conventions they have in place.

Associating servers to a development property, test property, UAT property or production property simplifies the identification of servers. This enables operations to provide reports that will show which server is assigned to each property.

SAM SOFTWARE ASSET MANAGEMENT

10

The goal of interpreting inventory data is twofold: reveal potential value for the customer by helping them save costs on unnecessary developer licensing in the non-production environment and guide the customer on the best way to manage their complex software licensing going forward. Production and non-production environments change quickly and software asset management for these environments can be challenging. There will often be a need to provide licensing recommendations for the non-production environment as a result of issues with developer tool licensing. The most prevalent issues in this environment are:

• Incorrect licensing of Microsoft Visual Studio and Visual Studio with MSDN products.

• Incorrect licensing of software products sourced from MSDN.

Based on the data you should be able to identify and share the following with the customer:

• MSDN over-licensed, under-licensed, or over-deployed products.

• Circumstances or events which may have led to over-licensing or under-licensing.

• License subscription needs and recommendations.

Interpretation of Inventory Data for Non-production Environments• You will need to work with the customer to define what falls within non-production and production environments. Ask

the customer how they differentiate the two environments. This is a crucial layer to the SAM engagement, as this human element cannot be replicated through a tool. When identifying test and development servers watch out for servers labeled as development that are actually running as production. There are many ways to do this, but it comes down to how the customer manages their test environments. Determine the following:

- Do customers have standard naming conventions?

- Are there different IP subnets?

- Are there multiple domains?

• When reviewing the inventory tool output, look for anomalies such as client count results that differ greatly from the number of employees. Question anything that seems unusual to ensure your analysis is an accurate representation of the customer’s environment.

• Data from the inventory tool should be combined with data from other sources (IT service management and finance, for example) so informed decisions can be made.

• The customer needs to know who is managing what in order to inventory assets properly. If the organization is using a service provider, clarify what was purchased and who is managing it.

• Check MSDN licensing to see if non-production is separated from production and if there are a reasonable number of active MSDN subscriptions.

Non-production EnvironmentInterpretation of Inventory Data

11

Non-production EnvironmentInterpretation of Inventory Data

Evaluating the Number of Users and Licensing Needs1. Determine the Current Footprint by Evaluating Key Data Points

a. MSDN high water mark of assignments

b. Inventory users of non-production infrastructure

c. Inventory non-production deployments

2. Determine Owned Licenses

a. Microsoft License Statement (MLS)

b. Declaration of MSDN ownership from Microsoft Partners

3. Gap Comparison Cadence

a. Annually for Microsoft Enterprise Enrollments

b. Monthly for Select and Open Enrollments and any MSDN subscriptions assigned, or products that do not appear in an enterprise agreement

ResourcesMPN License Grants – Product Use Guidemspartner.microsoft.com/en/us/pages/membership/internal-use-software.aspx#comp

Visual Studio Subscription (formerly MSDN Subscription) Admin Guidemsdn.microsoft.com/en-us/subscriptions/aa948862.aspx

Developer Tools Engagement Framework for SAM Engagementshttps://partner.microsoft.com/en-US/Licensing/software-asset-management#Navigated_Rich_Text_Node_8

Improving SAM Engagement Accuracy for MSDN, Visual Studio and Dev Test Environmentshttps://partner.microsoft.com/en-US/Licensing/software-asset-management#Navigated_Rich_Text_Node_8

Customer Briefing: How to Count Deployments and Licensing Assignmentshttps://partner.microsoft.com/en-US/Licensing/software-asset-management#Navigated_Rich_Text_Node_8

SAM SOFTWARE ASSET MANAGEMENT

12

Prior to initiating deployment, it is important to educate the customer on what to expect of a SAM engagement. Highlight known risks, misconceptions, complexities, and common tasks involved with a SAM engagement. Explain what the customer needs to know about MSDN and Visual Studio, common risks, and what you envision for steps to ensure the customer is correctly licensed going forward. This will help eliminate confusion and objections, while creating customer awareness ahead of time around the type of reporting they will need to supply for the engagement. Ensure there is time for the customer to ask all of their questions.

With your help, customers can successfully navigate the non-production environment engagement. There are implications beyond licensing; IT decisions may affect budgets, the manner in which IT is expensed, employee training, and more. Check with your customers to see if they have considered these aspects and provide them with guidance to help them successfully optimize their non-production environments. Encourage the incorporation of best practices to support successful employee training and developer tools subscription management.

Customers need to be able to be able to understand their current non-production software usage and licensing models in order to align to their near and long-term business needs. As a partner, you play an important role in helping the customer ensure that their current licensing is appropriate and fully compliant, and that they are optimally set up to address their future goals.

Deployment Best Practices For Non Production Environments• Ensure the customer understands the differentiators between production and non-production.

• Understand how the customer currently manages all their licensing subscriptions.

• Educate customers that all users accessing non-production must be licensed to do so, even if they are not coding in Visual Studio.

• Work with the customer to consolidate non-production environments whenever possible.

- Hosting disparate deployments can lead to underutilized server instances, generating additional licensing needs. Consolidating helps use more of the server’s resources. If you have a Development Host that can handle 20 VMs (to oversimplify, assuming each VM takes the same amount of resources), and you have two Hosts with 10 VMs, then you can consolidate and get rid of one of the Hosts which saves money in terms of hardware, maintenance, power, etc. It also simplifies tracking non-production vs production for licensing considerations when non-production is as consolidated as possible, instead of having small non-production pockets all around the environment.

• Understand the most common circumstances and behaviors that can impact a customer’s non-production licensing health. The customer may be over or under-paying for licenses. For example, the customer may use more products than they purchased and fails to order/True Up.

• Develop systems and process to manage increases and decreases in developer team size since these changes will impact license subscription levels.

Non-production EnvironmentDeployment Considerations

Ensure the customer understands the differentiators between production and non-production.

13

Non-production EnvironmentDeployment Considerations

• Migrating from non-production to production:

- It is common that a tested and finalized non-production system is pointed to the production data and called a production deployment. A finalized environment should be rebuild in a new production environment and connect to the production data.

- Non-production VMs can migrate across hosts as long as the non-production VM stays non-production.

- Server admins should, in a non-production environment, test the VM’s movement, dynamic resource scheduling, load balancing, high availability (failover), and functionality that virtualization can provide. They should do so in non-production to build it correctly and get it working before configuring the same in production.

- As long as everyone working on the hosts, in the full environment that the VMs move within has MSDN subscriptions, then the non-production VM moving across servers remains properly licensed via MSDN.

Moving Non-production Environments to AzureAzure is an Internet-scale computing and services platform hosted in Microsoft data centers. Azure has evolved over the years, and now with the Infrastructure Services (VMs) offered, it makes a lot of sense to leverage Azure for creating development environments and running testing scenarios.

Azure enables users to develop and test applications faster, at reduced cost, and with the flexibility to deploy in the cloud or on-premises, with these customer benefits:

Develop and Test Applications Faster: Rapidly self-provision as many virtual machines as you need for your application development and testing in the cloud without waiting for hardware, procurement, or internal processes. Connect globally to your on-premises network with Azure Virtual Network and confidently scale up, scale out, and generate load to deliver applications faster.

Access the Latest Development Tools in Minutes: Visual Studio 2013 is the best IDE for cloud development and test – and enables powerful scenarios including running Visual Studio in the cloud, plus the ability to manage cloud resources from Visual Studio. MSDN subscribers can use pre-configured Visual Studio 2013 Azure virtual machine images to get up and running in a flash.

Deploy On-premises or in the Cloud: Use Azure to develop and test your application faster, at a reduced cost, and then choose where to deploy them. You can go into production on Azure, or export your virtual machine and go live on-premises or with a hosting provider.

Non-production environments that have been designed to support a specific application will likely need to be modified to be accessible from Azure, adding an additional expense. There is not a one-to-one relationship and correlation among all on-premises products and Azure offerings. One important consideration is the implications to licensing and budget. For example:

• Initial setup costs for software

• Integration with other IT systems

• Additional storage requirements

• Service renewal costs

• Time-line and testing

The benefits provided by Azure will overshadow the majority of these costs in most instances, but it is best to take a holistic view of the customer’s environment and goals when making any recommendations about a move.

14

Non-production EnvironmentDeployment Considerations

ResourcesUpdate to Developer Tools Use Rightsmicrosoft.com/licensing/about-licensing/product-licensing.aspx

Microsoft Azure for Development and Testazure.microsoft.com/en-us/solutions/dev-test/

Developer Tools Engagement Framework for SAM engagementshttps://assets.microsoft.com/en-us/developer_tools_engagement_framework_sam_engagements_deck.pdf

Improving SAM Engagement Accuracy for MSDN, Visual Studio and Dev Test Environmentshttps://assets.microsoft.com/en-us/improving_sam_engagement_accuracy_msdn_visual-studio_test_environment.pptx

SAM Partner Playbook https://assets.microsoft.com/en-us/SAM-Services-Partner-Playbook.zip

Microsoft Cloud Services https://azure.microsoft.com/en-us/services/cloud-services/

Benefits of a Hybrid Cloud microsoft.com/en-us/server-cloud/cloud-os/modern-data-center.aspx#fbid=nG2-xiXCM_H

Microsoft Services microsoft.com/en-us/microsoftservices/default.aspx

ITIL itil-officialsite.com/

SAM SOFTWARE ASSET MANAGEMENT

15

Licensing for non-production environments can be complex. Software licenses often consume a significant part of an organization’s IT budget. If your customer’s software is not licensed correctly—whether they are over-licensed or under-licensed—they can potentially face compliance or budgeting issues. As a Software Asset Management (SAM) partner, your role is to help customers uncover their production environment usage scenarios and to help ensure the customer is not exhausting resources on incorrect developer licensing. Educate the customer on the different developer tools software licensing options that are available in order to help them optimize their spending and manage their IT budget. It is important that you communicate the different types of licensing that are available to an organization, how best to optimize their licensing based on usage, the documentation that is required, and how customers should best organize documentation.

Common Developer Tools Licensing MistakesIt is important to understand the most common circumstances and behaviors that can impact a customer’s licensing health. Identifying these problems during a SAM engagement may result in a licensing gap that the customer will need to resolve with a purchase. However, it is equally important that SAM partners spend equivalent time helping customers identify areas where these mistakes are preventing them from realizing the best possible return on the software investment they have already made. The following tables summarizes typical scenarios for under and over-licensing:

Under-licensing Scenarios

Buy Cheap, Use Expensive

Expired MSDN

MPN Benefit Misuse

Buy Few, Use Many

Unlicensed Outsourcing

Incorrectly Licensed Non-production

Customer uses higher product edition(s) than they purchased and fails to order/True Up

Customer uses more products than they purchased and fails to order/True Up

Customer without active MSDN subscription uses latest version of product

Customer uses outsourced development workforce internally and neither party pays to license those users

MPN partner uses MPN licensing to provide software development services and/or exceeds MPN benefit entitlement cap

Customer uses MSDN software on Development/Test servers without licensing all users reaching those environments

Each of the scenarios above have an opposite equivalent, which represents an opportunity for you to uncover value that the customer is not realizing from their current software investments and are, in fact, over licensed.

Non-production EnvironmentLicensing Considerations

16

Non-production EnvironmentLicensing Considerations

Over-licensing Scenarios

Buy Expensive, Use Cheap

Wasted MSDN

Wasted MPN Benefit

Buy Many, Use Few

Overlicensed Outsourcing

Overlicensed Non-production

Customer purchases Premium and/or Ultimate editions but Administrator fails to assign and users cannot access

Customer uses fewer products than they purchased and fails to deploy or renew down, renews unused software

Customer with an active MSDN subscription does not take advantage of new versions, Office production* and Azure use rights

Customer uses outsourced development workforce internally and both parties pay to license those users due to miscommunication

MPN partner qualifies for MSDN benefits but does not take advantage of them

Customer purchases or renews more MSDN subscriptions than are needed in order to license all users reaching those environments

*Please visit http://aka.ms/msdnbenefitscomparison to confirm if your subscription level includes Office use rights for production.

SAM Partners are uniquely positioned to help customers identify these scenarios where they exist within the organization and provide guidance as to how they can ensure they are getting maximum value from the software they have already purchased. For example, customers might be overpaying for Visual Studios with MSDN whereas they could get by on MSDN Platform, which is much less expensive. The customer may also realize that only 50% of their users may need these licenses.

It can go both ways. Another example could be that a large development team uses one MSDN subscription and the password is saved on the team’s share for use by the whole team. Identifying and quantifying complete and accurate details about the current environment and identifying opportunities for improvement plays a critical role in helping a SAM partner to earn a trusted advisor relationship, and provides substantial benefit for the customer.

Impact of MSDN on Non-production LicensingBecause MSDN Premium Subscriptions includes development and test licenses for Microsoft operating systems, servers, and clients, they are a convenient way to cost-effectively develop applications on the Microsoft platform with a simple licensing model. Licensed per user, MSDN enables management and licensing for all team members in a convenient per head acquisition model. The challenge for many customers is managing the licensing changes as projects move from a non-production environment licensed under MSDN to a production environment where MSDN licensing benefits no longer apply. This section covers the main implications of MSDN from a licensing perspective.

About the MSDN High Water MarkThroughout the development lifecycle, there will be periods where the number of developers coding and other users accessing the non-production environment, such as IT managers and testers, will increase and decrease. The point at which usage of the non-production environment is the highest is called the high water mark. Because it is not easy to identify the high water mark, managing MSDN licensing and usage is challenging. Any user accessing the non-production

17

Non-production EnvironmentLicensing Considerations

environment will need to be licensed.

Customer purchases MSDN Subscriptions on EA

Customer’s development team increases in size

Customer’s development team decreases in size,Admin deletes subscriptions

MSDN Administrator assigns purchasedsubscriptions to users

MSDN Administrator assigns additionalsubscriptions to new users

Customer purchases over-assigned subscriptions atTrue Up based on high water mark of usage

To determine what the high water mark is for a customer since their last True-up or license reconciliation, look at inventory data and MSDN reports provided by the customer and conduct interviews with IT Professionals and project managers to determine the peak usage. If you are working on a SAM engagement with a customer jointly with Microsoft, you can obtain the MSDN High Water Mark Report from Microsoft. This report is available to the MSDN Administrator through the Volume Licensing Service Center (VLSC) and contains complete MSDN subscription assignment history for the life of a customer agreement. The Microsoft Developer Tools Solution Specialist (SSP) assigned to the account can also help by providing historical profiling and background information for the account that you will want to incorporate into your review.

To reiterate, the high water mark report should be treated as one source of input and one part of a larger discussion, not a single source of truth. User data should be reviewed carefully to rule out duplicative data.

Visual Studio and Visual Studio with MSDN ProductsWhile there are developer tools products such as Microsoft Team Foundation Server (TFS) that are sold using a Server/CAL model, Visual Studio and MSDN subscriptions are licensed per user. Everyone who touches the non-production environment needs an MSDN subscription. Some of the common roles that will need MSDN subscription licenses include:

• Software Developers who use Microsoft tools or platforms.

• Testers who are responsible for using and testing software for the purpose of locating and eliminating bugs in the product and who review an application to help determine if it meets the User Acceptance Testing (UAT) criteria for release.

• Database Administrators (DBA) who are responsible for the installation, configuration, upgrading, administration,

18

Non-production EnvironmentLicensing Considerations

monitoring, maintenance, and security of databases in an organization.

• Project Managers who are responsible for supervising the work of staff and communicating progress to top management and department heads.

• Additional IT Professionals such as any Network Administrators who maintain hardware and software systems, or System Engineers who perform installation or system resets for Windows servers, in a non-production environment.

• Software Developers who use tools or platforms from vendors other than Microsoft.

Make sure you are familiar with the different price points and product levels when reviewing the Microsoft Licensing Statement. Licensing issues related to Visual Studio are typically associated with users running an edition of the Visual Studio product other than the one for which they have been licensed by their company’s MSDN Administrator, or with no license at all. Every user accessing a non-production environment running Microsoft software must have an appropriate MSDN subscription. If they do not, the environment must be licensed for production.

Professional 2013 Professional 2013 Upgrade

Operating Systems 2012

Professional 2013 with MSDN

Premium 2013 with MSDN

Ultimate 2013 with MSDN

Test Professional 2013 with MSDN

Platforms

MSDN Subscriptions Stand-alone tool

Per User Licensing Model

19

Non-production EnvironmentLicensing Considerations

New MSDN Platforms Licensing Option The new MSDN Platforms SKU provides developers using tools or platforms that are not from Microsoft and those in non-developer roles access to non-production environments at a reduced price. MSDN Platforms does not include Visual Studio, but it does provide development and test rights for all servers, including SharePoint and Exchange. This means that the customer’s entire team can be licensed, with access to all the Microsoft software your customer will need to use in testing environments such as SQL, Windows Server, SharePoint, Biz Talk, Windows 8 for Desktop, etc. This also means that MSDN Platforms is a great fit for licensing users who are accessing non-production software running in any type of lab environment, even those not related to developing custom applications.

For example, if a developer writes code, checks it into Microsoft Team Foundation Server, performs load-testing and bug tracking, then they are using Visual Studio and MSDN Platforms in not appropriate for them. If, however, the developer needs a new environment, they might ask their IT network administrator to install a new Windows Server and install SQL. The network administrator will not use Visual Studio but they need to be licensed for the Windows Server and SQL they just interacted with. Their solution is then MSDN Platforms.

MSDN Subscription ManagementFor customers with Enterprise and/or Select Agreements, MSDN subscriptions are managed in the Microsoft Volume Licensing Service Center (VLSC) web portal by a designated user in the customer organization called the MSDN Administrator. The administrator is responsible for assigning MSDN subscriptions to individual users within the organization and must understand key issues related to MSDN licensing and usage.

Using Visual Studio and/or MSDN software incurs a purchase obligation and includes• Installing• Configuring• Running• Viewing• Otherwise interacting

with

Assigning MSDN and/or Visual Studio with MSDN subscription licenses to users is a right customers do not have without making a purchase and indicates strong evidence of software usage

Reconciling software usage with corresponding purchases must be done annually for EA at True Up and monthly for Select

Understanding, monitoring and accurately communicating their company’s usage when assigning subscription licenses and/or distributing Visual Studio and/or MSDN software to users is the responsibility of the MSDN Administrator

However, the customer is responsible for tracking and communicating this activity to appropriate finance or procurement personnel within their organization to ensure that the incremental licenses are purchased. Even when subscription assignments decrease over time, the customer is obligated to track and report their peak of assignments, commonly referred to as the “high water mark of usage,” for each subscription type.

20

Non-production EnvironmentLicensing Considerations

Key QuestionsAsk the customer for help illustrating the following roles and MSDN subscriptions:

• Who accesses or interacts with the non-production systems?

- The customer can provide information on who works in this space.

- Their MSDN report will help by showing the customer’s developer subscriptions and who is assigned to them.

• In which capacity are the various users interacting with the non-production systems?

- Who are the IT managers who support, deploy, and retire the systems?

- Who are the actual developers, testers, database administrators, IT pros, project managers, etc.?

Licensing the Whole Team• Mapping users to the system they access will help clarify which licensing they need.

• Educate customers that all users accessing non-production must be licensed to do so even if they professional testers, software demonstrators, or systems administrators who are not coding.

• Promote awareness of MSDN platforms subscription aimed at non-developer and cross-platform developer roles.

Examples of How a Customer in a Non-production Environment can use Wrong Licenses through MSDN

• Demonstrating software “in production” in a non-production environment.

• Installing a server with production capabilities using the non-production environment.

Use of Legacy ProductsSome customers prefer to use old products. When an environment scan discovers an unlicensed legacy product, it’s not always evident what current product the customer needs to purchase in order to obtain use rights for the old product. Refer to the Legacy Product Mapping document in the Engagement Framework (see Resources at the end of this section) to identify the current product offering that maps to the legacy product the customer wants to continue using.

Microsoft Partner Network License GrantsMicrosoft Partner Network Partners (MPN) with a Silver or Gold Competency are granted licenses to Visual Studio Professional with MSDN. Application Lifecycle Management competency partners are granted incremental licenses to Visual Studio Ultimate with MSDN. Partner license grants have limited use rights. Be sure that you understand the rules for determining MPN entitlements. Examples of use right limitations:

• You cannot use Partner License Grants for external, revenue generating purposes. If a customer needs help with software development you must purchase licensing to do so. However, the MPN License Grants can be used to service Microsoft related software development needs.

• You only have a 12-month grace period to be on an older version, otherwise you always have to be using the current version of the product you’re granted partner licenses for.

You can obtain MPN entitlement report for MSDN through your SAM EM. For more information visit Microsoft’s Product Usage Guide as referenced in the Resources section.

21

Non-production EnvironmentLicensing Considerations

Looking ahead Once all of the inventory data, supplemental data, licensing information, and more has been explained to the customer, provide them with their “as is” picture and what their roadmap to an optimized state would be. Explain to them ways that they can improve their processes to help ensure they continue to deploy and license their environment as efficiently as possible going forward.

Below is a Customer Checklist that you can share with your customer as guidance for their own efforts in maintaining their environment and ensuring that proper licensing is in place.

Customer Check List ✔ Review the Documents. Be sure to read the PUR, MSDN Administrators Guide, and Visual Studio and MSDN

Licensing Whitepaper.

✔ Develop Your Schedule. Review your Microsoft Volume Licensing terms so you can be prepared to provide data inputs for license assignment changes, monthly select or open orders, incremental license purchases, and annual enterprise agreement true-ups.

✔ Define Your Process. A clear process for adding, removing, and managing user changes over time is important.

✔ Build Your Team. Identify internal contacts and external partners who can help you keep track of environment changes and users who “interact with MSDN software.”

✔ Automate Usage Inventory. Automated tools like Microsoft System Center or MAP (Microsoft Assessment and Planning Tool Kit) can help you identify your non-production environment—desktops, servers, and users.

✔ Automate User Assignment Tracking. The Volume Licensing Service Center is a good place to keep track of your “high water mark” of MSDN assignments.

✔ Get Help. Contact your SAM Partner or MSDN Administration Services representative for help

22

Non-production EnvironmentLicensing Considerations

ResourcesVisual Studio Subscription Details (formally MSDN Subscription Details)https://www.visualstudio.com/products/subscriber-benefits-vs

MPN License Grants – Product Use Guidemspartner.microsoft.com/en/us/pages/membership/internal-use-software.aspx#comp

Developer Tools Engagement Framework for SAM engagementshttps://assets.microsoft.com/en-us/developer_tools_engagement_framework_sam_engagements_deck.pdf

Improving SAM Engagement Accuracy for MSDN, Visual Studio and Dev Test Environmentshttps://assets.microsoft.com/en-us/improving_sam_engagement_accuracy_msdn_visual-studio_test_environment.pptx

Visual Studio 2013 and MSDN Licensing Whitepaper aka.ms/vswhitepaper

Visual Studio (Formerly MSDN) Subscriptions Administration Guide aka.ms/vladmin

Microsoft Product Terms (formerly Product Use Rights) aka.ms/pur

MSDN Platforms Product Information aka.ms/platforms

Enterprise Agreement (EA) True Up Guide aka.ms/eatrueupguide

SAM SOFTWARE ASSET MANAGEMENT

23

Once you’ve helped the customer uncover their deployment and licensing footprint, the next step will be to help the customer develop guidelines and policies to ensure ongoing proper software asset management. Having a plan in place is essential for ensuring that licensing is always up to date and to avoid unpleasant budget obligations. Creating standard practices can help the customer reduce waste, avoid unnecessary costs and business risks, and streamline the organization. A SAM plan can help empower customers to improve the health of their developer tool asset management now and in the future.

SAM Policies and Procedures for Non-production Environments MSDN Administrator in Place: This is the person who has access to the MSDN portal. They can see how all subscriptions have been allocated and the names of who has activated them. The MSDN administrator can reassign the subscriptions as appropriate. Occasionally, the procurement person who signed the contract is the company’s admin, but this person is traditionally not actively working with developers. It’s important to encourage the customer to have an administrator in place who is responsible for actively managing the MSDN subscriptions.

Clearly Designate Non-production and Production Environments: Associating servers to development, testing, UAT or production environments simplifies the identification of servers. This enables operations to provide reports that will show which server is assigned to each property.

• Isolate non-production in a dedicated, separate domain.

• Manage non-production and production systems in separate active directory organization unit (OU) for easy identification/mapping.

• Isolate non-production systems to virtual OSEs on dedicated non-production hosts.

• Standard, disciplined naming conventions.

Apply Naming Conventions: Naming conventions are important. Ask your customer what naming conventions they have in place. Look to server names to help identify their function. Recommend customer implementation of a consistent naming convention as a best practice. Example of how to name a server: IRedDSQL001

• I (first letter of company name)

• Red (domain)

• D (dev. server)

• SQL001 (standard)

Outsourced Development Workforce: Ensure that development workforces’ licenses (Visual Studio and MSDN subscriptions, Office, and other desktop applications, CALs, etc.) are well documented. If developers are providing their own Visual Studio and/or MSDN subscriptions during the term of the contract, ensure those licenses are documented at the start of the contract. Also, ensure that development workforces’ permissions are configured to only allow access to the

Non-production EnvironmentSAM Policies

24

Non-production EnvironmentSAM Policies

systems required for their roles to avoid security, licensing, etc. risks.

High Water Mark and Usage: Development environments and staff are highly dynamic. Ensure that uneven usage patterns are tracked closely in order to understand the high water mark of usage and ensure that all development systems and users are right licensed at all times.

Regularly Scheduled Software Inventories: It is advisable that customers perform frequent software inventories to keep their non-production subscriptions up to date. Performing frequent self-audits include reviewing if employees are still with the company and if they have the correct licensing subscriptions.

Moving from Non-production to Production: If a non-production systems is planned to be based on specific business needs, ensure that the appropriate production licensing is purchased in advance, as the MSDN licensing in the non-production environment no longer licenses the deployment once moved to production.

Ongoing Employee Training: With MSDN subscriptions, employees can download any MS software they want. It is easy for an employee to proceed without the right licensing. Educating employees on MSDN and licensing management is important.

Maintenance: Ensure the customer has dedicated license managers and processes in place that maintain compliance.

Roles and ResponsibilitiesDefine and develop processes, procedures, and policies based upon a clear understanding of roles and responsibilities. Document responsibilities explicitly; avoid making assumptions. This is extremely important in outsourcing scenarios.

You may need to bring in additional roles, such as finance managers and IT architects, to help ensure that everyone understands the unique challenges of a non-production environment, and that they are equally motivated to ensure the necessary processes are in place to optimize use and reduce costs.

Try to make sure the CIO and other relevant management roles are stakeholders and share commitment to the SAM process. Ideally, the CIO would drive this initiative from the top down to help ensure that all parties involved with non-production and provisioning are aligned in their understanding and overall organizational goals.

Best Practices for the IT Department• Track licensing subscription allocations and needs per project.

• Ensure licenses on projects that have moved from non-production to production are managed accordingly. Essentially, “managing licenses accordingly” when moving from non-production to production is actually buying licenses for those deployments, since they had previously been licensed via MSDN and are no longer able to be.

Managing Unneeded Server Hardware Help the customer develop a clear set of guidelines around what to do with a decommissioned server, such as canceling unnecessary licensing, recycling it, or repurposing it for a new project. It is important to have a rigorous program in place for removing obsolete servers at the end of their lifecycle. Obsolete servers consume electricity without doing any

Define and develop processes, procedures, and policies based upon a clear understanding of roles and responsibilities.

25

Non-production EnvironmentSAM Policies

computing, and unutilized licensing is taxing the IT budget.

SAM Across the OrganizationA discussion about how new SAM policies will be implemented is important. Management should become involved as stakeholders in the implementation and follow-through of SAM processes to ensure that these policies become part of the natural cycle of business for the organization.

Customers should define their internal SAM processes, procedures, and policies, including clear expectations of roles and responsibilities. Policies should include the desired attitude and behavior from an overall organizational perspective, to help ensure all controls are in place and communicated clearly for all involved in the process.

• Realize that SAM must span people, processes, and tools in order to sustainably manage licenses.

• Look at the Microsoft Operations Framework and follow it consistently as a standard best practice.

• Understand and implement a process framework within the organization.

• Incorporate SAM results as a part of governance reports.

• Understand what software tags are and how they are becoming increasingly important. ISO/IEC 19770-2 outlines the parameters for tagging software to optimize its identification and management. Governments are starting to add a requirement for software tags in procurement requisitions, and new Microsoft products include software tags.

• Take steps to ensure all outside teams, such as vendors and contractors, understand the organization’s SAM policies and procedures.

SAM Standards and FrameworksInternational Organization for Standardization (ISO)The comprehensive international standard for software asset management aligned to IT service management is ISO/IEC 19770-1:2012 SAM Processes. This vendor-independent standard can benefit your customers in many ways and is supported by much of the IT industry, including Microsoft.

SAM Optimization Model (SOM)The SAM Optimization Model is a framework developed by Microsoft that is aligned with Microsoft Infrastructure Optimization (IO). SOM enables partners and customers to evaluate SAM effectively and objectively, and manage the life cycle of software assets with vision, policies, procedures, and tools. SOM provides an established set of criteria to help you make consistent SAM assessments and recommendations. Using this model, your organization can conduct

26

Non-production EnvironmentSAM Policies

a SAM evaluation to determine how effectively your customer is managing software assets. You can use the results of the evaluation to offer guidance and create a road map to visualize the benefits and savings at each stage of SAM optimization.

SAM Optimization Model – Maturity Levels

BASIC STANDARDIZED RATIONALIZED DYNAMICSAM Throughout Organization

Project Manager assigned but SAM roles & responsibilities not defined

Direct SAM responsibility is identified throughout organization

Each functional group actively manages SAM

SAM responsibilities defined in job descriptions across organization

SAM Improvement Plan

No SAM development or communication plan

SAM plan is defined and approved

SAM Improvement is demonstrated

SAM goals part of executive scorecard; reviewed regularly

Hardware & Software Inventory

No centralized inventory or < 68% assets in central inventory

> 68% - 95% of assets in inventory

> 95% - 98% of assets in Inventory

> 99% of assets in inventory

Accuracy of Inventory Manual inventory; no discovery tools

Inventory sources reconciled annually

Inventory sources reconciled quarterly

Dynamic discovery tools provide near real-time deployment details

License Entitlement Records

Procurement manages contracts; not accessed by IT managers

Complete entitlement records exist across organization

Entitlement records reconciled with vendor records

SAM entitlement system interfaces with vendor entitlement to track usage

Periodic Evaluation IT operations managed on ad-hoc basis

Annual sign-off on SAM reports

Quarterly sign-off on SAM reports

System reconciliations and ITAM report available on demand

SAM Operations Mgmt & Interfaces

SAM not considered part of M&A risk plan and company integration

Operations manages separate asset inventories

Operations manages associated asset inventory

All business units follow the same strategy, process & technology for SAM

Acquisition Process Assets purchased on a per project basis; without a review of current availability

Software purchases use approved vendors

Software purchases based on deployment/entitlement reconciliation

All purchases are made using a predefined asset catalog; based on metered usage

Deployment Process Assets deployed by end-users in distributed locations; no centralized IT

Only approved software is deployed

Software deployment reports are accessible to stakeholders

Software is dynamically available to users on demand

Retirement Process Software is retired with hardware and is not harvested or reassigned

Unused software is harvested (where the license allows) and tracked within a centrally controlled inventory

Centrally controlled inventory of harvested licenses is maintained & available for reuse. Deployment & license records are updated

Automated process w/ centralized control & tracking of all installed software, harvest options, internal reassignment and disposal

27

Non-production EnvironmentSAM Policies

The SAM Optimization Model framework serves as the foundation and guidance for preparing to implement an effective SAM program that supports alignment with ISO standards. The ISO standard outlines the requirements and certifications recommended for a comprehensive SAM program. Essentially, Microsoft SOM focuses more on how to implement an effective SAM program whereas the ISO SAM standard focuses on what to implement for comprehensive SAM. Adopting both frameworks will help ensure that customers accurately and strategically implement and manage a successful ongoing SAM practice.

SAM Optimization Model & ISO SAM

MS SOM Dynamic ISO SAM Tier 4

MS SOM Rationalized

ISO SAM Tier 3

MS SOM Standardized

ISO SAM Tier 2

MS SOM Basic

ISO SAM Tier 1

3. Long-term focus

2. Subsequent focus

1. Initial focus

Largely Equivalent

Largely Equivalent

28

Non-production EnvironmentSAM Policies

Resources International Organization for Standardization (ISO) SAM StandardsISO/IEC 19770-5:2015 - Information technology — Software asset management — Part 5: Overview and vocabularyISO/IEC 19770-2:2015 - Information technology — Software asset management — Part 2: Software identification tagISO/IEC 19770-1:2012 - Information technology — Software asset management — Part 1: Processes and tiered assessment of conformance

SAM Optimization Modelhttps://www.microsoft.com/en-us/sam/baseline.aspx

BSA SAM Advantage Training Course Aligned to the ISO/IEC 19770-1 Standardbsa.org/anti-piracy/bsa-sam-solutions