We could reduce the operational cost for our customers drastically if we had the possibility to disable certain indexes that come with standard F&O that are not used in the context of a customer.

In AX 2012, it was possible to achieve this by setting a SysDeletedObjects config key that was disabled through overlayering. Unfortunately this is no longer possible in D365FO. I believe it should be possible to safely use the same strategy through table extensions, at least for nonclustered and non-PK indexes.

Bonus point if we also get insights in the index usage of the production environment through the SQL DMV dm_db_index_usage_stats to perform this exercise properly.