fix links, revert ui strings, add rebrand tips

windows/deployment/update/includes/wufb-reports-admin-center-permissions.md

@@ -11,7 +11,7 @@ ms.localizationpriority: medium
 <!--This file is shared by updates/wufb-reports-enable.md and the update/wufb-reports-admin-center.md articles. Headings may be driven by article context.  -->
 Accessing Windows Update for Business reports typcially requires permissions from multiple sources including:
 
-- [Microsoft Entra ID](/azure/active-directory/roles/custom-overview) or [Intune](/mem/intune/fundamentals/role-based-access-control): Used for managing Windows Update client policies services through Microsoft Graph API, such as enrolling into reports
+- [Microsoft Entra ID](/azure/active-directory/roles/custom-overview) or [Intune](/mem/intune/fundamentals/role-based-access-control): Used for managing Windows Update client policies through Microsoft Graph API, such as enrolling into reports
 - [Azure](/azure/role-based-access-control/overview): Used for controlling access to Azure resources through Azure Resource Management, such as access to the Log Analytics workspace
 - [Microsoft 365 admin center](/microsoft-365/admin/add-users/about-admin-roles): Manages access to the Microsoft 365 admin center, which allows only users with certain Microsoft Entra roles access to sign in
 

windows/deployment/update/release-cycle.md

@@ -101,7 +101,7 @@ Starting with Windows 11, version 22H2, new features and enhancements are introd
 Some of the new features may be disruptive to organizations. By default, these select features are turned off temporarily for all managed devices until the next annual feature update is installed. In this scenario, a device is considered managed if it uses one of the following to determine which updates to install:
 
 - Windows Update client policies
-  - Devices that have updates managed Microsoft Intune use Windows Update client policies
+  - Devices that have updates managed by Microsoft Intune use Windows Update client policies
 - WSUS
   - Devices that have updates managed by Configuration Manager use WSUS
 

windows/deployment/update/update-other-microsoft-products.md

@@ -1,7 +1,6 @@
 ---
 title: Update other Microsoft products
-titleSuffix: Windows Update client policies
-description: List of other Microsoft products that are updated when install updates for other Microsoft products (allowmuupdateservice) is used.
+description: List of other Microsoft products that are updated when install updates for other Microsoft products (AllowMUUpdateService) is used.
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: reference

windows/deployment/update/waas-configure-wufb.md

@@ -20,18 +20,18 @@ ms.date: 02/27/2024
 ---
 
 # Configure Windows Update client policies
-<a name="configure-windows-update-for-business"></a>
 
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/windows/windows-update-faq-8a903416-6f45-0718-f5c7-375e92dddeb2).
+
+You can use Group Policy or your mobile device management (MDM) service to configure Windows Update client policies for your devices. The sections in this article provide the Group Policy and MDM policies for Windows 10, version 1511 and later, including Windows 11. The MDM policies use the OMA-URI setting from the [Policy CSP](/windows/client-management/mdm/policy-configuration-service-provider).
 
 > [!NOTE]
 > Windows Server _doesn't_ get feature updates from Windows Update, so only the quality update policies apply. This behavior doesn't apply to [Azure Stack hyperconverged infrastructure (HCI)](/azure-stack/hci/).
 
-You can use Group Policy or your mobile device management (MDM) service to configure Windows Update client policies for your devices. The sections in this article provide the Group Policy and MDM policies for Windows 10, version 1511 and later, including Windows 11. The MDM policies use the OMA-URI setting from the [Policy CSP](/windows/client-management/mdm/policy-configuration-service-provider).
-
-> [!IMPORTANT]
-> Beginning with Windows 10, version 1903, organizations can use Windows Update client policies, regardless of the diagnostic data level chosen. If the diagnostic data level is set to **0 (Security)**, Windows Update client policies will still be honored. For instructions, see [Configure the operating system diagnostic data level](/windows/configuration/configure-windows-diagnostic-data-in-your-organization#diagnostic-data-levels).
+You can use Windows Update client policies regardless of the diagnostic data level that you chose. If the diagnostic data level is set to **0 (Security)**, Windows Update client policies are still honored. For more information, see [Configure the operating system diagnostic data level](/windows/configuration/configure-windows-diagnostic-data-in-your-organization#diagnostic-data-levels).
 
+> [!TIP]
+> This feature was formerly known as _Windows Update for Business_.
 
 ## Start by grouping devices
 
@@ -188,7 +188,7 @@ Starting with Windows 10, version 1709, you can set policies to manage preview b
 The **Manage preview builds** setting gives administrators control over enabling or disabling preview build installation on a device. You can also decide to stop preview builds once the release is public.
 * Group Policy: **Computer Configuration/Administrative Templates/Windows Components/Windows Update/Windows Update for Business** - *Manage preview builds*
 * MDM: **Update/ManagePreviewBuilds**
-* Microsoft Configuration Manager: **Enable dual scan, manage through Windows Update client policies**
+* Microsoft Configuration Manager: **Enable dual scan, manage through Windows Update for Business policy**
 
 >[!IMPORTANT]
 >This policy replaces the "Toggle user control over Insider builds" policy under that is only supported up to Windows 10, version 1703. You can find the older policy here:

windows/deployment/update/waas-integrate-wufb.md

@@ -16,10 +16,13 @@ ms.date: 02/27/2024
 
 # Integrate Windows Update client policies with management solutions
 
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq) 
+> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/windows/windows-update-faq-8a903416-6f45-0718-f5c7-375e92dddeb2).
 
 You can integrate Windows Update client policy deployments with existing management tools such as Windows Server Update Services (WSUS) and Microsoft Configuration Manager.
 
