Actually for some use cases it does make sense, but as a general approach it may help with provideing more flexibility in how enterprises are using your platform and how they apply existing processes in your solution. Example as follows:
We create cases automatically and we map work orders to cases in a 1 to 1 scenario.
We automatically assign the work orders based on SLAs, tech availability and user preference etc.
We also automatically populate knowledge in Dynamics 365 from external systems, because of the multitude of systems that the techs need to act upon.
Our techs work directly inside the work order, using "checklists" that involve interaction with multiple "products" that need to work on (think about IT field services, where the work order can consist of steps that span multiple products: backup the device using product X, reimage the device using product Y etc.) and other components specific to the work order.
For them to access the knowledge and be able to use the "search" engine associated with this knowledge module, they need to go back to the actual case and lookup the knowledge article that may apply to what their work order entails, then navigate back to the work order to continue their "intervention". This creates an inefficiency in the process, as the technician has to go back and forth from case to work order etc.