11/19/2017 Improving SAM Engagement Accuracy for MSDN, Visual Studio, and Dev/Test Environments Carlos Zimmermann – WW Sales Director John Griffin - US.

11/19/2017 Improving SAM Engagement Accuracy for MSDN, Visual Studio, and Dev/Test Environments Carlos Zimmermann – WW Sales Director John Griffin - US Developer Tools AP Lead © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Developer Tools in SAM engagements
11/19/2017 Developer Tools in SAM engagements © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Engagement objectives
11/19/2017 Engagement objectives When approaching the Developer Tools footprint during a SAM engagement, we have the following objectives: Ensure the customer has a solid understanding of Developer Tools licensing model Collaborate with the customer to accurately assess their Developer Tools licensing position Empower the customer to improve the health of their Dev Tools asset management system in the future © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Engagement challenges
11/19/2017 Engagement challenges Over the course of typical engagements involving Developer Tools, partners report challenges during these phases: Preparation Onsite Follow up Know the Common Licensing Mistakes License Entitlement Review MSDN Subscription Data Review Preliminary Meetings/Calls User Polling Customer Briefing Personnel Interviews Review of Personnel Records Domain/Machine Identification Environment Scanning Scan Data Review License Reconciliation ELP Generation © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Preparation - Know the most common licensing mistakes
11/19/2017 Preparation - Know the most common licensing mistakes Customer practices impacting their licensing health Challenge Review the Common Licensing Mistakes outlined in the Engagement Framework and watch for them in your engagements Solution To anticipate where customers will need assistance getting right licensed, we need to be familiar with the scenarios where problems most commonly occur © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Preparation - License entitlement review
11/19/2017 Preparation - License entitlement review MSDN subscription entitlements obtained via MPN benefits Challenge Understand rules for determining MPN entitlements Obtain MPN entitlement report for MSDN through your SAM EM (available in December) Solution If the customer is also a Microsoft Partner, it’s difficult to assess how many MSDN subscriptions they are entitled to through their MPN benefit © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Preparation - MSDN subscription data review
11/19/2017 Preparation - MSDN subscription data review Understanding how to license non-Developer user roles Challenge Educate customers that all users accessing Dev & Test must be licensed to do so. Promote awareness of MSDN Platforms subscription aimed at non-Developer and cross-platform Developer roles. Solution What is the best product offering for non-Developers and cross-platform Developers accessing Dev & Test environments? Customers sometimes report that they don’t know they are expected to license those users at all © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Licensing the whole team
MGXFY13 11/19/2017 Licensing the whole team Microsoft Developers Other Dev Team Roles Testers DBAs Project Managers IT Pros Non-MS Developers MSDN Platforms New SKU aimed at all non-dev users (and non-MS devs) accessing Dev/Test environments Provides Dev/Test use rights for all servers including SharePoint and Exchange © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Preparation - MSDN subscription data review
11/19/2017 Preparation - MSDN subscription data review Who has been assigned MSDN subscriptions and when? Challenge Obtain MSDN High Water Mark Report from your SAM EM Shows historical assignments vs. entitlements Shows user assignments by subscription level Solution It’s hard to tell who is using MSDN software It’s hard to tell if the customer’s current state of subscription assignment is also their high water mark © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Onsite - Customer briefing
11/19/2017 Onsite - Customer briefing Setting the stage for a smooth engagement experience Challenge Read and understand the Visual Studio and MSDN Licensing White Paper – a one stop shop for depth guidance on Developer Tools licensing questions Solution We need to better educate customers, manage their expectations, and head off their future objections We want to make our customer briefings more interactive so the customer is part of the process © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Onsite - Customer briefing
11/19/2017 Onsite - Customer briefing Setting the stage for a smooth engagement experience Challenge Use the Customer Briefing Deck from the Engagement Framework to structure the Developer Tools portion of your onsite kickoff with appropriate stakeholders Customer friendly highlights of key issues from Licensing White Paper in presentation format Solution Read and understand the Visual Studio and MSDN Licensing White Paper – a one stop shop for depth guidance on Developer Tools licensing questions Solution We need to better educate customers, manage their expectations, and head off their future objections We want to make our customer briefings more interactive so the customer is part of the process © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Onsite - Domain/machine identification
11/19/2017 Onsite - Domain/machine identification Determining what is Dev and Test Challenge Refer to the formal definition materials and litmus test available in the Engagement Framework Solution We need a clear definition of what constitutes Dev and Test environment vs. Production © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Onsite - Personnel interviews
11/19/2017 Onsite - Personnel interviews Are you asking the right questions? Challenge At a minimum, use the set of questions provided in the Engagement Framework documentation Solution What is the minimum set of questions every partner should ask a customer regarding their Developer Tools environment? © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Follow up - License reconciliation
11/19/2017 Follow up - License reconciliation Some customers like to use old products and that’s ok Challenge Refer to the Legacy Product Mapping document in the Engagement Framework to identify the current product offering that maps to the legacy product the customer wants to continue using Solution When an environment scan discovers an unlicensed legacy product, we don’t always know what current product the customer needs to purchase in order to obtain use rights for the old product © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Engagement Framework assets
11/19/2017 Engagement Framework assets Guidance and tools for you and your customers Asset Name To Partner Through Partner Engagement Guide ● Engagement Framework Deck Training Videos Customer Briefing Visual Studio and MSDN Licensing White Paper MSDN Subscription Administration Guide Legacy Product Mapping Microsoft Product Use Rights MSDN Products by Benefit Level MSDN Subscription Reporting © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Going further Defining Dev and Test
11/19/2017 Going further Defining Dev and Test © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 Per the Product Use Rights document, MSDN software may not be used in a Production environment. To understand what the customer may fairly claim is a Dev/Test environment, you must first rule it out as a Production environment. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Definition of Production Environment:
11/19/2017 Definition of Production Environment: “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 of that application or Feedback. 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” Source: Visual Studio 2013 and MSDN Licensing White Paper – November 2013 (pg 12) © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 If you are unsure whether a physical server or operating system environment should be considered Production, apply the following test: Can you take this environment, and any data that it is consuming, offline permanently without impacting end users? If the answer is “no”, you should treat the machine in question as Production. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Going further Personnel interviews
11/19/2017 Going further Personnel interviews © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Questions for IT Pros and other key personnel
11/19/2017 Questions for IT Pros and other key personnel 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, DBAs and non-MS developers access dev and test 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? Who does the testing? Do you have a staging environment? © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Going further Beyond the gap: Uncovering value for our customers
11/19/2017 Going further Beyond the gap: Uncovering value for our customers © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Most common Dev Tools licensing mistakes
MGXFY13 11/19/2017 Most common Dev Tools licensing mistakes 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 w/o active MSDN subscription uses latest version of product Unlicensed Outsourcing Customer uses outsourced development workforce internally and neither party pays to license those users Common licensing mistakes that can lead to a licensing gap 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 Dev/Test servers without licensing all users reaching those environments © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Most common Dev Tools licensing mistakes
MGXFY13 11/19/2017 Most common Dev Tools licensing mistakes 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 w active MSDN subscription does not take advantage of new version rights Overlicensed Outsourcing Customer uses outsourced development workforce internally and both parties pay to license those users due to miscommunication Common licensing mistakes that can represent unrealized value that partners should be helping customers to uncover 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 © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Going further MSDN subscriptions
11/19/2017 Going further MSDN subscriptions © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Purchasing MSDN subscriptions
11/19/2017 Purchasing MSDN subscriptions Administrators 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 © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Managing MSDN subscriptions
Customer purchases MSDN subscriptions on EA MSDN Administrator assigns purchased subscriptions to users Customer’s dev team increases in size MSDN Administrator assigns additional subscriptions to new users Customer’s dev team decreases in size, Admin deletes subscriptions Customer purchases over-assigned subscriptions at True Up based on high water mark of usage

