When implementing TouchID for an enterprise authentication solution there are some interesting attack vectors to consider, that are not obvious.
There are differences in requirements between COPE and BYOD deployments for instance.
Depending on the type of deployment and the type of data accessed, the security required may call for (a) a simple TouchId based “user presence check”, without a password being stored or retrieved, or (b) for a password to be stored in the enclave to be retrieved, or (c) for TouchId to be combined with another factor for a multi-factor authentication solution.
Some drawbacks to the initial TouchID implementation for enterprise uses cases, were discussed here . There is now a developer API available which allows more flexibility in implementing a solution for the enterprise.