You plan to use
- an Android Custom ROM not certified by Google
- not supported by Fairphone
- still in beta stage
- coming without the genuine Google services
- replacing them with an Open Source reimplementation of parts of them
- which even for the parts it covers can conceptually never reach 100% compatibility to the original over time, because Google can at any moment break compatibility by changing something on their side which microG would need to catch up on (again, as this really happens from time to time)
to seriously, professionally use Google-dependent Apps?
You really think you can work around this?
Here’s what you could try, if you really need some extra thrill in your work environment:
- /e/ is a degoogling effort for reasons.
Drop /e/ and install LineageOS once it’s going official (in LineageOS terms), as LineageOS is closer to AOSP than /e/ and contrary to /e/ should still have everything in it the genuine Google services themselves need to work. - Install the genuine Google services via Open GApps or similar packages.
- To play it safe with your Google account, have a look at Google’s device registration for the use of Google Apps and services on non-certified Android OSes … https://www.google.com/android/uncertified/
Still no Fairphone support, automatic nightly builds you have to check yourself for possible functionality regressions after every update you install … but running Google-dependent stuff much better than /e/, conceptually. Have fun 
!