Skip to content

Commit fde5622

Browse files
committed
make links relative
1 parent cb696ed commit fde5622

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Many people feel there are significant gaps between SharePoint Designer (classic
6767
- **Workflow history storage** – Flows maintain an extensively detailed history in the context of the flow itself in the Power Automate dashboard for the runs that have occured in the last 28 days. If you need tracking in your sites, or keep historical logging longer than 28 days, you can have the flow log information in a list you create.
6868
- **Impersonation** - In SharePoint 2010 workflows, you can add an impersonation step to act as a different user. You could achieve similar functionality by using different user accounts with different (elevated) priviledges for certain actions. Alternatively you can consider using an Azure Active Directory Application registration, assigning it permissions and using that to directly call into the APIs. The latter will require a Premium Power Automate license and requires more manual effort to make the calls.
6969

70-
While these pain points do exist, you can see there are workarounds for each of them. Do beware that some of these workarounds will require a Power Automate Premium license. Read more about the [license implications](https://learn.microsoft.com/power-platform/admin/power-automate-licensing/faqs#i-have-multiple-flows-running-under-a-shared-service-account-what-licenses-do-i-need) of doing so and [who will require to have a Premium license](https://learn.microsoft.com/power-platform/admin/power-automate-licensing/faqs#who-needs-to-purchase-a-premium-license).
70+
While these pain points do exist, you can see there are workarounds for each of them. Do beware that some of these workarounds will require a Power Automate Premium license. Read more about the [license implications](/power-platform/admin/power-automate-licensing/faqs#i-have-multiple-flows-running-under-a-shared-service-account-what-licenses-do-i-need) of doing so and [who will require to have a Premium license](/power-platform/admin/power-automate-licensing/faqs#who-needs-to-purchase-a-premium-license).
7171

7272
## Modern approvals with Power Automate flows
7373

0 commit comments

Comments
 (0)