edits for new content

Author: haywoodsloan

support/power-platform/power-automate/flow-run-issues/triggers-troubleshoot.md

@@ -346,9 +346,15 @@ To ensure your flows continue to function as expected, follow these steps:
 
 > [!NOTE]
 > If a flow uses an HTTP action to call another flow, the parent flow is considered to be an external system. The URL in the parent flow should be updated with the new URL that is displayed in the child flow's trigger card. However, if the child flow is called through the **Run a child flow** action no change is needed.
->
-### Get admin view of all flows
 
-Admins can also use Powershell script (https://www.powershellgallery.com/packages/Microsoft.PowerApps.Administration.PowerShell/2.0.216) to list all flows with these triggers along with flowID and environmentID to facilitate the update. 
-<img width="3837" height="893" alt="image" src="https://github.com/user-attachments/assets/cf203563-202a-478e-acc5-c979f7721ade" />
+### List all flows with migrating trigger URLs
+
+Admins can use the [Microsoft.PowerApps.Administration.PowerShell](https://www.powershellgallery.com/packages/Microsoft.PowerApps.Administration.PowerShell/2.0.216) package to list all flows whose trigger URLs will be migrated. Having the package installed, run the following PowerShell cmdlet:
+
+```powershell
+Get-AdminFlowWithMigratingTriggerUrl -EnvironmentName <EnvironmentName>
+```
 
+The cmdlet gives an output similar to the following example:
+
+<img width="3837" height="893" alt="image" src="https://github.com/user-attachments/assets/cf203563-202a-478e-acc5-c979f7721ade" />