A presentation by Mike Austin explaining how to build an Effective License Position (ELP) for software compliance. The speaker emphasizes understanding which data is required (beyond basic inventory dumps), and highlights that auditors commonly request Active Directory to reconcile device counts during audits—using examples like Office and Adobe desktop products and cloud subscriptions.
Chapters
So when it comes to creating an elp, right, these are the sorts of questions that if you can't answer them, you're going to. You're going to get into some challenges when it comes to compliance. Okay? So it's like, first of all, do I even know what data is required to create an elp? Right? So I'm going to use simple examples, right? I'm getting audited for Office on Desktop back in the day, or I'm getting audited for Adobe Simple Desktop product. We're going to talk about cloud subscriptions right now, but I'm getting audited for Adobe, okay? So I have an inventory tool or I have a software asset management tool. I'll just pull a dump out of there and I'll get the devices and deployments and we'll figure out the accounts. That's not what you need to create an elp, but that's how a lot of people will do it, right? The first thing an auditor is going to ask for is Active Directory, so they can look at the number of devices that you have in Active Directory and compare that to the number of devices that are in inventory.