Really no good reason to introduce hundreds/thousands of potential errors into your workflow. Now everything I mentioned before was under the assumption this was going to be privately used, it's especially a bad idea for work in my opinion. It's not strong enough and it wasn't designed to be. Looking at the specs of the m1 and benchmarks from what I can see, it still doesn't hold up against windows counterparts, especially for high level CAD and gaming. Now let's say you somehow get everything to load and 'work' on a MAC, there are still many features and verticals that don't work on it because they weren't designed to. AutoCAD is still designed to run on the intel structure and microsoft probably hasn't worked out a reasonable solution to get 'windows' onto the new Macs and work with the ARM structure. This is going to be worse with the new M1 chips because of their ARM structure vs x86.

Even though most current apple computers use intel x86 chips, it's still a different OS so you need to run a software to virtualize windows or get a second OS on your machine.

In general, using apple for AutoCAD is a bad idea. Are you intending to use it in conjunction with a VM like OP mentioned or as a standalone? Either way it's likely not great, VM only works if you have IT / CAD staff that actually understand how to make it all work rather than just 'setting it up and leaving it'.

Autocad apple m1