Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/SupportArticles-docs (branch main) (#11842)

* Update custom metadata for Ubuntu UFW guide (#2070)

* New article for CI 12114 (#11704)

* Update dynamic membership troubleshoot sample links (#11702)

Links SupportArticles guidance to the Microsoft Learn dynamic membership PowerShell sample pages and adds administrative unit coverage.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* New article for CI 12114 (#11703)

---------

Co-authored-by: Ken Withee <27743960+kenwith@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fixed formatting for Note and Tip in article abt auto-labeling (#11707) (#11708)

* New article for CI 12114

* Updated formatting for Note and Tip

* Fixed typo

* AB#11975: SQL25 CU6 KB (#11698) (#11714)

* Initial draft, waiting for final build

* add table

* Add build info

* Update cumulativeupdate6.md

1Edit review per CI 11973

* Update cumulativeupdate6.md

* fix description

* format tables

* add links to release notes

---------

Co-authored-by: Sloan Haywood <haywood.sloan@yahoo.com>
Co-authored-by: Jerry Sitser <36421998+przlplx@users.noreply.github.com>

* Update troubleshoot-application-gateway-deployment-scaling-deletion-failures.md (#2074)

In "Resolution H / step 7," changed "omits" to "issues." This was incorrectly changed from the original "emits." However, "emits" could be translated as "ejects," "expels," or "leaks.

* Updated 24 direct routing articles with an include requested by Rebecca Valdivia (#11830) (#11831)

* New article for CI 12114

* Updated formatting for Note and Tip

* Fixed typo

* Updates to an existing article via CI 11886. Extra writing work needed to fix SME's text.

* New include for Teams Direct Routing articles

* New article for CI 12028, PR 11571

* Fixed typos in links

* Updated 24 articles with a new include for Teams Direct Routing articles

* Fixed the link to the include in 1 file to test

* Updated the link to the include in 23 articles

* Update manage-orphan-flow-when-owner-leaves-org.md (#2075)

---------

Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>
Co-authored-by: Jarrett Renshaw <jarrettr@microsoft.com>
Co-authored-by: Learn Build Service GitHub App <Learn Build Service LearnBuild@microsoft.com>
Co-authored-by: Meera Krishna <meerak@microsoft.com>
Co-authored-by: Ken Withee <27743960+kenwith@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Aarti Goyle <82040308+aartig13@users.noreply.github.com>
Co-authored-by: Sloan Haywood <haywood.sloan@yahoo.com>
Co-authored-by: Jerry Sitser <36421998+przlplx@users.noreply.github.com>
Co-authored-by: Antanina Druzhkina <antanina.druzhkina@gmail.com>

Author: 10 people

support/power-platform/power-automate/flow-management/manage-orphan-flow-when-owner-leaves-org.md

@@ -20,7 +20,7 @@ This article helps you manage orphaned flows in Power Automate after a flow owne
 > [!NOTE]
 > Only users with appropriate privileges can view flows that don't have any valid owners.
 
-On the [environment page from Power Platform admin center](https://admin.powerplatform.microsoft.com/environments), go to the **Resources** tab and select **Flows**. Look for flows that don't have an owner listed in the **Owners** column.
+On the [environment page from Power Platform admin center](https://admin.powerplatform.microsoft.com/environments), select an environment, then go to the **Resources** tab and select **Flows**. Look for flows that don't have an owner listed in the **Owners** column.
 
 If there are many flows, select **Load more** to load the next set of flows. This way, you can ensure you look through all flows that might be orphaned.