mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge branch 'main' into patch-14
This commit is contained in:
Meghan Stewart
GitHub
commit
02649103d2
@ -2,13 +2,19 @@
|
||||
|
||||
|
||||
|
||||
## Week of December 11, 2023
|
||||
## Week of January 15, 2024
|
||||
|
||||
|
||||
| Published On |Topic title | Change |
|
||||
|------|------------|--------|
|
||||
| 12/12/2023 | Chromebook migration guide | removed |
|
||||
| 12/12/2023 | Deploy Windows 10 in a school district | removed |
|
||||
| 12/12/2023 | Deploy Windows 10 in a school | removed |
|
||||
| 12/12/2023 | Windows 10 for Education | removed |
|
||||
| 12/12/2023 | [Reset devices with Autopilot Reset](/education/windows/autopilot-reset) | modified |
|
||||
| 1/16/2024 | Deployment recommendations for school IT administrators | removed |
|
||||
| 1/16/2024 | Microsoft Entra join with Set up School PCs app | removed |
|
||||
| 1/16/2024 | [Set up School PCs app technical reference overview](/education/windows/set-up-school-pcs-technical) | modified |
|
||||
| 1/16/2024 | Set up student PCs to join domain | removed |
|
||||
| 1/16/2024 | Provision student PCs with apps | removed |
|
||||
| 1/16/2024 | Set up Windows devices for education | removed |
|
||||
| 1/16/2024 | [Configure applications with Microsoft Intune](/education/windows/tutorial-school-deployment/configure-device-apps) | modified |
|
||||
| 1/16/2024 | [Configure and secure devices with Microsoft Intune](/education/windows/tutorial-school-deployment/configure-device-settings) | modified |
|
||||
| 1/16/2024 | [Configure devices with Microsoft Intune](/education/windows/tutorial-school-deployment/configure-devices-overview) | modified |
|
||||
| 1/16/2024 | [Set up Microsoft Entra ID](/education/windows/tutorial-school-deployment/set-up-microsoft-entra-id) | modified |
|
||||
| 1/16/2024 | Windows 10 editions for education customers | removed |
|
||||
|
||||
@ -3,7 +3,7 @@ title: Manage Copilot in Windows
|
||||
description: Learn how to manage Copilot in Windows for commercial environments using MDM and group policy. Learn about the chat providers available to Copilot in Windows.
|
||||
ms.topic: conceptual
|
||||
ms.subservice: windows-copilot
|
||||
ms.date: 11/06/2023
|
||||
ms.date: 01/22/2024
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
appliesto:
|
||||
@ -12,9 +12,10 @@ appliesto:
|
||||
|
||||
# Manage Copilot in Windows
|
||||
<!--8445848-->
|
||||
|
||||
>**Looking for consumer information?** See [Welcome to Copilot in Windows](https://support.microsoft.com/windows/welcome-to-copilot-in-windows-675708af-8c16-4675-afeb-85a5a476ccb0).
|
||||
|
||||
Copilot in Windows provides centralized generative AI assistance to your users right from the Windows desktop. Copilot in Windows appears as a side bar docked on the Windows desktop. It's designed to help your users get things done in Windows. Copilot in Windows can perform common tasks in Windows like changing Windows settings, which makes it different from the browser-based [Copilot in Edge](/bing-chat-enterprise/edge). However, both user experiences, Copilot in Windows and Copilot in Edge, can share the same underlying chat provider platform. It's important for organizations to properly configure the chat provider platform that Copilot in Windows uses, since it is possible for users to copy and paste sensitive information into the chat provider.
|
||||
Copilot in Windows provides centralized generative AI assistance to your users right from the Windows desktop. Copilot in Windows appears as a side bar docked on the Windows desktop and is designed to help users get things done in Windows. Copilot in Windows can perform common tasks in Windows like changing Windows settings, which makes it different from the browser-based [Copilot in Edge](/copilot/edge). However, both user experiences, Copilot in Windows and Copilot in Edge, can share the same underlying chat provider platform. It's important for organizations to properly configure the chat provider platform that Copilot in Windows uses, since it's possible for users to copy and paste sensitive information into the chat.
|
||||
|
||||
> [!Note]
|
||||
> - Copilot in Windows is currently available as a preview. We will continue to experiment with new ideas and methods using your feedback.
|
||||
@ -39,62 +40,63 @@ Organizations that aren't ready to use Copilot in Windows can disable it until t
|
||||
|
||||
## Chat provider platforms for Copilot in Windows
|
||||
|
||||
Copilot in Windows can use either Bing Chat or Bing Chat Enterprise as its chat provider platform. The chat provider platform is the underlying service that Copilot in Windows uses to communicate with the user. The chat provider platform that Copilot in Windows uses is important because it is possible for users to copy and paste sensitive information into the chat provider. Each chat provider platform has different privacy and security protections.
|
||||
Copilot in Windows can use either Microsoft Copilot or Copilot with commercial data protection as its chat provider platform. The chat provider platform is the underlying service that Copilot in Windows uses to communicate with the user. The chat provider platform is important because it's possible for users to copy and paste sensitive information into the chat. Each chat provider platform has different privacy and security protections.
|
||||
|
||||
**Bing Chat**:
|
||||
### Copilot
|
||||
|
||||
[Bing Chat](https://www.microsoft.com/bing/do-more-with-ai/what-is-bing-chat-and-how-can-you-use-it) is a consumer experience and if a user isn't signed in with their Microsoft account, the number of chat queries per user has a daily limit. Bing Chat doesn't offer the same commercial data protection as Bing Chat Enterprise does. The following privacy and security protections apply for Bing Chat:
|
||||
- [Copilot in Windows: Your data and privacy](https://support.microsoft.com/windows/3e265e82-fc76-4d0a-afc0-4a0de528b73a)
|
||||
- The privacy statement for using Bing Chat follows the [Microsoft privacy statement](https://privacy.microsoft.com/privacystatement) including the product specific guidance in the Microsoft privacy statement for **Bing** under the **Search, Microsoft Edge, and artificial intelligence** section.
|
||||
Copilot is a consumer experience and has a daily limit on the number of chat queries per user when not signed in with a Microsoft account. It doesn't offer the same data protection as Copilot with commercial data protection.
|
||||
|
||||
- [Copilot in Windows: Your data and privacy](https://support.microsoft.com/windows/3e265e82-fc76-4d0a-afc0-4a0de528b73a)
|
||||
- The privacy statement for using Copilot follows the [Microsoft privacy statement](https://privacy.microsoft.com/privacystatement) including the product specific guidance in the Microsoft privacy statement for **Bing** under the **Search, Microsoft Edge, and artificial intelligence** section.
|
||||
|
||||
|
||||
**Bing Chat Enterprise**:
|
||||
### Copilot with commercial data protection
|
||||
|
||||
[Bing Chat Enterprise](/bing-chat-enterprise/overview) is intended for commercial use scenarios and offers commercial data protection. The following privacy and security protections apply for Bing Chat Enterprise:
|
||||
[Copilot with commercial data protection](/copilot/overview) is intended for commercial use scenarios and offers commercial data protection. The following privacy and security protections apply for Copilot with commercial data protection:
|
||||
|
||||
- With [Bing Chat Enterprise](/bing-chat-enterprise/overview), user and organizational data is protected, chat data isn't saved, and your data isn't used to train the underlying large language models. Because of this protection, chat history, 3rd-party plugins, and the Bing mobile app for iOS or Android aren't currently supported. Bing Chat Enterprise is accessible from mobile browsers, including Edge mobile on iOS and Android. Review the Bing Chat Enterprise [privacy statement](/bing-chat-enterprise/privacy-and-protections).
|
||||
- Bing Chat Enterprise is available, at no additional cost, for the following licenses:
|
||||
- User and organizational data is protected, chat data isn't saved, and your data isn't used to train the underlying large language models. Because of this protection, chat history, 3rd-party plugins, and the Bing app for iOS or Android aren't currently supported. Copilot with commercial data protection is accessible from mobile browsers, including Edge mobile on iOS and Android. Review the Copilot with commercial data protection [privacy statement](/copilot/privacy-and-protections).
|
||||
- Copilot with commercial data protection is available, at no additional cost, for the following licenses:
|
||||
- Microsoft 365 E3 or E5
|
||||
- Microsoft 365 A3 or A5 for faculty
|
||||
- Microsoft 365 Business Standard
|
||||
- Microsoft 365 Business Premium
|
||||
|
||||
> [!Note]
|
||||
> Bing Chat Enterprise and Bing Chat don't have access to Microsoft Graph, unlike [Microsoft 365 Copilot](/microsoft-365-copilot/microsoft-365-copilot-overview) which can be used in the Microsoft 365 apps. This means that Bing Chat Enterprise and Bing Chat can't access Microsoft 365 Apps data, such as email, calendar, or files.
|
||||
> Copilot doesn't have access to Microsoft 365 Apps data, such as email, calendar, or files using Microsoft Graph, unlike [Copilot for Microsoft 365](/microsoft-365-copilot/microsoft-365-copilot-overview) which can be used in the Microsoft 365 apps.
|
||||
|
||||
## Configure the chat provider platform that Copilot in Windows uses
|
||||
|
||||
Configuring the correct chat provider platform for Copilot in Windows is important because it is possible for users to copy and paste sensitive information into the chat provider. Each chat provider platform has different privacy and security protections. Once you have selected the chat provider platform that you want to use for Copilot in Windows, ensure it's configured for your organization's users. The following sections describe how to configure the chat provider platform that Copilot in Windows uses.
|
||||
Configuring the correct chat provider platform for Copilot in Windows is important because it's possible for users to copy and paste sensitive information into the chat. Each chat provider platform has different privacy and security protections. Once you select the chat provider platform that you want to use for Copilot in Windows, ensure it's configured for your organization's users. The following sections describe how to configure the chat provider platform that Copilot in Windows uses.
|
||||
|
||||
### Bing Chat as the chat provider platform
|
||||
### Microsoft Copilot as the chat provider platform
|
||||
|
||||
Bing Chat is used as the default chat provider platform for Copilot in Windows when any of the following conditions occur:
|
||||
Copilot is used as the default chat provider platform for Copilot in Windows when any of the following conditions occur:
|
||||
|
||||
- Bing Chat Enterprise isn't configured for the user
|
||||
- The user isn't assigned a license that includes Bing Chat Enterprise
|
||||
- Bing Chat Enterprise is [turned off](/bing-chat-enterprise/manage)
|
||||
- The user isn't signed in with a Microsoft Entra account that's licensed for Bing Chat Enterprise
|
||||
- Commercial data protection isn't configured for the user.
|
||||
- Commercial data protection is [turned off](/copilot/manage).
|
||||
- The user isn't assigned a license that includes Copilot with commercial data protection.
|
||||
- The user isn't signed in with a Microsoft Entra account that's licensed for Copilot with commercial data protection.
|
||||
|
||||
### Bing Chat Enterprise as the chat provider platform (recommended for commercial environments)
|
||||
### Copilot with commercial data protection as the chat provider platform (recommended for commercial environments)
|
||||
|
||||
To verify that Bing Chat Enterprise is enabled for the user as the chat provider platform for Copilot in Windows, use the following instructions:
|
||||
To verify that Copilot with commercial data protection is enabled for the user as the chat provider platform for Copilot in Windows, use the following instructions:
|
||||
|
||||
1. Sign into the [Microsoft 365 admin center](https://admin.microsoft.com/).
|
||||
1. In the admin center, select **Users** > **Active users** and verify that users are assigned a license that includes Bing Chat Enterprise. Bing Chat Enterprise is included and enabled by default for users that are assigned one of the following licenses:
|
||||
1. In the admin center, select **Users** > **Active users** and verify that users are assigned a license that includes **Copilot**. Copilot with commercial data protection is included and enabled by default for users that are assigned one of the following licenses:
|
||||
- Microsoft 365 E3 or E5
|
||||
- Microsoft 365 A3 or A5 for faculty
|
||||
- Currently, Microsoft 365 A3 and A5 for faculty requires additional configuration. For more information, see [Manage Bing Chat Enterprise](/bing-chat-enterprise/manage).
|
||||
- Currently, Microsoft 365 A3 and A5 for faculty requires additional configuration. For more information, see [Manage Copilot](/copilot/manage).
|
||||
- Microsoft 365 Business Standard
|
||||
- Microsoft 365 Business Premium
|
||||
1. To verify that Bing Chat Enterprise is enabled for the user, select the user's **Display name** to open the flyout menu.
|
||||
1. To verify that commercial data protection is enabled for the user, select the user's **Display name** to open the flyout menu.
|
||||
1. In the flyout, select the **Licenses & apps** tab, then expand the **Apps** list.
|
||||
1. Verify that **Bing Chat Enterprise** is enabled for the user.
|
||||
1. If you prefer to view a user's licenses from the [Azure portal](https://portal.azure.com), you will find it under **Microsoft Entra ID** > **Users**. Select the user's name, then **Licenses**. Select a license that includes Bing Chat Enterprise, and verify that it's listed as **On**.
|
||||
1. Verify that **Copilot** is enabled for the user.
|
||||
1. If you prefer to view a user's licenses from the [Azure portal](https://portal.azure.com), you'll find it under **Microsoft Entra ID** > **Users**. Select the user's name, then **Licenses**. Select a license that includes **Copilot**, and verify that it's listed as **On**.
|
||||
|
||||
> [!Note]
|
||||
> If you previously disabled Bing Chat Enterprise using the URL, `https://aka.ms/TurnOffBCE`, see [Manage Bing Chat Enterprise](/bing-chat-enterprise/manage) for verifying that Bing Chat Enterprise is enabled for your users.
|
||||
> If you previously disabled Copilot with commercial data protection (formerly Bing Chat Enterprise) using the URL, `https://aka.ms/TurnOffBCE`, see [Manage Copilot](/copilot/manage) for verifying that commercial data protection is enabled for your users.
|
||||
|
||||
The following sample PowerShell script connects to Microsoft Graph and lists which users that have Bing Chat Enterprise enabled and disabled:
|
||||
The following sample PowerShell script connects to Microsoft Graph and lists which users that have Copilot with commercial data protection enabled and disabled:
|
||||
|
||||
```powershell
|
||||
# Install Microsoft Graph module
|
||||
@ -108,16 +110,16 @@ Connect-MgGraph -Scopes 'User.Read.All'
|
||||
# Get all users
|
||||
$users = Get-MgUser -All -ConsistencyLevel eventual -Property Id, DisplayName, Mail, UserPrincipalName, AssignedPlans
|
||||
|
||||
# Users with Bing Chat Enterprise enabled
|
||||
# Users with Copilot with commercial data protection enabled
|
||||
$users | Where-Object { $_.AssignedPlans -and $_.AssignedPlans.Service -eq "Bing" -and $_.AssignedPlans.CapabilityStatus -eq "Enabled" } | Format-Table
|
||||
|
||||
# Users without Bing Chat Enterprise enabled
|
||||
# Users without Copilot with commercial data protection enabled
|
||||
$users | Where-Object { -not $_.AssignedPlans -or ($_.AssignedPlans.Service -eq "Bing" -and $_.AssignedPlans.CapabilityStatus -ne "Enabled") } | Format-Table
|
||||
```
|
||||
|
||||
When Bing Chat Enterprise is the chat provider platform, the user experience clearly states that **Your personal and company data are protected in this chat**. There's also a shield symbol labeled **Protected** at the top of the Copilot in Windows sidebar and the provider is listed under the Copilot logo when the sidebar is first opened. The following image shows the message that's displayed when Bing Chat Enterprise is the chat provider platform for Copilot in Windows:
|
||||
When Copilot with commercial data protection is the chat provider platform, the user experience clearly states that **Your personal and company data are protected in this chat**. There's also a shield symbol labeled **Protected** at the top of the Copilot in Windows sidebar and the provider is listed under the Copilot logo when the sidebar is first opened. The following image shows the message that's displayed in this scenario:
|
||||
|
||||
:::image type="content" source="images/bing-chat-enterprise-chat-provider.png" alt-text="Screenshot of the Copilot in Windows user experience when Bing Chat Enterprise is the chat provider." lightbox="images/bing-chat-enterprise-chat-provider.png":::
|
||||
:::image type="content" source="images/bing-chat-enterprise-chat-provider.png" alt-text="Screenshot of the Copilot in Windows user experience when Copilot with commercial data protection is the chat provider." lightbox="images/bing-chat-enterprise-chat-provider.png":::
|
||||
|
||||
## Ensure the Copilot in Windows user experience is enabled
|
||||
|
||||
@ -130,7 +132,7 @@ Copilot in Windows isn't technically enabled by default for managed Windows 11,
|
||||
To enable Copilot in Windows for managed Windows 11, version 22H2 devices, you need to enable features under temporary enterprise control for these devices. Since enabling features behind [temporary enterprise control](/windows/whats-new/temporary-enterprise-feature-control) can be impactful, you should test this change before deploying it broadly. To enable Copilot in Windows for managed Windows 11, version 22H2 devices, use the following instructions:
|
||||
|
||||
1. Verify that the user accounts have the correct chat provider platform configured for Copilot in Windows. For more information, see the [Configure the chat provider platform that Copilot in Windows uses](#configure-the-chat-provider-platform-that-copilot-in-windows-uses) section.
|
||||
1. Apply a policy to enable features under temporary enterprise control for managed clients. The following polices apply to Windows 11, version 22H2 with [KB5022845](https://support.microsoft.com/en-us/topic/february-14-2023-kb5022845-os-build-22621-1265-90a807f4-d2e8-486e-8a43-d09e66319f38) and later:
|
||||
1. Apply a policy to enable features under temporary enterprise control for managed clients. The following polices apply to Windows 11, version 22H2 with [KB5022845](https://support.microsoft.com/topic/february-14-2023-kb5022845-os-build-22621-1265-90a807f4-d2e8-486e-8a43-d09e66319f38) and later:
|
||||
- **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)
|
||||
@ -152,9 +154,9 @@ To enable Copilot in Windows for managed Windows 11, version 22H2 devices, you n
|
||||
|
||||
### Enable the Copilot in Windows user experience for Windows 11, version 23H2 clients
|
||||
|
||||
Once a managed device installs the version 23H2 update, the [temporary enterprise control](/windows/whats-new/temporary-enterprise-feature-control) for Copilot in Windows will be removed. This means that Copilot in Windows will be enabled by default for these devices.
|
||||
Once a managed device installs the version 23H2 update, the [temporary enterprise control](/windows/whats-new/temporary-enterprise-feature-control) for Copilot in Windows is removed. This means that Copilot in Windows is enabled by default for these devices.
|
||||
|
||||
While the user experience for Copilot in Windows is enabled by default, you still need to verify that the correct chat provider platform configured for Copilot in Windows. While every effort has been made to ensure that Bing Chat Enterprise is the default chat provider for commercial organizations, it's still possible that Bing Chat might still be used if the configuration is incorrect, or if other settings are affecting Copilot in Windows. For more information, see:
|
||||
While the user experience for Copilot in Windows is enabled by default, you still need to verify that the correct chat provider platform configured for Copilot in Windows. While every effort is made to ensure that Copilot with commercial data protection is the default chat provider for commercial organizations, it's still possible that Copilot might still be used if the configuration is incorrect, or if other settings are affecting Copilot in Windows. For more information, see:
|
||||
- [Configure the chat provider platform that Copilot in Windows uses](#configure-the-chat-provider-platform-that-copilot-in-windows-uses)
|
||||
- [Other settings that might affect Copilot in Windows and its underlying chat provider](#other-settings-that-might-affect-copilot-in-windows-and-its-underlying-chat-provider)
|
||||
|
||||
@ -165,25 +167,26 @@ Organizations that aren't ready to use Copilot in Windows can disable it until t
|
||||
|
||||
## Other settings that might affect Copilot in Windows and its underlying chat provider
|
||||
|
||||
Copilot in Windows and [Copilot in Edge](/bing-chat-enterprise/edge), can share the same underlying chat provider platform. This also means that some settings that affect Bing Chat, Bing Chat Enterprise, and Copilot in Edge can also affect Copilot in Windows. The following common settings might affect Copilot in Windows and its underlying chat provider:
|
||||
Copilot in Windows and [Copilot in Edge](/copilot/edge), can share the same underlying chat provider platform. This also means that some settings that affect Copilot, Copilot with commercial data protection, and Copilot in Edge can also affect Copilot in Windows. The following common settings might affect Copilot in Windows and its underlying chat provider:
|
||||
|
||||
### Bing settings
|
||||
|
||||
- If [SafeSearch](https://support.microsoft.com/topic/946059ed-992b-46a0-944a-28e8fb8f1814) is enabled for Bing, it can block chat providers for Copilot in Windows. The following network changes block the chat providers for Copilot in Windows and Copilot in Edge:
|
||||
- mapping `www.bing.com` to `strict.bing.com`
|
||||
- mapping `edgeservices.bing.com` to `strict.bing.com`
|
||||
- blocking `bing.com`
|
||||
- If [SafeSearch](https://support.microsoft.com/topic/946059ed-992b-46a0-944a-28e8fb8f1814) is enabled for Bing, it can block chat providers for Copilot in Windows. The following network changes block the chat providers for Copilot in Windows and Edge:
|
||||
|
||||
- If Bing Chat Enterprise is turned on for your organization, users will be able to access it through Edge mobile when signed in with their work account. If you would like to remove the Bing Chat button from the Edge mobile interface, you can use an [Intune Mobile Application Management (MAM) policy for Microsoft Edge](/mem/intune/apps/manage-microsoft-edge) to remove it:
|
||||
- Mapping `www.bing.com` to `strict.bing.com`
|
||||
- Mapping `edgeservices.bing.com` to `strict.bing.com`
|
||||
- Blocking `bing.com`
|
||||
|
||||
|Key |Value |
|
||||
|:---------|:------------|
|
||||
|com.microsoft.intune.mam.managedbrowser.Chat| **true** (default) shows the interface </br> **false** hides the interface |
|
||||
- If Copilot with commercial data protection is turned on for your organization, users can access it through Edge mobile when signed in with their work account. If you would like to remove the Bing Chat button from the Edge mobile interface, you can use an [Intune Mobile Application Management (MAM) policy for Microsoft Edge](/mem/intune/apps/manage-microsoft-edge) to remove it:
|
||||
|
||||
| Key | Value |
|
||||
|:---------------------------------------------|:---------------------------------------------------------------------------|
|
||||
| com.microsoft.intune.mam.managedbrowser.Chat | **true** (default) shows the interface </br> **false** hides the interface |
|
||||
|
||||
### Microsoft Edge policies
|
||||
|
||||
- If [HubsSidebarEnabled](/deployedge/microsoft-edge-policies#hubssidebarenabled) is set to `disabled`, it blocks Copilot in Edge from being displayed.
|
||||
- If [DiscoverPageContextEnabled](/deployedge/microsoft-edge-policies#discoverpagecontextenabled) is set to `disabled`, it blocks Bing Chat and Bing Chat Enterprise from reading the current webpage context. The chat providers need access to the current webpage context for providing page summarizations and sending user selected strings from the webpage into the chat provider.
|
||||
- If [DiscoverPageContextEnabled](/deployedge/microsoft-edge-policies#discoverpagecontextenabled) is set to `disabled`, it blocks Copilot from reading the current webpage context. The chat providers need access to the current webpage context for providing page summarizations and sending user selected strings from the webpage into the chat provider.
|
||||
|
||||
### Search settings
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows quality updates overview with Autopatch groups experience
|
||||
description: This article explains how Windows quality updates are managed with Autopatch groups
|
||||
ms.date: 08/23/2023
|
||||
ms.date: 01/22/2024
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -34,11 +34,82 @@ For devices in the [Default Autopatch group](../deploy/windows-autopatch-groups-
|
||||
|
||||
## Service level objective
|
||||
|
||||
Windows Autopatch aims to keep at least 95% of eligible devices on the latest Windows quality update 21 days after release. Devices that have cadence type set to Schedule install aren't eligible for Windows quality update SLO. For more information about the Schedule Install cadence type, see [Deployment cadence types](../operate/windows-autopatch-groups-windows-update.md#deployment-cadence).
|
||||
Windows Autopatch aims to keep at least 95% of [Up to Date devices](../operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md#up-to-date-devices) on the latest quality update. Autopatch uses the previously defined release schedule on a per ring basis with a five-day reporting period to calculate and evaluate the service level objective (SLO). The result of the service level objective is the column “% with the latest quality update” displayed in release management and reporting.
|
||||
|
||||
### Service level objective calculation
|
||||
|
||||
There are two states a device can be in when calculating the service level objective (SLO):
|
||||
|
||||
- Devices that are active during the release
|
||||
- Devices that become active after the release
|
||||
|
||||
The service level objective for each of these states is calculated as:
|
||||
|
||||
| State | Calculation |
|
||||
| ----- | ----- |
|
||||
| Device that is active during release | This service level objective calculation assumes the device has typical activity during the scheduled release period.<p>Calculated by:</p>`Deferral + Deadline + Reporting Period = service level objective` |
|
||||
| Device that becomes active after release | This service level objective calculation refers to offline devices during the scheduled release period but come back online later.<p>`Calculated by:</p>Grace Period + Reporting period = service level objective` |
|
||||
|
||||
| Timeframe | Value defined in |
|
||||
| ----- | ----- |
|
||||
| Deferral | Targeted deployment ring |
|
||||
| Deadline | Targeted deployment ring |
|
||||
| Grace period | Targeted deployment ring |
|
||||
| Reporting period | Five days. Value defined by Windows Autopatch. |
|
||||
|
||||
> [!NOTE]
|
||||
> Targeted deployment ring refers to the deployment ring value of the device in question. If a device has a five day deferral with a two day deadline, and two day grace period, the SLO for the device would be calculated to `5 + 2 + 5 = 12`-day service level objective from the second Tuesday of the month. The five day reporting period is one established by Windows Autopatch to allow enough time for device check-in reporting and data evaluation within the service.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Windows Autopatch supports registering [Windows 10 Long-Term Servicing Channel (LTSC)](/windows/whats-new/ltsc/) devices that are being currently serviced by the [Windows LTSC](/windows/release-health/release-information). The service only supports managing the [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) workload for devices currently serviced by the LTSC. Windows Update for Business service and Windows Autopatch don't offer Windows feature updates for devices that are part of the LTSC. You must either use [LTSC media](https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise) or the [Configuration Manager Operating System Deployment capabilities to perform an in-place upgrade](/windows/deployment/deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager) for Windows devices that are part of the LTSC.
|
||||
|
||||
## Import Update rings for Windows 10 and later (public preview)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> This feature is in **public preview**. It's being actively developed, and might not be complete.
|
||||
|
||||
You can import your organization’s existing Intune Update rings for Windows 10 and later into Windows Autopatch. Importing your organization’s Update rings provides the benefits of the Windows Autopatch's reporting and device readiness without the need to redeploy, or change your organization’s existing update rings.
|
||||
|
||||
Imported rings automatically register all targeted devices into Windows Autopatch. For more information about device registration, see the [device registration workflow diagram](../deploy/windows-autopatch-device-registration-overview.md#detailed-device-registration-workflow-diagram).
|
||||
|
||||
> [!NOTE]
|
||||
> Devices which are registered as part of an imported ring, might take up to 72 hours after the devices have received the latest version of the policy, to be reflected in Windows Autopatch devices blade and reporting. For more information about reporting, see [Windows quality and feature update reports overview](../operate/windows-autopatch-groups-windows-quality-and-feature-update-reports-overview.md).
|
||||
|
||||
> [!NOTE]
|
||||
> Device registration failures don't affect your existing update schedule or targeting. However, devices that fail to register might affect Windows Autopatch’s ability to provide reporting and insights. Any conflicts should be resolved as needed. For additional assistance, [submit a support request](../operate/windows-autopatch-support-request.md).
|
||||
|
||||
### Import Update rings for Windows 10 and later
|
||||
|
||||
**To import Update rings for Windows 10 and later:**
|
||||
|
||||
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
2. Select **Devices** from the left navigation menu.
|
||||
3. Under the **Windows Autopatch** section, select **Release management**.
|
||||
4. In the **Release management** blade, go to the **Release schedule** tab and select **Windows quality updates**.
|
||||
5. Select **Import Update rings for Windows 10 and later**.
|
||||
6. Select the existing rings you would like to import.
|
||||
7. Select **Import**.
|
||||
|
||||
### Remove an imported Update ring for Windows 10 and later
|
||||
|
||||
**To remove an Imported Update rings for Windows 10 and later:**
|
||||
|
||||
1. Go to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
2. Select **Devices** from the left navigation menu.
|
||||
3. Under the **Windows Autopatch** section, select **Release management**.
|
||||
4. In the **Release management** blade, go to the **Release schedule** tab and select **Windows quality updates**.
|
||||
5. Select the Update rings for Windows 10 and later you would like to remove.
|
||||
6. Select the **horizontal ellipses (...)** and select **Remove**.
|
||||
|
||||
### Known limitations
|
||||
|
||||
The following Windows Autopatch features aren't available with imported Intune Update rings:
|
||||
|
||||
- Autopatch groups and features dependent on Autopatch groups
|
||||
- Moving devices in between deployment rings in devices
|
||||
- Automated deployment ring remediation functions
|
||||
- Policy health and remediation
|
||||
|
||||
## Release management
|
||||
|
||||
> [!NOTE]
|
||||
@ -54,14 +125,14 @@ In the Release management blade, you can:
|
||||
|
||||
For each [deployment ring](windows-autopatch-update-management.md#windows-autopatch-deployment-rings), the **Release schedule** tab contains:
|
||||
|
||||
- The status of the update. Releases appear as **Active**. The update schedule is based on the values of the [Windows 10 Update Ring policies](/mem/intune/protect/windows-update-for-business-configure), which have been configured on your behalf.
|
||||
- The status of the update. Releases appear as **Active**. The update schedule is based on the values of the [Windows 10 Update Ring policies](/mem/intune/protect/windows-update-for-business-configure), which are configured on your behalf.
|
||||
- The date the update is available.
|
||||
- The target completion date of the update.
|
||||
- In the **Release schedule** tab, you can either [**Pause** and/or **Resume**](#pause-and-resume-a-release) a Windows quality update release.
|
||||
|
||||
### Expedited releases
|
||||
|
||||
Threat and vulnerability information about a new revision of Windows becomes available on the second Tuesday of each month. Windows Autopatch assesses that information shortly afterwards. If the service determines that it's critical to security, it may be expedited. The quality update is also evaluated on an ongoing basis throughout the release and Windows Autopatch may choose to expedite at any time during the release.
|
||||
Threat and vulnerability information about a new revision of Windows becomes available on the second Tuesday of each month. Windows Autopatch assesses that information shortly afterwards. If the service determines that it's critical to security, it might be expedited. The quality update is also evaluated on an ongoing basis throughout the release and Windows Autopatch might choose to expedite at any time during the release.
|
||||
|
||||
When expediting a release, the regular goal of 95% of devices in 21 days no longer applies. Instead, Windows Autopatch greatly accelerates the release schedule of the release to update the environment more quickly. This approach requires an updated schedule for all devices outside of the Test ring since those devices are already getting the update quickly.
|
||||
|
||||
@ -104,7 +175,7 @@ For the deployment rings that have passed quality updates deferral date, the OOB
|
||||
|
||||
The service-level pause is driven by the various software update deployment-related signals Windows Autopatch receives from Windows Update for Business, and several other product groups within Microsoft.
|
||||
|
||||
If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-groups-windows-quality-update-signals.md), we may decide to pause that release.
|
||||
If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-groups-windows-quality-update-signals.md), we might decide to pause that release.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Pausing or resuming an update can take up to eight hours to be applied to devices. Windows Autopatch uses Microsoft Intune as its device management solution and that's the average frequency Windows devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.<p>For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).</p>
|
||||
@ -125,8 +196,8 @@ The three following statuses are associated with paused quality updates:
|
||||
|
||||
| Status | Description |
|
||||
| ----- | ------ |
|
||||
| Paused by Service | If the Windows Autopatch service has paused an update, the release has the **Paused by Service** status. The Paused by Service only applies to rings that aren't Paused by the Tenant. |
|
||||
| Paused by Tenant | If you've paused an update, the release has the **Paused by Tenant** status. The Windows Autopatch service can't overwrite a tenant pause. You must select **Resume** to resume the update. |
|
||||
| Paused by Service | If the Windows Autopatch service paused an update, the release has the **Paused by Service** status. The **Paused by Service** status only applies to rings that aren't Paused by the Tenant. |
|
||||
| Paused by Tenant | If you paused an update, the release has the **Paused by Tenant** status. The Windows Autopatch service can't overwrite a tenant pause. You must select **Resume** to resume the update. |
|
||||
|
||||
## Remediating Not ready and/or Not up to Date devices
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2024
|
||||
description: This article lists the 2024 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 01/18/2024
|
||||
ms.date: 01/22/2024
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: whats-new
|
||||
@ -27,6 +27,8 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
|
||||
| Article | Description |
|
||||
| ----- | ----- |
|
||||
| [Windows quality updates overview](../operate/windows-autopatch-groups-windows-quality-update-overview.md) | Added [Import Update rings for Windows 10 and later](../operate/windows-autopatch-groups-windows-quality-update-overview.md#import-update-rings-for-windows-10-and-later-public-preview) |
|
||||
| [Windows quality updates overview](../operate/windows-autopatch-groups-windows-quality-update-overview.md#service-level-objective) | Updated the Service level objective, added the Service level objective calculation. |
|
||||
| [Prerequisites](../prepare/windows-autopatch-prerequisites.md#more-about-licenses) | Added more E3 and E5 licenses to the [More about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses) section. |
|
||||
|
||||
## January service releases
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user