The use case is more of a validation and auditing function. Once the initial phase and happy path of requesting and deployment is made, I am wanting to validate it is deployed as expected and not have to review that validation each time when I look at the consumption tab. There are also other scenarios where a customer may not be aware they have made a change that impacted license entitlements, such as a new server being added to a cluster and therefore consuming additional entitlements. How does one easily identify a new server being added to a virtual environment? The only field I could find that may be able to satisfy what I am looking for is the "Allocation type". It would allow me to easily filter the consumption list to identify new installs that have not been previously validated (allocated). The downside of using that field that I can see is if the application is uninstalled, the device remains allocated (does not consume entitlements) and has to be manually unallocated. ... View more