SAM for Non-production Environments Presenter Name

Non-production environments Today, more and more companies develop their own custom software. As the number of employees engaged in software development increase so does the complexity of managing licensing within this environment.

Who benefits from a non-production SAM engagement? A non-production SAM engagement is not just for companies developing custom software. The special considerations associated with tracking and managing software that is not licensed for production use mean that this engagement could benefit all businesses running any type of non-production lab environment.

Complex, dynamic, ever-changing 2/9/2018 Complex, dynamic, ever-changing Modern non-production environments: characterized by change It can be difficult for an organization to: Understand how non-production systems are deployed, developed and tested upon, decommissioned, and rebuilt Get a clear picture of the organization’s software footprint Understand the licensing subscriptions available Understand who needs to be licensed Key points: Non-production environment optimization and licensing are complex challenges that many customers need to work through. Increasing number of software development projects, number of people involved and software developments moving between developing/testing/User Acceptance Testing/Staging only adds to the complexity of managing non-production environments. With this arsenal of data and people involvement we can help identify new ways to optimize your licensing investment for more productivity or reduce over-licensing for cost reductions. SAM is a set of proven processes and procedures for managing and optimizing your organization's non-production environments. SAM supports your licensing strategy by providing key insights into the best approach going forward to gain maximum utilization and efficiencies from your non-production environment.

Non-production SAM engagement Understand licensing options Get a clear pictures of your organization’s software footprint Increase efficiencies Optimally manage your environment A customer focused SAM engagement will help you: Key Points: Transition to more detailed discussion of a Non-production SAM engagement The Non-production SAM program has been designed around specific customer feedback. This program is designed to help customers improve your understanding of your software environment and to use this information to help ensure your production and non-production environments are optimally set up. Let’s spend a few minutes now going into more detail about the Non-production SAM engagement and how it can help you attain your long-term business objectives. We will Create an inventory of your software estate Review your licensing Discuss SAM policies, procedures and best practices A Non-production SAM engagement helps you to receive the most value from your licensing investments.

Non-production SAM engagement benefits 2/9/2018 Non-production SAM engagement benefits Gain a better understanding of how developer tool licensing works Receive value from your licensing investments Reduce costs through operational efficiencies Incorporate standardization across management of company assets Improve internal licensing communication Establish a solid foundation for achieving future organizational objectives Key notes: There are significant benefits to a SAM engagement. You will learn how to: Gain a better understanding of how developer tool licensing works Receive value from your licensing investments Reduce costs through operational efficiencies Incorporate standardization across management of company assets Improve internal licensing communication Establish a solid foundation for achieving future organizational objectives

Non-production environments SAM engagement: Step 1 2/9/2018 Non-production environments SAM engagement: Step 1 Organizational Profile Licensing Considerations Development, Testing, User Acceptance Testing, Staging People involvement Infrastructure Basic information about the organization Key notes: The first step is to learn more about your organization and understand the landscape of your non-production environment. Organizational Profile: Who is working in your non-production environment? How do they interact with your software products in development, testing User Acceptance Testing, Staging? How does your company define non-production vs. production? People Environment Gather preliminary information about the existing environment, future goals, and security concerns

Non-production environments SAM engagement: Step 2 2/9/2018 Non-production environments SAM engagement: Step 2 After establishing an organization’s goals and objectives, the next step is to complete a software review The report will match installations with licenses Inventory deployed software build a detailed report on your current state Key notes: We will conduct a software review to develop a clear understanding of your environment. One important goal of this step is to reveal potential value for you by helping you save costs on unnecessary developer licensing in the non-production environment. We will also use this information to provide you with guidance on the best way to manage your software licensing going forward.

Non-production environments SAM engagement: Step 3 2/9/2018 Non-production environments SAM engagement: Step 3 We will review with you: Non-production vs. production: Discuss differentiators between non- production and production environments and updates to product use rights (PUR). Common licensing mistakes: Review common over-licensing and under- licensing mistakes. Licensing options: Walk through challenges of managing licensing and licensing options available. Best Practices: Review best practices for navigating the non-production environments, managing software licensing subscriptions and consolidation of non- production environments. Policies and Guidelines: Based on our findings we will have a good understanding of how we can help your organization create policies for managing your non-production environments going forward. Report on key findings and guidance Key notes: The second step is to review: Non-production vs. production: Discuss differentiators between non-production and production environments and updates to product use rights (PUR). Common licensing mistakes: Review common over-licensing and under-licensing mistakes. Licensing options: Walk through challenges of managing licensing and licensing options available. Best Practices: Review best practices for navigating the non-production environments, managing software licensing subscriptions and consolidation of non-production environments. Policies and Guidelines: At the end of our engagement we will have a good understanding of how we can help your organization create policies for managing your non-production environments going forward.

Typical interview 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? 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? 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? Which types of roles manage testing? Who is overseeing moving software projects through the development, testing, User Acceptance Testing, staging to production cycle? How do you mange decommissioned servers? Key Points: As part of the discovery process we will talk with you about your organization to help clarify critical details about software development and testing. We will also develop a profile of users to understand who is accessing the non-production environment. This slide illustrates the types of questions that we will cover in this phase of the engagement.

