 Vincent says that creating a power app that will run under a service account that has access to Exchange online to send emails. Pretty straightforward. I'm being told that the service account needs to hold an E3 license, which seems overkill to me. E3 includes installable office applications. So why would I need that? Surely an F3 or even an Exchange plan license would suffice. What are others using? E3 or E5, just like the requirements say, the difference between those other two licenses that you mentioned in the front line. F3 is a frontline users license, and it just simply isn't available for them to do that. The same with the Exchange only. A service account has got to have permissions to work within the context of the back-end of the service, and neither one of those contacts do. It's pretty straightforward. I know that he says with the overkill of it, but Power Apps is a pretty complex application, which requires plug-in to pretty much the whole suite. If you're going to do Power Apps, you don't want to provide Power Apps where an F3 worker has very limited functionality so they can just get their job done out in the field. That is the basics of working online. They don't need the desktop apps, they don't need all that. Therefore, having something like Power Apps to plug in, just doesn't make sense from a licensing perspective. Hence why you then have to go to the next level and have literally things lit up so that when you start to create anything that sits in that Power space, because Power, literally Power, is about getting stuck into everything. It's kind of the one or the other. You've got to go down the road of a higher license. The F3 is not going to cut it.