Currently in order to publish a FeatureService (for editing, sync, extract, replication, etc.) by reference from an enterprise geodatabase, you need to also publish the associated MapService (enabling "feature service" in the process.
However sometimes all we need is the FeatureService (e.g. for extract workflows with visualization on datasets that don't need a mapservice to power visualization). It would be nice if there was an option to just publish the FeatureService. I imagine that might reduce strain on server resources, minimize the number of Portal assets, and lessen confusion to users (especially new users), when looking at a FeatureService and MapService of the same exact data.