Under-licensing mistakes that are commonly made Buy Cheap, Use Expensive Customer uses higher product edition(s) than they purchased and fails to order/True Up Buy Few, Use Many Customer uses more products than they purchased and fails to order/True Up Expired MSDN Customer without active MSDN subscription uses latest version of product Unlicensed Outsourcing Customer uses outsourced development workforce internally and neither party pays to license those users Key notes: Here are some interesting examples of common licensing mistakes, which can have a significant impact on your organization’s IT budget. A SAM engagement will help identifying any gaps and may result in realization of over-spending or under-spending on licensing. MPN Benefit Misuse MPN partner uses MPN licensing to provide software development services and/or exceeds MPN benefit entitlement cap Incorrectly Licensed Non-production Customer uses MSDN software on Development/Test servers without licensing all users reaching those environments

Over-licensing mistakes that are commonly made Buy Expensive, Use Cheap Customer purchases Premium and/or Ultimate editions but Administrator fails to assign and users cannot access Buy Many, Use Few Customer uses fewer products than they purchased and fails to deploy or renew down, renews unused software Wasted MSDN Customer with an active MSDN subscription does not take advantage of new version, Office production* and Azure use rights Overlicensed Outsourcing Customer uses outsourced development workforce internally and both parties pay to license those users due to miscommunication Key notes: Each of the under-licensing examples have an opposite equivalent for over-licensing, which represents an opportunity for us to help you to uncover value and cost savings that you might not be aware of exists. For example, you might be overpaying for Visual Studios with MSDN whereas they could get by on MSDN Platform, which is much less expensive. Our goal is to help you identify areas where these mistakes are preventing you from realizing the best possible return on the software investment you have already made. *Please visit http://aka.ms/msdnbenefitscomparison to confirm if your subscription level includes Office use rights for production. Wasted MPN Benefit MPN partner qualifies for MSDN benefits but does not take advantage of them Overlicensed Non-production Customer purchases or renews more MSDN subscriptions than are needed in order to license all users reaching those environments

Licensing options for non-production environments Visual Studio and Visual Studio with MSDN Products MSDN subscriptions Stand-alone tool Ultimate 2013 With MSDN Microsoft Premium 2013 With MSDN Microsoft Professional 2013 Microsoft Professional 2013 Upgrade Microsoft Test Professional 2013 With MSDN Microsoft Professional 2013 With MSDN Microsoft Key notes: Available Licensing options for non-production environments are complex. Software licenses often consume a significant part of an organization’s IT budget. Over-licensing or under-licensing can result in budgeting issues. The purpose of a SAM engagement is to help you better understand your non-production environment and to help ensure you are not exhausting resources on incorrect developer licensing. During the engagement we will review which developer tools software licensing is available in order to help you optimize spending on licensing subscriptions, who in your organization needs to be licensed and how to best organize the documentation. As an example: While 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. Platforms Microsoft Operating Systems 2012 Microsoft msdn msdn

MSDN Platforms Software, services, support, training: MSDN Platforms is a licensing option for non-developers that provides your organization cost effective and convenient access to wide range of resources. Lowers software acquisition costs Simplifies licensing Empowers your teams Increases agility Key Points: MSDN Platforms is a new subscription that helps provide a cost-effective way to license Microsoft software for individuals involved in the development and test process who do not require the full suite of Visual Studio development tools. 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. 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.

Topics covered by SAM Policies and processes MSDN Administrator in place Regularly scheduled software inventories Ongoing employee training Maintenance and processes Defining processes, roles and responsibilities Training Employees, vendors, and others accessing organizational resources Post production guidelines for decommissioned servers Example policy: 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. Key Points: A large part of the Non-production Environments SAM Engagement is to review the SAM policies and procedures that will help you to proactively work to avoid the risks associated with licensing in non-production environments. It is critical that an organization’s SAM plan includes protocols governing non-production and how it’s managed. Some of the topics we cover include best practices around the topics shown, and development of related policies that are designed specifically to address your organization’s priorities and goals.

The path forward Project scoping & technical meeting Inventory 2/9/2018 The path forward Now Assess How optimal is your environment? Production Non-production Test Dev MSDN Discuss program & next steps Organizational Objectives Understand the organization’s culture, and business goals and objectives they hope to achieve Inventory Collect data on software deployments and gather additional information on the IT environment Review & Validate Detect licensing needs and define policies for non-production environment. Discover Plan Project scoping & technical meeting Are you taking full advantage of cost savings? Review Are there any licensing issues to discuss? Key Points: 3 minutes We will guide you through a well-defined process to help you develop a plan and manage your non-production environments based upon your future goals and a clear understanding of your current state. REVIEW THESE SPEAKER NOTES We will schedule a scoping meeting with you to have a deeper-level technical discussion to understand your environment and your unique needs. The result will be a full project plan with deliverables and deadlines. During the discovery phase, you’ll work with us to inventory and collect data on Microsoft software in your environment. We’ll also help you get an accurate view of all of your license entitlements. We’ll discuss your organizational objectives, and develop a profile of your current state. In the assessment phase, we develop recommendations based upon considerations of your existing infrastructure, people involvement, and how your organization is positioned relative to licensing . We will schedule a review meeting with you to deliver the reports and present the findings. We’ll provide you with guidance about opportunities for you to better protect your infrastructure, with a specific focus on recommendations around SAM policies and procedures to reduce cyber risk. We’ll also cover ways to best manage IT assets to help reduce waste, avoid unnecessary costs, and streamline the entire organization. Now it’s time to see what questions there are and to discuss next steps after today.

Next steps and Q&A Next Steps Questions & Answers 2/9/2018 Next steps and Q&A Next Steps Select project scoping meeting date Review and approve project plan Get started Questions & Answers What’s on your mind?