hi everyone this is universe in today's demonstration we'll talk about bring your own license and its support on servicenow sam pro so let's get started before understanding how servicenow samples supports bring your license let's understand the different licensing rules for microsoft products as well as oracle products on their deployments in aws and azure notice for example windows server has got different licensing rules for aws and azure also there are different licensing rules when software assurance is enabled versus when it's not enabled for example you can notice here that for windows server deployment on aws share tenancy host bviol is not allowed when software assurance is enabled or when it's not enabled this is because windows server does not have license mobility rights this is an important licensing rule another licensing rule states that windows server data center allows dual use rights when software assurance with azure hybrid benefit is enabled there's also additional flexibility which states that windows server standard licenses can license the windows server data center installs on microsoft azure notice that these rules are only with software assurance when software assurance is not enabled these benefits that are enabled for azure are not applicable anymore also notice that there are licensing rules for dedicated hosts one of the main licensing rules which was effective on first october 2019 states that b value is not allowed for purchases made after first october 2019. this is for aws dedicated so you can see that there are different licensing rules uh which need to be determined correctly to determine the correct license compliance position let's go to sql server again notice that there are different licensing rules for aws and azure shared versus dedicated host in here notice that for aws shared with software assurance by l is allowed this is because sql server has got license mobility rights however if software assurance is not enabled the viral is also not allowed notice that for microsoft sequel server deployments on azure when there is software assurance enabled and azure hybrid benefit is enabled there are certain benefits for example there is a benefit for edition flexibility which states that one sql server enterprise on-prem can cover for four sql server standard on azure these are some of the benefits that you get when you deploy sql server on azure share tenancy host as you can notice that there are different licensing rules on dedicated host as well as we just spoke about dedicated host there is a recent licensing change from microsoft which is effective from first august 2019 which states that [Music] if you have purchased licenses after first october 2019 without software assurance and mobility rights they cannot be deployed on dedicated hosted cloud services offered by the following cloud providers microsoft alibaba amazon and google they will be referred to as listed providers so you can see that you know there are different licensing rules for dedicated host as well as share tenancy host on azure as well as aws now when we come to oracle db server the rules are totally different we can see that for aws and azure the core factor table is not required also notice that there are certain size limitations for example standard edition 2 can be run on a vm but not more than 8 vcpu cores if i go ahead i can see that there are different licensing rules for options and packs as well for example oracle rsc or real application cluster is not authorized on the cloud providers unless it's oracle cloud so you can notice that there are different licensing rules for named user licenses and ula multi-asia deployments and so on and these need to be respected so that the correct license compliance position can be gathered all right so let's move to uh the demonstration uh i'll be talking about uh some use cases here so in this use case we have got sql server deployed uh on a shared tenancy dedicated host tenancy across aws in azure and the vms will consume rights as per the licensing rules and we talked about some of the optimization benefits for example edition flexibility benefit uh unlimited virtualization benefit and so on these will be auto applied by servicenow in another use case we have got windows server and it's deployed across aws dedicated host as well as shared host as well as azure shared and dedicated list and here again all the licensing rules are applied and benefits such as addition flexibility and dual use rights that apply and also uh as we just uh just saw that viral is not allowed for windows server deployments on uh aws dedicated host if the purchase date is greater than first october 2019. also b viral is not allowed when windows server is deployed on aws or um shared or dedicated tenancy host as it does not have license mobility rights so these are some of the rules that we'll check in the demo i've got another use case for oracle db server and it's also about oracle db deployments across aws which includes both iis and pass pass is aws rds as well as the aws uh uh oracle deployments on microsoft azure and on-prem so all these licensing rules will be combined together and an effective license compliance position can be determined accurately on servicenow sample so let's get started so i've logged in as a sam manager and i've gone into the microsoft license workbench the first thing i noticed is that i can see the microsoft products across hybrid environments which gives me the installations of all microsoft products across on-prem azure and aws i can see the license types bring your own license or license included across both aws and azure i can click on on these charts and drill down to see the exact resources or the installs having those license types now as a use case was about sql server first uh let's deep dive into that so i'm going to sql server 2017 enterprise and i can notice that uh i can see the license results which is showing me that 130 licenses are owned and about 108 licenses are required that means i'm compliant i can drill down into the license required section and see all the resources consuming license i can see that there is azure shared tenancy host which are consuming license there is an azure dedicated host that is consuming license and there is an aws dedicated host that is consuming license i can see that um the dedicated host um is consuming 32 rights and uh aws dedicated host is consuming 36 rights and this is also an azure benefit that is applied for dedicated boost moving on i can see that this vm is a 16 core vm as but it's still consuming just four writes and this is because of addition flexibility i can notice the number of cores here i can see that it's a 16 gold machine having sql server standard installed and i can go to the cloud special rights section to determine that if any special write was applied for the same and i can notice that although it's a 16 core vm only four core rights got applied and this is because of uh additional flexibility which is an azure hybrid benefit are applicable only for deployments of sql server on microsoft azure when software assurance is enabled so you can notice that servicenow sam pro can automatically apply these optimization benefits all right so let's move to another use case in here we'll talk about windows server and i'll go to windows server 2012 and i can notice that a removal candidate got automatically generated and let's see what this removal candidate is about notice that this is a deployment of windows server on aws shared environment and what service now is telling you that it is an unlicensed install because windows server does not have license mobility benefits and hence it cannot be deployed on aws shared environment if you have software assurance or if you do not have software assurance hence your advice to decommission the virtual machine so you can notice that you know this is a risk for organizations and servicenow is automatically creating removal candidates if it encounters any such installation risk all right so let's move to another use case this time i'll talk about windows 7 2019 data center i can now go to the entitlements i can see that it's a it's a core gal entitlement with software assurance enabled and the purchase date is less than first october 2019. that means it is a valid install i can go to the license required section again and notice uh the aws dedicated host consuming license now if the purchase was greater than 1st october 2019 then the aws dedicated host is not allowed to be deployed and this is automatically taken care by servicenow sampro and move back and go to the remediation options the servicenow has automatically generated some remediation options and if i click on remove unlicensed cloud installs it will start creating removal candidates which are basically workflows to correct the non-compliance and servicenow sam as we just saw provides enough context to the sam manager as to why these reclamation candidates are created and what is the action for the same and this notice that this is a deployment on aws dedicated host and this is unlicensed because the number of rights are less however servicenow sam is pointing out that there is a risk because uh uh you will not be allowed to upgrade windows server software to versions released or purchased after first october 2019 and hence you are stuck here therefore it's advised to decommission the virtual machine or uninstall the software so notice that risk which can happen in the future but also uh determined by uh by servicenow sam pro and a showcase to the sam manager so that they can take effective action on the same so that was about windows server as well as sql server um there's one more thing which is uh shown on the progress indicators which is the number of cloud assets covered by byos so if you want to know all your cloud assets covered by byol you can just click on the progress indicator and drill down into that specific chart all right so that was about microsoft let's move to oracle so i'll move to oracle here and uh i'll go to the oracle database server enterprise edition and notice here that in the similar manner there are progress indicators for the number of cloud assets covered by byol what is the license types of oracle db server across azure and across aws and i could drill down uh into them notice for oracle db server for aws the past resources are also discovered including the license type now as i was moving to enterprise i will move to enterprise and i'll directly go to the removal section removal candidate section and i can see that servicenow has automatically generated reclamation candidates for real application cluster and that is because real application cluster is not authorized to be activated on the aws data center environment hence it is advised to deactivate this option notice here again that servicenow is pointing to the license compliance risk that the organization can face if real application cluster is enabled the similar manner servicenow sam creates all these remediation options optimize vc view remove unlicensed installs etc and if you click on them it will create removal candidates and those removable candidates will have adequate information as to what why why is it a potential risk and what needs to be done to fix it in this case you you have shifted your licenses to the cloud without having adequate on-prem rights so this is a license compliance risk in a similar manner if i move to standard edition two and go to removal candidates and open up the removal category for standard edition two i can see that again servicenow sam has automatically generated the reclamation candidate here and this is because oracle database standardization 2 is incorrectly deployed on a vcpu having size 16. and we just noticed that the licensing rule states that edition standard edition 2 can only be licensed on authorized cloud environments having size max up to 8 vcp and hence this is uh advised to uninstall the oracle database standard edition 2 from this environment so you can see that both for microsoft as well as oracle the framework of licensing remains the same if the license compliance is correct license will be consumed if they are incorrect then a removal candidate or a remediation option will be created with a workflow so that sam managers can take adequate action for the same in addition we just saw that you know you could look at the license types across azure and aws and also determine uh all the cloud assets covered by byo before ending i'll talk about few reports which we have introduced one is the azure vival relay savings report and this report is about the actual savings that the customer has has received if they have enabled azure hybrid benefit you can see that there is the standard price mentioned the actual price mentioned the standard saving relies and the actual savings released so this is a good indicator for organization to determine the actual savings when azure hybrid benefit has been enabled for their deployments on azure another report is the oracle db server deployments per agreement this is also important because there are significant risk if you have got oracle deployed on a ula contract so this report gives enough information as to um as to where that oracle db server is deployed and what is the agreement type whether it's generic or it's unlimited licensing so these are the two major reports on on bring your own license for both [Music] windows server sql server and oracle database server so that concludes the demonstration thank you