Why it is not recommended to remove "artifactory" from the Context URL in Artifactory 7?

Prior to Artrifactory version 7.0, it was possible to remove the /artifactory context, either by modifying the Tomcat configurations or via the reverse proxy configurations. In subsequent versions of Artifactory (Artifactory 7.0 or higher), as a result of architectural changes to the application, this is no longer possible.

Artifactory 7 introduced the notion of the “JFrog platform”, where Artifactory is no longer a standalone product, but rather a part of the larger, unified platform.

Because of the unified platform approach, it is impossible to run Artifactory as the root Tomcat context, and the reverse proxy configurations could (and should) not be modified in such a way, as the reverse proxy should be configured to route other JFrog contexts (For example: /ui, /mc, /access and others) to the Router microservice, and not to the Artifactory microservice.

The following wiki article provides an overview of the JFrog platform's unified approach:
https://www.jfrog.com/confluence/display/JFROG/System+Architecture