[Music] hi everyone this is shivas product manager SRO in today's demonstration we'll talk about Microsoft Visual Studio license compliance support on service now s so let's get started so first let's understand what is Microsoft Visual Studio so Microsoft Visual Studio is a subscription that allows development team members to install and use common software like Microsoft SQL Server bit server Windows server and many other softwares to design develop test evaluate and demonstrate these softwares there many tenants to visual Studio software and let's discuss these tenants the first tenant is that it's user based licensing so each development team member requires a visual studio license purchase through a subscription Visual Studio cannot be used for production purposes it can only be used for development and test purposes it includes a wide array of software including the common ones like SQL Windows server biso server and many others the entire list is provided by Microsoft it's provided as a subscription there are many subscriptions such as Visual Studio Enterprise professional test professional visual studio with GitHub and so on each and every subscription has got a defined list of softwares available and then lastly it is managed through a portal so there's a visual studio portal where administrators can check their subscriptions and assign subscribers so those are the major tenants of Visual Studio licensing let's have a quick peek on the licensing rules so it can only be used for development and test environments it cannot be used for production purposes the licensing model is per user based it's available as a subscription mostly and visual studio has provided as um many flavors like Enterprise test professional and and many more uh however Community Edition is a free addition for individual developers so these are the major licensing rules for the full list please check the Microsoft product terms now what are the risk and challenges faced by ATA managers the first risk is uh discovery of infrastructure and user access how do I discover the software and the infrastructure used uh for the users accessing the same how do I determine if there are visual studio subscribers using visual studio in non- production environments or nonsubscribers accessing Visual Studio software how do I license Visual Studio softwares separate from my regular software so this is the common issue that is faced by a lot of organizations ations because they have got U the common softwares like Microsoft SQL Server deployed in production environments and the same Microsoft SQL Server deployed for uh non- production purposes that needs to be licensed to visual studio now how do they separate the license consumption for these two different softwares so that's one of the major risk that are faced by time managers how do I track licens compliance of Visual Studio software and lastly as we just saw that Visual Studio has got a vast array of software there are more than 100 plus softwares how do I keep track of which subscription has got which softwares assigned to it so this is all very hard for uh Sam managers or it time managers and let's see what service now Sam Pro does to support these challenges the first one is that we support discovery of infrastructure and also the users accessing the same the second is that uh we support showcasing unlicensed installs if the visual studio is installed on a production environment for instance as well as a reason for the same as we just discussed you know uh it's important for for Sam managers to determine current correct license consumption of the softwares which are deployed on production environments versus the the softwares deployed on non-production environments which need to be licensed to visual studio so we support configurations so that this license consumption happens accurately we support user based license compliance model and then we have got an entire content Services support wherein for each subscription we maintain an accurate list of what all the softwares that are provided in each subscription so that that list need not be maintained by our customers so those are all the support that we provide for visual studio uh for on service now SRO so uh that was all about support now let's understand what it takes to set up visual studio on service now SRO so uh imagine that you know you're a Sam administrator or a Sam manager so what needs to be done so first of all ensure that the cmdb is accurate with the requisite demarcation of environments this is really critical because this helps service now SRO to accurately consume licenses for the installations thereafter run Discovery and check normalization results import or add entitlements and once you add entitlements you know we Prov provide service now content Services support so that an accurate software model and their components are created with downgrades so this is the uh content Services support that's really critical to ensure that for each different type of subscription purchase accurate list of softwares that you are entitled to is added so that at the end license compliance is defined accurately import the subscriber list from Visual Studio portal and then add the subscriber list as an allocation to the entitlements on service Now sample thereafter configure a product installed condition which just states that this consumption needs to be happened uh for visual studio on dev environment and for for the other software for instance SQL server on production environment this will ensure that the correct license consumption happens for the correct product run reconcillation check license compliance results so that was all about setup on service now SRO of course when once you uh run reconcillation check license compin you would be able to determine the risk of unlicensed installs uh as well as those uh installs which are not allocated in use this will help you determine which Visual Studio softwares installs are on production environment and also determine which are those non-subscribers having Visual Studio software installs the important risk uh which uh the Sam managers need to take into account so that they can fix the visual studio subscriptions so that was all about setup now let's get into details on service now Sam and understand how it works for that we need to understand the use case which is a common use case for most of the organizations so in this case the customer has a SQL Server database software which is deployed both on development environment as well as production environment of course the development environment needs to be licensed with Visual Studio subscription and the production environment needs to be licensed with a SQL Server license so that's what the use case is about now before we go to the demonstration of it how does it work on service now so let's see the right side first which is the entitlements and the models you can see that uh you know uh you added some entitlements and what it does is that uh based on the publisher part number the software model is automatically created because you know as I mentioned there is service now content support and with this all the different uh downgrade rights or the suite components are automatically added so this is really important and thereafter once the installation in this case you know there's installation of a SQL server on a client computer which is a Dev environment is found and discovered it would create a Discovery Model because it would be normalized and determined as normalized and licensable and you can see here that this installation is inferred to visual studio and this inference if you see happens due to the installed conditions that you would have configured so what this picture entirely represents that there is this SQL Server 2022 Enterprise Edition which is installed on a client computer which is a Dev environment and that got inferred automatically to visual studio 2022 Enterprise and what that means is that ultimately the consumption of the license would happen for the visual studio Enterprise entitlement so that's how Visual Studio licensing works in the same way if there was a SQL Server deployment on a production environment in this case uh there is a SQL Server 2019 standard installed on production environment and you you can see that the inference happened to SQL Server 2022 Enterprise because of the product installed conditions which basically match the installation to the correct entitlement and in this case uh the consumption would have happened on the SQL server 2022 Enterprise license so that's how things work for visual studio uh so let's see that in a demonstration so in here I've logged in as a Sam manager um as as as we know the first thing to check is whether I've got demarcation of my production environment and uh development environment so uh usually we use the environment field which is Prov Ed on these server server tables to demarcate but you could use any other nor cature as well so in this case there are about five Microsoft SQL server deployments on production environment and um on the dev environment I think there's about six installations so that was the first thing to check whether the cmdb is clearly demarcated or not now um as we as you just saw that it's important to check if uh the entitlements are added or not so uh let's see if uh there are the requisite entitlements so I will go into entitlement section check for visual studio and I can see here that there is a visual studio Enterprise entitlement which I've added and uh notice that I've added a publisher part number and I've added the user allocations which is basically the the subscriber list from Visual Studio portal so once I've added this I can check if uh the downgrade rights have been added automatically So based on the publisher part number through service now content Services these downgrade rights get added automatically and then um just to check the different softwares uh components which are added as part of Visual Studio I can open the software model and I can go to the suite company components and here I can see all the different software components that are added as part of uh Visual Studio again automatically added as part of content Services here of course I can check if uh for example SQL Server is part of the suite and of course it's it is so this is regularly maintained by service now content services so that for each different type of Visual Studio subscription you get an accurate list of software that you are entitled to so I added uh the demarcation of environments I added my entitlements my locations I think the only thing now remaining is uh the installed conditions so this this is a u fairly new feature introduced in Vancouver where you could create an install condition for product so in this case I've created an install condition which says that for visual studio product the install environment is development and for SQL Server the install on environment is production what it does is that uh for any installation across different versions and editions of Visual Studio wherever the environment is development uh the installs will be inferred to visual studio entitlement and so those installs would actually consume a visual studio license and the same goes for SQL server deployments on production so that was all the setup that is required I've run reconcilation I can now go and check the results so I go into the license workbench and uh first of all let's see things for visual studio I go to the visual Studio software model 2022 uh I see the entitlements here so this were the same entitlements that we just saw about 100 entitlements I can see the license metric result to understand uh the consumption so 100 licenses own about 10 consumed so I can go into the 10 I can see that these are all the different users consuming the license and I can verify these installs and um you can see that these are all the installs that are on U development machines because they would have been licensed through through uh through the product install conditions so that verification is good so now I can easily say that these are all the development machines that you consumed uh with Visual Studio Enterprise license so all these SQL Server deployments are deployed on development environment and hence through product installed condition were licensed through Visual Studio so that was about visual studio now let me go to SQL server and then verify the same here again uh there 200 licenses about 40 were consumed I can understand that these are all the devices consuming the license I can check the installs and I can go to the installed on to check the environment and again in this case the environment has to be production environment is production so that verify is the same um now just as a final check if uh you would want to understand and inference at the install level itself you can go to the installation section and uh just pull in the inferred suite and here you will see that for these installs which are on development environment the inferred Suite is Visual Studio 2022 Enterprise and uh 2022 professional which basically means that these all installs were licensed through Visual Studio 2022 professional so that was uh all about visual Studio license compliance support on SRO let us know if there's any questions thank you