Share
ReportLike they say, the devil is in the details. I've been playing around in a sandbox and discovering more and more oddities about the power platform... When you understand the platform they make sense but it sure is dangerous to assume...
I will have a small group of per app licensed users that interact with a model driven app in a dedicated environment. They will take actions in the app that will triggers flows and cause approvals to e3 only licensed users depending on user selection in a lookup. For the e3 licensed users to be options in the user table and to receive these approval requests, they seem to need to be users in the dedicated environment.
My thought is to provision the dedicated environment without a security group (or at least one containing more than just the per app users) for the model driven app. This will ensure that all users are created in the dedicated environment and can receive approvals as far as I can tell. Those users will be active and can be chosen using lookups but none of them will have security roles or per app licenses. Approvals will appear in Teams under the environment (less than ideal, but ok) and they will get their notification. Their responses will be captured in flow and returned to the model driven app.
Does anyone see any issues with this? Any alternative approaches? I think the app will appear in the e3 users business apps section which annoys me but is ok. I could build the app in the default environment but I don't like the sounds of that. E-mails with choices don't allow a "comment" so that's a deal breaker.
Thanks for any ideas and suggestions!
All responses (
Answers (
1,843
