Putting the “Auto” Back into Autodesk

There are some software packages that politely walk into a packaging process. Autodesk tends to arrive with a toolbox, a clipboard, three licensing paths, and a small queue of follow-up questions.

That is not a criticism of Autodesk. It is powerful software, used in complex ways, across a wide set of subjects and courses. But that complexity can make packaging harder than it needs to be.

So, we have been working on a better way!

Redrawing the Autodesk packaging process

Autodesk applications have historically been among the more complex packages we deliver. Your environments vary, licensing requirements vary, and even small differences in setup can create extra work for institutions and support teams.

One of the recurring pain points we’ve found has been the use of CSV files alongside the Master License Appset. CSVs are useful in the right context, but they can also introduce avoidable issues when edited, formatted, shared, or handled differently across environments.

In short, there were too many moving parts!

Small changes to a CSV file could create disproportionately large headaches, both for customers and our teams.

Since April, we have been reviewing our Autodesk packaging process with a focus on reducing those avoidable support moments and making the experience smoother for customers.

Engineering out unnecessary complexity

Starting with Autodesk 2027 applications, we are introducing a new approach that removes the need for CSV files while continuing to support Autodesk licensing requirements.

The Master License Appset will still be required, so this is not a full reinvention of the process. But it is a meaningful step towards making Autodesk deployments cleaner, more predictable, and easier to manage.

Autodesk 2026 and earlier versions will continue to be supported using the existing licensing model and CSV-based approach. That backwards compatibility matters, because improvement should not create unnecessary disruption for customers already running earlier versions.

Fewer moving parts

The aim is simple: fewer moving parts, fewer avoidable errors, and a more consistent Autodesk packaging experience.

• Reduce setup and configuration issues
• Simplify Autodesk licensing and deployment
• Improve reliability across different customer environments
• Remove common CSV-related errors from the process
• Maintain compatibility with Autodesk 2026 and earlier deployments
• Make Autodesk delivery easier to support and manage over time

From workaround to workflow

This is also part of a wider enhancement for our Packaging Service. We are looking closely at where customers lose time, where requests become harder than they need to be, and where we can make the experience feel more joined-up.

Autodesk is a good example because it is exactly the kind of packaging area where small improvements can have a big impact. Removing CSV handling from future versions should reduce friction, improve reliability, and make the process feel more like it should: submit the request, provide the right information, and let the service do more of the heavy lifting.

There is much more to come, but this is another useful step in making packaging easier, clearer, and more dependable.

A cleaner blueprint for Autodesk delivery

We are continuing to test and validate the new model, with a target release in summer 2026. In packaging terms, this is our version of tidying up the drawing board: keeping what works, removing what causes friction, and building a cleaner blueprint for future Autodesk releases.

For now, the headline is simple: We're putting the "Auto" back in Autodesk by taking unnecessary complexity out of the packaging process.

Need a hand with the plans?

If you have any questions, feel free to message me or raise a ticket with us.