MSDN High Water Mark Report example
MGXFY13 11/19/2017 MSDN High Water Mark Report example © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

MSDN High Water Mark Reports
11/19/2017 MSDN High Water Mark Reports What you need to know Questions Available from the DevSalesBI Portal ( Complete MSDN subscription assignment history for the life of a customer agreement Reports are governed by your MSSales access High Water Mark Reports should be treated as one source of input and one part of a larger discussion; Not a single source of truth; May contain duplicate user data that should be reviewed carefully Answers Where do we get the reports? What do they contain? Why can’t I access a given report? How should I use the reports? © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 MSDN High Water Mark Reports What you need to know (contd) Questions A High Water Mark Report should be provided to your SAM partner after you have assigned them to deliver a SAM engagement and before they begin the main/onsite phase with the customer The reports contain Personally Identifiable Information (PII) for the customer’s users, so reports should not be forwarded as unencrypted attachments; Please use encrypted or secure FTP to deliver reports to partners Answers When should I provide the reports to my partners? How should I provide the report to my partners? © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 MSDN High Water Mark Reports What you need to know (contd) Questions You should work closely with the Developer Tools Solution Specialist (SSP) assigned to the account who can often provide historical profiling and background for the account that you will want to incorporate into your review; You may also contact the Developer Tools AP Champ in your region for additional input. Contact the TBD alias for support Answers Where do I go for help reviewing the reports? Where do I go for technical help with the DevSalesBI Portal? © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Going further Turn your customer briefing into a conversation
11/19/2017 Going further Turn your customer briefing into a conversation © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Exchange Server SharePoint Server SQL Server 1 SQL Server 2
11/19/2017 Exchange Server SharePoint Server SQL Server 1 POP QUIZ: Environment scanning discovers these machines… SQL Server 2 Windows Server © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Developer 1 Exchange Server Developer 2 SharePoint Server
11/19/2017 Developer 1 Exchange Server Developer 2 SharePoint Server Tester (Non-coding) SQL Server 1 IT Pro User logs cross referenced with HR and Active Directory records show all of these users accessing all of these machines… SQL Server 2 Technical PM Windows Server © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Visual Studio Professional with MSDN SharePoint Server
11/19/2017 Developer 1 Visual Studio Premium with MSDN Exchange Server Developer 2 Visual Studio Professional with MSDN SharePoint Server Tester (Non-coding) Visual Studio Professional with MSDN SQL Server 1 IT Pro Unlicensed MSDN Report shows these users have the MSDN subscriptions shown. How many of these users are correctly licensed to access all of these machines? SQL Server 2 Technical PM Unlicensed Windows Server © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Visual Studio Professional with MSDN SharePoint Server
11/19/2017 Developer 1 Visual Studio Premium with MSDN Exchange Server Developer 2 Visual Studio Professional with MSDN SharePoint Server Visual Studio Premium with MSDN MSDN Platforms Tester (Non-coding) Visual Studio Professional with MSDN SQL Server 1 IT Pro Unlicensed MSDN Platforms ANSWER: Because the environment includes Exchange Server and SharePoint Server, only the first user is correctly licensed. SQL Server 2 MSDN Platforms Technical PM Unlicensed Windows Server © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 Thank you! © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 Call to action Put the SAM Engagement Framework for Dev Tools to work for you Learn Use Educate Improve Read and understand engagement framework content, Attend upcoming Microsoft webcasts and training calls and other opportunities to delve deeper into the material Apply framework content in your SAM engagements involving Developer Tools Increase awareness of best practices, tools and processes among customer stakeholders and your own personnel Help us to improve the framework by providing feedback and identifying key areas that need more coverage © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 Online resources You can find the latest versions of many of the SAM Engagement Framework for Dev Tools materials online Complete Materials All Dev Tools SAM Engagement Framework Materials Public Link Coming Soon! Individual Materials Visual Studio 2013 and MSDN Licensing Whitepaper MSDN Subscriptions Administration Guide Microsoft Product Use Rights MSDN Platforms Product Information © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 Appendix © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Onsite - Domain/machine identification
11/19/2017 Onsite - Domain/machine identification Understanding Cloud considerations for SAM Challenge Solution How does the Cloud impact how we should be looking at a customer’s environment with respect to Developer Tools? Visual Studio Online Visual Studio Online is easy for customers to manage. If users are using, the customer is already paying for it Also, VSO benefits are included with every MSDN subscription, seeding the market and paving the way for a strong future in the Cloud Azure Approach MSDN-sourced software running in VMs on Azure during a SAM engagement just as you would VMs running on on- premise hardware © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2017 Improving SAM Engagement Accuracy for MSDN, Visual Studio, and Dev/Test Environments Carlos Zimmermann – WW Sales Director John Griffin - US.

Similar presentations

Presentation on theme: "11/19/2017 Improving SAM Engagement Accuracy for MSDN, Visual Studio, and Dev/Test Environments Carlos Zimmermann – WW Sales Director John Griffin - US."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

11/19/2017 Improving SAM Engagement Accuracy for MSDN, Visual Studio, and Dev/Test Environments Carlos Zimmermann – WW Sales Director John Griffin - US.

Similar presentations

Presentation on theme: "11/19/2017 Improving SAM Engagement Accuracy for MSDN, Visual Studio, and Dev/Test Environments Carlos Zimmermann – WW Sales Director John Griffin - US."— Presentation transcript:

Similar presentations

About project

Feedback