+> [!TIP]
+> This feature was formerly known as _Windows Update for Business_.
+
 ## Integrate Windows Update client policies with Windows Server Update Services
 <a name="integrate-windows-update-for-business-with-windows-server-update-services"></a>
 
@@ -95,5 +98,4 @@ For Windows 10, version 1607, organizations already managing their systems with
 
 :::image type="content" alt-text="Example of unknown devices." source="images/wufb-sccm.png" lightbox="images/wufb-sccm.png":::
 
-For more information, see [Integration with Windows Update client policies in Windows 10](/mem/configmgr/sum/deploy-use/integrate-windows-update-for-business-windows-10).
-
+For more information, see [Integration with Windows Update client policies](/mem/configmgr/sum/deploy-use/integrate-windows-update-for-business-windows-10).

windows/deployment/update/waas-manage-updates-wufb.md

@@ -19,7 +19,7 @@ ms.date: 05/16/2024
 
 # What are Windows Update client policies?
 
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/windows/windows-update-faq-8a903416-6f45-0718-f5c7-375e92dddeb2).
 
 Windows Update client policies are a free service that is available for the following editions of Windows 10 and Windows 11:
 
@@ -29,6 +29,9 @@ Windows Update client policies are a free service that is available for the foll
 
 Windows Update client policies enable IT administrators to keep their organization's Windows client devices always up to date with the latest security updates  and Windows features by directly connecting these systems to the Windows Update service. You can use Group Policy or Mobile Device Management (MDM) solutions, such as Microsoft Intune, to configure the Windows Update client policies that control how and when devices are updated.
 
+> [!TIP]
+> This feature was formerly known as _Windows Update for Business_.
+
 Specifically, Windows Update client policies let you control update offerings and experiences to allow for reliability and performance testing on a subset of devices before deploying updates across the organization. It also provides a positive update experience for people in your organization.
 
 ## What can I do with Windows Update client policies?

windows/deployment/update/waas-wufb-csp-mdm.md

@@ -16,13 +16,15 @@ ms.date: 03/18/2025
 
 # Walkthrough: Use CSPs and MDMs to configure Windows Update client policies
 
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq) 
-
+> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/windows/windows-update-faq-8a903416-6f45-0718-f5c7-375e92dddeb2).
 
 ## Overview
 
 You can use Configuration Service Provider (CSP) policies to control how Windows Update client policies work by using a Mobile Device Management (MDM) tool. You should consider and devise a deployment strategy for updates before you make changes to the Windows Update client policies.
 
+> [!TIP]
+> This feature was formerly known as _Windows Update for Business_.
+
 An IT administrator can configure Windows Update client policies by using Microsoft Intune or a non-Microsoft MDM tool.
 
 To manage updates with Windows Update client policies, you should prepare with these steps, if you haven't already:
@@ -59,7 +61,7 @@ Drivers are automatically enabled because they're beneficial to device systems.
 
 #### I want to manage which released feature update my devices receive
 
