How MI One maps what you own to what you run: entitlements from contracts, deployments from connectors and imports, and utilization per product.
By the MI Solutions SAM team8 min read2 exhibits
Entitlements tell you what you own. Deployments tell you what you use. Mapping one to the other, product by product, is what turns two lists into a license position: where you are paying for idle licenses and where you are exposed. MI One does this mapping continuously.
The flow
Exhibit 1
Where deployment data comes from
01Connectors
Microsoft, Okta, Google Workspace, Google Cloud, AWS, Azure, Jamf and Salesforce.
02Admin-portal exports
For SaaS products without a connector: upload the export, preview the rows, then apply.
03Spreadsheet imports
Any other source, with column mapping and duplicate detection.
What you see
For each product: licenses owned, deployed and in use, utilization over time, and the users behind it with their last-seen dates and costs. See effective license position.
Exhibit 2
How mapping stays current
Data syncs
Connectors refresh deployments and last-seen dates on a schedule.
Imports add the rest
Admin-portal exports and spreadsheets for products without a connector.
Mappings apply
New deployment records are linked to the entitlement they consume.
Utilization updates
Owned vs in use refreshes per product, ready for the next review.
Get started
Frequently asked questions
Does mapping need to be set up for every product?
Start with the products that carry the most spend or risk. Many mappings follow automatically once products are normalized.
What if a product has no connector?
Use an admin-portal export or a spreadsheet import.
How often does the data refresh?
Connector data refreshes on a schedule; imported data refreshes each time you import a new export.
See where your software budget goes
Bring your five largest vendors to a 30-minute call. Our SAM experts will show you where the savings usually hide, and how fast MI One can surface them.
