Can a feature service use data from a file geodatabase?

[AllenDailey1]

Can you publish a feature service (as opposed to a map service) from Pro if the data lives in a file geodatabase rather than an enterprise geodatabase? 

I am trying to do this, and when analyzing before publishing, I get Error 00134: "Layer's data source is not supported" for all the layers.  

All the layers come from a single file geodatabase that is stored in a folder on the same ArcGIS Server that all of our services are published on.  That is, the data and the service would be on the same server.

I searched Esri documentation about this question and couldn't find an answer that seemed clear to me.

I also found this Esri Community post from 2016 that says it's not possible, but I'm wondering if things have changed or not.

I'm using Pro 3.0.3 and Enterprise 11.3 (I should probably update Pro...).

I don't need editing enabled; I just want a feature service because the layers have problems rendering in AGOL as a map service, and when I turn on feature access for the layers in Server Manager, the rendering problems go away.

[JoshuaBixby · Accepted solution]

Short answer, you can't.  Typically software companies document requirements, not non-requirements because listing the latter would be a never ending task.  That said, sometimes a specific non-requirement is important enough to state clearly.

In the case of feature services (see Feature services—ArcGIS Server | Documentation for ArcGIS Enterprise), there are a lot of requirements so it can be easy to get lost going through them all.  Probably the most concise statement that answers your question, albeit it doesn't necessarily jump off the page, is from Prepare data to publish a feature service—ArcGIS Server | Documentation for ArcGIS Enterprise:

Requirements common to geodatabases and databases

The following requirements are true whether the source data is stored in a relational database, a cloud data warehouse, or an enterprise geodatabase:

The 3 types of "databases" mentioned are relational, cloud data, and enterprise.  A file geodatabase is not included, nor is a mobile geodatabase, shape files, or many other data formats.

[AllenDailey1]

Thank you so much for your reply.  That all makes sense and is helpful.