-A Windows Update client policies administrator can defer or pause updates. You can defer feature updates for up to 365 days and defer quality updates for up to 30 days. Deferring simply means that you don't receive the update until it has been released for at least the number of deferral days you specified (offer date = release date + deferral date). You can pause feature or quality updates for up to 35 days from a given start date that you specify.
+A Windows Update administrator can defer or pause updates. You can defer feature updates for up to 365 days and defer quality updates for up to 30 days. Deferring simply means that you don't receive the update until it has been released for at least the number of deferral days you specified (offer date = release date + deferral date). You can pause feature or quality updates for up to 35 days from a given start date that you specify.
 
 - To defer a feature update: [Update/DeferFeatureUpdatesPeriodInDays](/windows/client-management/mdm/policy-csp-update#deferfeatureupdatesperiodindays)
 - To pause a feature update: [Update/PauseFeatureUpdatesStartTime](/windows/client-management/mdm/policy-csp-update#pausefeatureupdatesstarttime)

windows/deployment/update/waas-wufb-group-policy.md

@@ -22,7 +22,7 @@ ms.date: 03/18/2025
 
 # Walkthrough: Use Group Policy to configure Windows Update client policies
 
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/windows/windows-update-faq-8a903416-6f45-0718-f5c7-375e92dddeb2).
 
 ## Overview
 
@@ -30,6 +30,9 @@ You can use Group Policy through the Group Policy Management Console (GPMC) to c
 
 An IT administrator can configure Windows Update client policies by using Group Policy, or they can be set locally (per device). All of the relevant policies are under the path **Computer configuration > Administrative Templates > Windows Components > Windows Update**.
 
+> [!TIP]
+> This feature was formerly known as _Windows Update for Business_.
+
 To manage updates with Windows Update client policies as described in this article, you should prepare with these steps, if you haven't already:
 
 - Create Active Directory security groups that align with the deployment rings you use to phase deployment of updates.
@@ -86,7 +89,7 @@ Drivers are automatically enabled because they're beneficial to device systems.
 
 #### I want to manage which released feature update my devices receive
 
-A Windows Update client policies administrator can defer or pause updates. You can defer feature updates for up to 365 days and defer quality updates for up to 30 days. Deferring simply means that you won't receive the update until it has been released for at least the number of deferral days you specified (offer date = release date + deferral date). You can pause feature or quality updates for up to 35 days from a given start date that you specify.
+A Windows Update administrator can defer or pause updates. You can defer feature updates for up to 365 days and defer quality updates for up to 30 days. Deferring simply means that you won't receive the update until it has been released for at least the number of deferral days you specified (offer date = release date + deferral date). You can pause feature or quality updates for up to 35 days from a given start date that you specify.
 
 - To defer or pause a feature update: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview Builds and feature updates are Received**
 - Defer or pause a quality update: **Computer configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Quality Updates are Received**

windows/deployment/update/wufb-compliancedeadlines.md

@@ -1,6 +1,5 @@
 ---
 title: Enforce compliance deadlines with policies
-titleSuffix: Windows Update client policies
 description: This article contains information on how to enforce compliance deadlines using Windows Update client policies.
 ms.service: windows-client
 ms.subservice: itpro-updates

windows/deployment/update/wufb-reports-faq.yml

@@ -16,14 +16,14 @@ summary: |
 
   **General questions**:
 
-  - [What is Windows Update for Business reports?](#what-is-Windows Update for Business reports)
-  - [Is Windows Update for Business reports free?](#is-Windows Update for Business reports-free)
+  - [What are Windows Update for Business reports?](#what-are-windows-update-for-business-reports)
+  - [Are Windows Update for Business reports free?](#are-windows-update-for-business-reports-free)
   - [What Windows versions are supported?](#what-windows-versions-are-supported)
 
   **Setup questions**:
 
-  - [How do you set up Windows Update for Business reports?](#how-do-you-set-up-Windows Update for Business reports)
-  - [Why is "Waiting for Windows Update for Business reports data" displayed on the page](#why-is--waiting-for-Windows Update for Business reports-data--displayed-on-the-page)
+  - [How do you set up Windows Update for Business reports?](#how-do-you-set-up-windows-update-for-business-reports)
+  - [Why is "Waiting for Windows Update for Business reports data" displayed on the page](#why-is--waiting-for-windows-update-for-business-reports-data--displayed-on-the-page)
   - [Why am I getting the error "400 Bad Request: The specified resource already exists"?](#why-am-i-getting-the-error--400-bad-request--the-specified-resource-already-exists-)
 
   **Questions about using Windows Update for Business reports**:
@@ -54,10 +54,10 @@ summary: |
 sections:
   - name: General
     questions:
-      - question: What is Windows Update for Business reports?
+      - question: What are Windows Update for Business reports?
         answer: |
           Windows Update for Business reports is a cloud-based solution that provides information about your Microsoft Entra joined devices' compliance with Windows updates. Windows Update for Business reports is offered through the [Azure portal](https://portal.azure.com), and it's included as part of the Windows 10 or Windows 11 prerequisite licenses.
-      - question: Is Windows Update for Business reports free?
+      - question: Are Windows Update for Business reports free?
         answer: |
           Data ingested into your Log Analytics workspace can be retained at no charge for up to first 31 days (or 90 days if [Microsoft Sentinel](/azure/sentinel/overview) is enabled on the workspace). Data ingested into [Application Insights](/azure/azure-monitor/app/app-insights-overview), either classic or workspace-based, is retained for 90 days without any charge.
           Data retained beyond these no-charge periods are charged for each GB of data retained for a month, pro-rated daily. For more information, see **Log Data Retention** in [Azure Monitor pricing](https://azure.microsoft.com/en-us/pricing/details/monitor/#pricing).
@@ -147,7 +147,7 @@ sections:
             - **OSQualityUpdateStatus**: Indicates the status of the monthly update that's released on the fourth Tuesday
       - question: How do I confirm that devices are sending data?
         answer: |
-          Once enrollment is done and devices are properly configured to share data, wait for 48 hours for data to start showing up in reports. It can take up to 14 days for all of your devices to show up in reports in some cases where devices aren't active much. You can check to see if the Log Analytics tables are being populated in your workspace. The data is ingested by the service daily to generate reports. If you notice a day is missing, it's possible that the reports service missed an ingestion. To confirm devices are sending data, [query](wufb-reports-use.md#display-Windows Update for Business reports-data) the [UCClient table](wufb-reports-schema-ucclient.md). The following query shows total enrolled device count per time-generated: 
+          Once enrollment is done and devices are properly configured to share data, wait for 48 hours for data to start showing up in reports. It can take up to 14 days for all of your devices to show up in reports in some cases where devices aren't active much. You can check to see if the Log Analytics tables are being populated in your workspace. The data is ingested by the service daily to generate reports. If you notice a day is missing, it's possible that the reports service missed an ingestion. To confirm devices are sending data, [query](wufb-reports-use.md#display-windows-update-for-business-reports-data) the [UCClient table](wufb-reports-schema-ucclient.md). The following query shows total enrolled device count per time-generated:
 
           `UCClient | summarize count() by TimeGenerated`
 

windows/deployment/update/wufb-reports-overview.md

@@ -59,7 +59,7 @@ You'll set up Windows Update for Business reports by enrolling into the service
 
 - Update deployment progress
 - Delivery Optimization usage data
-- Windows Update client policies configuration data
+- Windows Update client policy configuration data
 
 The Azure Log Analytics ingestion and retention charges aren't incurred on your Azure subscription for Windows Update for Business reports data. You also choose an [Azure Log Analytics workspaces](/azure/azure-monitor/logs/log-analytics-overview) that you own for your client diagnostic data. The collected diagnostic data populates the Windows Update for Business reports tables so you can easily query your data.
 

windows/deployment/update/wufb-wsus.md

@@ -16,7 +16,7 @@ ms.date: 04/22/2024
 
 # Use Windows Update client policies and WSUS together
 
-> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
+> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/windows/windows-update-faq-8a903416-6f45-0718-f5c7-375e92dddeb2).
 
 The Windows update scan source policy enables you to choose what types of updates to get from either [WSUS](waas-manage-updates-wsus.md) or Windows Update client policies.
 

windows/deployment/windows-autopatch/prepare/windows-autopatch-configure-network.md

@@ -34,7 +34,7 @@ There are URLs from several Microsoft products that must be in the allowed list
 | ----- | ----- |
 | Microsoft Entra ID | [Hybrid identity required ports and protocols](/azure/active-directory/hybrid/reference-connect-ports)<p><p>[Active Directory and Active Directory Domain Services Port Requirements](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd772723(v=ws.10))</p> |
 | Microsoft Intune | [Intune network configuration requirements](/mem/intune/fundamentals/network-bandwidth-use)<p><p>[Network endpoints for Microsoft Intune](/mem/intune/fundamentals/intune-endpoints)</p> |
-| Windows Update client policies | [Windows Update client policies firewall and proxy requirements](https://support.microsoft.com/help/3084568/can-t-download-updates-from-windows-update-from-behind-a-firewall-or-p) |
+| Windows Update client policies | [Windows Update client policies firewall and proxy requirements](/troubleshoot/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting#device-cant-access-update-files) |
 
 #### [Windows Enterprise E3+ and F3](#tab/windows-enterprise-e3-and-f3-licenses-required-microsoft-endpoints)
 

windows/whats-new/temporary-enterprise-feature-control.md

@@ -44,7 +44,7 @@ You can use a policy to enable features that are behind temporary enterprise fea
 - **Group Policy:** Computer Configuration\Administrative Templates\Windows Components\Windows Update\Manage end user experience\\**Enable features introduced via servicing that are off by default**
 
 - **CSP**: ./Device/Vendor/MSFT/Policy/Config/Update/[AllowTemporaryEnterpriseFeatureControl](/windows/client-management/mdm/policy-csp-update?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#allowtemporaryenterprisefeaturecontrol)
-   - In the Intune [settings catalog](/mem/intune/configuration/settings-catalog), this setting is named **Allow Temporary Enterprise Feature Control** under the **Windows Update client policies** category.
+   - In the Intune [settings catalog](/mem/intune/configuration/settings-catalog), this setting is named **Allow Temporary Enterprise Feature Control** under the **Windows Update for Business** category.
 
 ### Windows 11 features behind temporary enterprise feature control