Tenant Pool Usage, a new option or not?

[powerdeva01]

Hello,

Last week we suddenly see a option "Tenant pool Usage", this is a switch on each flow and it is enabled on all our flows.

Is this a new option? and why is it default enabled?

 

Because this is enabled some flows are disabled and we cant enable them, we then get this message "Cannot enable tenant pool for flow 'id', the flow must be owned by an application user and in dynammics app context."

Am i missing something here and did we caused this by ourself or is this really some new option introduced in the platform? Thank you.

[MarkVoldersCron]

I have the same question. This recently showed up but no documentation of Microsoft to be found.

[powerdeva01]

Very strange indeed.. 

[PriyaKodukula]

Thank you for bringing this to my attention. We will fix this as soon as possible. 

Application user/Service principal flows draw from a tenant pool. See this document below

https://learn.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations#non-licensed-u...

We recently released a feature (still in rollout) that enables makers to turn on tenant pool for their critical flows that need  higher Power platform requests. If the toggle is on, it is using from tenant pool. To avoid noncritical flows from using up the tenant pool, the maker can turn off the tenant pool on the flow. This feature is only available for flows owned by Service principal and in context of Dynamics 365 applications.

In this case, when the flow was running under service principal and has tenant pool turned on (default setting for all previously created flows). When the solution was imported in a different environment, it is imported as a user (not service principal) hence the error . 

Workaround: Turn off tenant pool in the source environment and import again. 

[Jon7]

"Workaround: Turn off tenant pool in the source environment and import again. " 

We have an Azure DevOps pipeline promoting a solution with these flows. In our source environment, we do not have an option for a tenant pool. When we promote the flow, it turns off the flow and checks the Tenant Pool flag.

Are there any other workarounds to disable the Tenant Pool by default?

[hjaf]

"Dyna_mm_ics", kinda feels like someone rushed this into production a bit?

Which dataverse version was this introduced (I'm seeing the error on version 9.2.24022.00196)? 
I'm only blessed with this error message and have no such option available, I can't find any documentation about this toggle. I have never seen this option before, neither in the source environment or any of the other environment I have checked. Perhaps this is related to the introduction of application association for flows (?), in my case the flow is associated with a power app.

Its about time we do not have to opt out of using a "unstable" version where undocumented functionality could be introduced.