cleanup

Author: haywoodsloan

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

@@ -348,7 +348,7 @@ To ensure your flows continue to function as expected, follow these steps:
 - **Updated trigger URL**: The URL displayed on the HTTP trigger card in your flow's designer will reflect a new URL. This new URL is required for your flows to function correctly.
 - **Length of the new URL**: The updated URL might exceed 255 characters, especially when [Shared Access Signature (SAS) authentication](/azure/storage/common/storage-sas-overview) is configured. Verify that your destination system supports URLs longer than 255 characters and adjust its configuration if necessary.
   - Update your system configurations to support URLs longer than 255 characters, if possible.
-  - If your system can't support URLs longer than 255 characters, consider other solutions such as using a proxy wrapper (for example, see [Azure API Management Quickstart](/azure/api-management/get-started-create-service-instance)), Azure Functions, or similar approaches.
+  - If your system can't support URLs longer than 255 characters, consider other solutions such as using a proxy wrapper like [Azure API Management](/azure/api-management/get-started-create-service-instance), [Azure Functions](/azure/azure-functions/functions-get-started), or a similar approach.
 - **Warning banner**: A warning banner will appear on your flow details page or within the designer, displaying the old URL that has been replaced. This serves as a reminder to update any references to the outdated URL with the new URL. If you do not see the warning banner on flows with HTTP or Teams webhook trigger, your environment is most likely on Self Host Multitenant architecture, and your flows will not be impacted.
 
   > Click here to copy the new trigger URL. The old trigger URL \<trigger URL> will stop working on November 30, 2025. Your tools that use this flow WILL break unless you update them with the new URL.