The built in DI doesn't support it. You can continue to use Autofac if you want. It integrates with MS DI.
But ultimately it is sign your design might be incorrect. Aggregation is the general solution to this but aggregating interfaces is an anti-pattern in many cases because you're not actually using the interface as an abstraction but a grouping construct. Autofac has no problem with this, and why it recommends that, because it is going to generate a dynamic proxy anyway. Honestly you might do better to just create a regular old class that accepts the interfaces as parameters (you're really just moving them from one bucket to another though). At least in this case you don't have to create 2 types (the interface and the impl that does nothing but group the interfaces together). You still have the same design issue but you've pushed it down to another type.
Long term I would group related interfaces together and then accept those as parameters to your code. At that point I'd be using a regular class if it is just a grouping construct as an interface wouldn't make sense.