Type "Team" or "Enterprise"

The main difference Between the Teams Subscription and Enterprise Subscription is the Deployment Options and Identity Options.  There is more control available under the Enterprise version and it is a little higher in cost.

Enterprise allows for Enterprise ID's and Federated ID's. 

My understanding is that with the Teams version only Adobe ID's are used.

With Enterprise you can package and push out the installation easier, where with Teams I believe that it is a local install on the device.

Acrobat DC for enterprise provides the robust IT infrastructure needed to manage enterprise capabilities, including: •Support for multiple types of administrators

•Service configurability

•More secure identity methods (including SSO)

•Dedicated-key file encryption These enhancements offer more value for organizations that need enterprise-level control and support.

What forms of identity are supported in Acrobat DC for enterprise?

One of the advantages of Acrobat DC for enterprise is the option to select the user authentication method that works best for your organization. Acrobat DC supports authentication through Adobe ID, Enterprise ID, and Federated ID (SSO).

• Adobe IDs are hosted by Adobe and managed by the end user. Users go to Adobe.com and set up their own ID based on email and self-selection of a password. The organization cannot control users’ access to apps, services, and files. This identity is used for Creative Cloud for individuals, Creative Cloud for teams, Acrobat DC for individuals, and Acrobat DC for teams. It’s also the default identity for enterprise licenses.

• Enterprise IDs are created, owned, and managed by an organization. Adobe hosts the Enterprise ID and performs authentication, but the organization maintains the Enterprise ID. End users cannot sign up and create an Enterprise ID, nor can they sign up for additional products and services from Adobe using an Enterprise ID. Admins create an Enterprise ID and issue it to a user. Admins can revoke access to products and services by taking over the account or deleting the Enterprise ID to permanently block access to associated data.

• Federated IDs are created and owned by the organization and linked to the enterprise directory via federation. The organization manages credentials and processes SSO via an SAML2 identity provider.

Both Federated and Enterprise IDs require an IT infrastructure to execute.