Retention Labels – PowerAutomate integration doesn’t support solution flows?
Hi there,
As explained in the documentation here, you can now call a PowerAutomate flow when a retention label reaches the end of its retention period, which is great.
However, based on my tests, this functionnality does NOT support flows that are part of a solution. It only works for flows created in “My Flows”.
Am I the only one thinking no serious enterprise would handle a process as big as tenant-wide retention using a “personal” flow created by a random user in “My Flows”? I would rather use a “corporate” flow that is packaged, service-principal-owned and deployed through staging environments using ALM best practices but somehow someone decided that solution flows weren’t supported, which makes the functionality useless 🙁
Anybody found a workaround to make it work with a solution flow?
Thanks!
Hi there, As explained in the documentation here, you can now call a PowerAutomate flow when a retention label reaches the end of its retention period, which is great. However, based on my tests, this functionnality does NOT support flows that are part of a solution. It only works for flows created in “My Flows”. Am I the only one thinking no serious enterprise would handle a process as big as tenant-wide retention using a “personal” flow created by a random user in “My Flows”? I would rather use a “corporate” flow that is packaged, service-principal-owned and deployed through staging environments using ALM best practices but somehow someone decided that solution flows weren’t supported, which makes the functionality useless 🙁 Anybody found a workaround to make it work with a solution flow? Thanks! Read More