From 505c4e24b68c501e95ad1b4c4adebaaeaa1312b8 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 16 Nov 2022 15:11:30 -0500 Subject: [PATCH 01/36] MSGraph POST sample --- education/windows/edu-stickers.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index dc25c4e817..cb2e43478e 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -41,6 +41,12 @@ Stickers aren't enabled by default. Follow the instructions below to configure y [!INCLUDE [intune-custom-settings-2](includes/intune-custom-settings-2.md)] [!INCLUDE [intune-custom-settings-info](includes/intune-custom-settings-info.md)] +Alternatively, try using the following MSGraph call to automatically create the custom policy in your tenant: + +```msgraph-interactive +POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations/{"id":"00-0000-0000-0000-000000000000","displayName":"Stickers","roleScopeTagIds":["0"],"@odata.type":"#microsoft.graph.windows10CustomConfiguration","omaSettings":[{"omaUri":"./Vendor/MSFT/Policy/Config/Stickers/EnableStickers","displayName":"EnableStickers","@odata.type":"#microsoft.graph.omaSettingInteger","value":1}]} +``` + #### [:::image type="icon" source="images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg) To configure devices using a provisioning package, [create a provisioning package][WIN-1] using Windows Configuration Designer (WCD) with the following settings: From 81323d8fc891865f0d0615db0c48594388babcbb Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 16 Nov 2022 17:23:39 -0500 Subject: [PATCH 02/36] updates --- education/windows/edu-stickers.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index cb2e43478e..7333c0734e 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -41,7 +41,8 @@ Stickers aren't enabled by default. Follow the instructions below to configure y [!INCLUDE [intune-custom-settings-2](includes/intune-custom-settings-2.md)] [!INCLUDE [intune-custom-settings-info](includes/intune-custom-settings-info.md)] -Alternatively, try using the following MSGraph call to automatically create the custom policy in your tenant: +> [!TIP] +> Try using the following MSGraph call to automatically create the custom policy in your tenant. ```msgraph-interactive POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations/{"id":"00-0000-0000-0000-000000000000","displayName":"Stickers","roleScopeTagIds":["0"],"@odata.type":"#microsoft.graph.windows10CustomConfiguration","omaSettings":[{"omaUri":"./Vendor/MSFT/Policy/Config/Stickers/EnableStickers","displayName":"EnableStickers","@odata.type":"#microsoft.graph.omaSettingInteger","value":1}]} From c53ab899b4aa177dbe2a8f746d30e11b3b370813 Mon Sep 17 00:00:00 2001 From: mounicabattula <95552440+mounicabattula@users.noreply.github.com> Date: Mon, 5 Dec 2022 11:36:23 -0800 Subject: [PATCH 03/36] New feature - QU expedite Opt-out --- .../windows-autopatch/operate/windows-autopatch-wqu-overview.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index f2d4f477af..2f6a60536a 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -58,6 +58,8 @@ Threat and vulnerability information about a new revision of Windows becomes ava When running an expedited 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 as quickly. +Windows Autopatch provides the option to opt out of service driven quality updates expedite. To opt out of service driven expedite, customers can go to Release Management blade under Windows Autopatch section under Tenant Administration on [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431). On the release management blade, the Expedited Quality Updates setting on the Release Settings tab can be used to change the expedite behavior. + | Release type | Group | Deferral | Deadline | Grace period | | ----- | ----- | ----- | ----- | ----- | | Standard release | Test

First

Fast

Broad | 0

1

6

9 | 0

2

2

5 | 0

2

2

2 | From c36337077f3f41c11fdcaea2e61e097e225af14f Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 5 Dec 2022 11:58:58 -0800 Subject: [PATCH 04/36] Update windows-autopatch-wqu-overview.md Made tweaks. --- .../operate/windows-autopatch-wqu-overview.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index 2f6a60536a..e00180267b 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -58,7 +58,9 @@ Threat and vulnerability information about a new revision of Windows becomes ava When running an expedited 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 as quickly. -Windows Autopatch provides the option to opt out of service driven quality updates expedite. To opt out of service driven expedite, customers can go to Release Management blade under Windows Autopatch section under Tenant Administration on [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431). On the release management blade, the Expedited Quality Updates setting on the Release Settings tab can be used to change the expedite behavior. +### Opt out of expedited releases + +Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the [Microsoft Endpoint Manager portal]((https://go.microsoft.com/fwlink/?linkid=2109431) > Tenant administration > Windows Autopatch > **Release management** blade. In the Release management blade, under the **Release Settings** tab, turn off the **Expedited Quality Updates** setting. | Release type | Group | Deferral | Deadline | Grace period | | ----- | ----- | ----- | ----- | ----- | From f4e6063f6d1d7f4c236792f513b2fb484a8aaa1a Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 5 Dec 2022 12:02:46 -0800 Subject: [PATCH 05/36] Update windows-autopatch-wqu-overview.md --- .../windows-autopatch/operate/windows-autopatch-wqu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index e00180267b..63ac721337 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -60,7 +60,7 @@ When running an expedited release, the regular goal of 95% of devices in 21 days ### Opt out of expedited releases -Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the [Microsoft Endpoint Manager portal]((https://go.microsoft.com/fwlink/?linkid=2109431) > Tenant administration > Windows Autopatch > **Release management** blade. In the Release management blade, under the **Release Settings** tab, turn off the **Expedited Quality Updates** setting. +Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the [Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431) > Tenant administration > Windows Autopatch > **Release management** blade. In the Release management blade, under the **Release Settings** tab, turn off the **Expedited Quality Updates** setting. | Release type | Group | Deferral | Deadline | Grace period | | ----- | ----- | ----- | ----- | ----- | From 06ae6b451cf97c8a16d68fe73c59cb3fbc7ba728 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 5 Dec 2022 12:04:21 -0800 Subject: [PATCH 06/36] Update windows-autopatch-wqu-overview.md --- .../windows-autopatch/operate/windows-autopatch-wqu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index 63ac721337..a97be2ea9d 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -60,7 +60,7 @@ When running an expedited release, the regular goal of 95% of devices in 21 days ### Opt out of expedited releases -Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the [Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431) > Tenant administration > Windows Autopatch > **Release management** blade. In the Release management blade, under the **Release Settings** tab, turn off the **Expedited Quality Updates** setting. +Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the [Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431) > **Tenant administration** > **Windows Autopatch** > **Release management** blade. In the **Release management** blade, under the **Release Settings** tab, turn off the **Expedited Quality Updates** setting. | Release type | Group | Deferral | Deadline | Grace period | | ----- | ----- | ----- | ----- | ----- | From 5d11db7d9899d8db9e13693ff245f1297efe0192 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 5 Dec 2022 12:04:59 -0800 Subject: [PATCH 07/36] Update windows-autopatch-wqu-overview.md --- .../windows-autopatch/operate/windows-autopatch-wqu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index a97be2ea9d..12c0848bd6 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -60,7 +60,7 @@ When running an expedited release, the regular goal of 95% of devices in 21 days ### Opt out of expedited releases -Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the [Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431) > **Tenant administration** > **Windows Autopatch** > **Release management** blade. In the **Release management** blade, under the **Release Settings** tab, turn off the **Expedited Quality Updates** setting. +Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Tenant administration** > **Windows Autopatch** > **Release management** blade. In the **Release management** blade, under the **Release Settings** tab, turn off the **Expedited Quality Updates** setting. | Release type | Group | Deferral | Deadline | Grace period | | ----- | ----- | ----- | ----- | ----- | From 3aea5659931ed4f38b2753530865b1936dc134a6 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Mon, 5 Dec 2022 15:20:44 -0500 Subject: [PATCH 08/36] POST update --- education/windows/edu-stickers.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index 7333c0734e..fb0966ddb8 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -45,7 +45,9 @@ Stickers aren't enabled by default. Follow the instructions below to configure y > Try using the following MSGraph call to automatically create the custom policy in your tenant. ```msgraph-interactive -POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations/{"id":"00-0000-0000-0000-000000000000","displayName":"Stickers","roleScopeTagIds":["0"],"@odata.type":"#microsoft.graph.windows10CustomConfiguration","omaSettings":[{"omaUri":"./Vendor/MSFT/Policy/Config/Stickers/EnableStickers","displayName":"EnableStickers","@odata.type":"#microsoft.graph.omaSettingInteger","value":1}]} +POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations/ +Content-Type: application/json +{"id":"00-0000-0000-0000-000000000000","displayName":"Stickers","roleScopeTagIds":["0"],"@odata.type":"#microsoft.graph.windows10CustomConfiguration","omaSettings":[{"omaUri":"./Vendor/MSFT/Policy/Config/Stickers/EnableStickers","displayName":"EnableStickers","@odata.type":"#microsoft.graph.omaSettingInteger","value":1}]} ``` #### [:::image type="icon" source="images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg) From b847c85753f44c999a360e5f615db146796eee25 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Mon, 5 Dec 2022 15:39:47 -0500 Subject: [PATCH 09/36] updates --- education/windows/edu-stickers.md | 1 - 1 file changed, 1 deletion(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index fb0966ddb8..4a9a9f8f88 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -46,7 +46,6 @@ Stickers aren't enabled by default. Follow the instructions below to configure y ```msgraph-interactive POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations/ -Content-Type: application/json {"id":"00-0000-0000-0000-000000000000","displayName":"Stickers","roleScopeTagIds":["0"],"@odata.type":"#microsoft.graph.windows10CustomConfiguration","omaSettings":[{"omaUri":"./Vendor/MSFT/Policy/Config/Stickers/EnableStickers","displayName":"EnableStickers","@odata.type":"#microsoft.graph.omaSettingInteger","value":1}]} ``` From 01b468801eecf60831121405c4f9d6a0d5a05bc3 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Mon, 5 Dec 2022 15:44:40 -0500 Subject: [PATCH 10/36] update --- education/windows/edu-stickers.md | 1 + 1 file changed, 1 insertion(+) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index 4a9a9f8f88..42361dcf63 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -46,6 +46,7 @@ Stickers aren't enabled by default. Follow the instructions below to configure y ```msgraph-interactive POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations/ + {"id":"00-0000-0000-0000-000000000000","displayName":"Stickers","roleScopeTagIds":["0"],"@odata.type":"#microsoft.graph.windows10CustomConfiguration","omaSettings":[{"omaUri":"./Vendor/MSFT/Policy/Config/Stickers/EnableStickers","displayName":"EnableStickers","@odata.type":"#microsoft.graph.omaSettingInteger","value":1}]} ``` From de4119d48afbb95e9031c8e49114af2ca4ea5400 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Mon, 5 Dec 2022 15:49:49 -0500 Subject: [PATCH 11/36] update --- education/windows/edu-stickers.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index 42361dcf63..1900c9e886 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -45,7 +45,8 @@ Stickers aren't enabled by default. Follow the instructions below to configure y > Try using the following MSGraph call to automatically create the custom policy in your tenant. ```msgraph-interactive -POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations/ +POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations +Content-Type: application/json {"id":"00-0000-0000-0000-000000000000","displayName":"Stickers","roleScopeTagIds":["0"],"@odata.type":"#microsoft.graph.windows10CustomConfiguration","omaSettings":[{"omaUri":"./Vendor/MSFT/Policy/Config/Stickers/EnableStickers","displayName":"EnableStickers","@odata.type":"#microsoft.graph.omaSettingInteger","value":1}]} ``` From d5fff060bef67f2d81ef413f9ad6ff27ce5d0bed Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Mon, 5 Dec 2022 16:16:46 -0500 Subject: [PATCH 12/36] updates --- education/windows/edu-stickers.md | 4 ++-- education/windows/includes/intune-custom-settings-1.md | 3 --- 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index 1900c9e886..bc9af08637 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -42,13 +42,13 @@ Stickers aren't enabled by default. Follow the instructions below to configure y [!INCLUDE [intune-custom-settings-info](includes/intune-custom-settings-info.md)] > [!TIP] -> Try using the following MSGraph call to automatically create the custom policy in your tenant. +> Use the following Graph call to automatically create the custom policy in your tenant without assignments nor scope tags. ```msgraph-interactive POST https://graph.microsoft.com/beta/deviceManagement/deviceConfigurations Content-Type: application/json -{"id":"00-0000-0000-0000-000000000000","displayName":"Stickers","roleScopeTagIds":["0"],"@odata.type":"#microsoft.graph.windows10CustomConfiguration","omaSettings":[{"omaUri":"./Vendor/MSFT/Policy/Config/Stickers/EnableStickers","displayName":"EnableStickers","@odata.type":"#microsoft.graph.omaSettingInteger","value":1}]} +{"id":"00-0000-0000-0000-000000000000","displayName":"_MSLearn_Stickers","roleScopeTagIds":["0"],"@odata.type":"#microsoft.graph.windows10CustomConfiguration","omaSettings":[{"omaUri":"./Vendor/MSFT/Policy/Config/Stickers/EnableStickers","displayName":"EnableStickers","@odata.type":"#microsoft.graph.omaSettingInteger","value":1}]} ``` #### [:::image type="icon" source="images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg) diff --git a/education/windows/includes/intune-custom-settings-1.md b/education/windows/includes/intune-custom-settings-1.md index fa7811c9eb..a8d82dfea6 100644 --- a/education/windows/includes/intune-custom-settings-1.md +++ b/education/windows/includes/intune-custom-settings-1.md @@ -7,9 +7,6 @@ ms.topic: include To configure devices with Microsoft Intune, use a custom policy: - > [!TIP] - > If you're browsing with an account that can create Intune policies, you can skip to step 5 by using this direct link to create a custom policy (opens in a new tab). - 1. Go to the Microsoft Endpoint Manager admin center 2. Select **Devices > Configuration profiles > Create profile** 3. Select **Platform > Windows 10 and later** and **Profile type > Templates > Custom** From e34eb5f22dabafcaf55e61acf2e60f9ac5d53535 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 7 Dec 2022 09:27:33 -0500 Subject: [PATCH 13/36] updates --- education/windows/edu-stickers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index bc9af08637..ab2424149b 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -14,7 +14,7 @@ ms.collection: Starting in **Windows 11 SE, version 22H2**, *Stickers* is a new feature that allows students to decorate their desktop with digital stickers. Students can choose from over 500 cheerful, education-friendly digital stickers. Stickers can be arranged, resized, and customized on top of the desktop background. Each student's stickers remain, even when the background changes. -Similar to the [education theme packs](edu-themes.md), Stickers is a personalization feature that helps the device feel like it was designed for students. +Similar to the [education theme packs](edu-themes.md "my tooltip example that opens in a new tab"), Stickers is a personalization feature that helps the device feel like it was designed for students. :::image type="content" source="./images/win-11-se-stickers.png" alt-text="Windows 11 SE desktop with 3 stickers" border="true"::: From b0e8186cff540420a39bb52bd017444f8de03903 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 7 Dec 2022 09:49:07 -0500 Subject: [PATCH 14/36] update --- education/windows/edu-stickers.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index ab2424149b..669a9de79f 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -10,6 +10,15 @@ ms.collection: - education --- +This document describes Windows Hello for Business functionalities or scenarios that apply to:\ +✅ **Deployment type:** [hybrid ℹ️]("The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ +✅ **Trust type:** [key trust](../identity-protection/hello-for-business/hello-how-it-works-technology.md#key-trust)\ +✅ **Device registration type:** [Azure AD join](../identity-protection/hello-for-business/hello-how-it-works-technology.md#azure-active-directory-join), [Hybrid Azure AD join](../identity-protection/hello-for-business/hello-how-it-works-technology.md#hybrid-azure-ad-join) + +
+ +--- + # Configure Stickers for Windows 11 SE Starting in **Windows 11 SE, version 22H2**, *Stickers* is a new feature that allows students to decorate their desktop with digital stickers. Students can choose from over 500 cheerful, education-friendly digital stickers. Stickers can be arranged, resized, and customized on top of the desktop background. Each student's stickers remain, even when the background changes. From 18cc9f63ead87fcfd871ab1c28269f837d08fe33 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 7 Dec 2022 09:53:02 -0500 Subject: [PATCH 15/36] update --- education/windows/edu-stickers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index 669a9de79f..84888e61ff 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -11,9 +11,9 @@ ms.collection: --- This document describes Windows Hello for Business functionalities or scenarios that apply to:\ -✅ **Deployment type:** [hybrid ℹ️]("The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ -✅ **Trust type:** [key trust](../identity-protection/hello-for-business/hello-how-it-works-technology.md#key-trust)\ -✅ **Device registration type:** [Azure AD join](../identity-protection/hello-for-business/hello-how-it-works-technology.md#azure-active-directory-join), [Hybrid Azure AD join](../identity-protection/hello-for-business/hello-how-it-works-technology.md#hybrid-azure-ad-join) +✅ **Deployment type:** [hybrid 🗒️](http://bing.com "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ +✅ **Trust type:** [key trust 🗒️](http://bing.com "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ +✅ **Device registration type:** [Azure AD join 🗒️](http://bing.com "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")
From 03f5d62f014aef33c5ed629e31a918965d8470b6 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 7 Dec 2022 10:04:30 -0500 Subject: [PATCH 16/36] updates --- education/windows/edu-stickers.md | 6 +++--- education/windows/images/icons/information.svg | 13 +++++++++++++ 2 files changed, 16 insertions(+), 3 deletions(-) create mode 100644 education/windows/images/icons/information.svg diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index 84888e61ff..d0ae8f399b 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -11,9 +11,9 @@ ms.collection: --- This document describes Windows Hello for Business functionalities or scenarios that apply to:\ -✅ **Deployment type:** [hybrid 🗒️](http://bing.com "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ -✅ **Trust type:** [key trust 🗒️](http://bing.com "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ -✅ **Device registration type:** [Azure AD join 🗒️](http://bing.com "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") +✅ **Deployment type:** [:::image type="icon" source="images/icons/information.svg"::: hybrid](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ +✅ **Trust type:** [:::image type="icon" source="images/icons/information.svg"::: key trust](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ +✅ **Device registration type:** [:::image type="icon" source="images/icons/information.svg"::: Azure AD join](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")
diff --git a/education/windows/images/icons/information.svg b/education/windows/images/icons/information.svg new file mode 100644 index 0000000000..761a946709 --- /dev/null +++ b/education/windows/images/icons/information.svg @@ -0,0 +1,13 @@ + + + + + + + + + + Icon-general-5 + + + \ No newline at end of file From ac6eeee567c37c9b85e204934b0ef41a46584832 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 7 Dec 2022 10:09:26 -0500 Subject: [PATCH 17/36] updates --- education/windows/edu-stickers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index d0ae8f399b..65af26e386 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -11,9 +11,9 @@ ms.collection: --- This document describes Windows Hello for Business functionalities or scenarios that apply to:\ -✅ **Deployment type:** [:::image type="icon" source="images/icons/information.svg"::: hybrid](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ -✅ **Trust type:** [:::image type="icon" source="images/icons/information.svg"::: key trust](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ -✅ **Device registration type:** [:::image type="icon" source="images/icons/information.svg"::: Azure AD join](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") +✅ **Deployment type:** hybrid [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ +✅ **Trust type:** key trust [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ +✅ **Device registration type:** Azure AD join [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")
From 9c7b9499c1ba9fb843234bda9ca4913179bf38d1 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 7 Dec 2022 10:13:21 -0500 Subject: [PATCH 18/36] updates --- education/windows/edu-stickers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index 65af26e386..cba9a74a65 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -11,9 +11,9 @@ ms.collection: --- This document describes Windows Hello for Business functionalities or scenarios that apply to:\ -✅ **Deployment type:** hybrid [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ -✅ **Trust type:** key trust [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ -✅ **Device registration type:** Azure AD join [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") +- **Deployment type:** hybrid [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ +- **Trust type:** key trust [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ +- **Device registration type:** Azure AD join [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")
From cb1853c9d0fc6886a2c59b52a13dadcb10fe46a8 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 7 Dec 2022 10:26:30 -0500 Subject: [PATCH 19/36] updates --- education/windows/edu-stickers.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index cba9a74a65..ce16e09aaa 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -10,10 +10,10 @@ ms.collection: - education --- -This document describes Windows Hello for Business functionalities or scenarios that apply to:\ -- **Deployment type:** hybrid [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ -- **Trust type:** key trust [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")\ -- **Device registration type:** Azure AD join [:::image type="icon" source="images/icons/information.svg":::](. "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") +This document describes Windows Hello for Business functionalities or scenarios that apply to: +- **Deployment type:** hybrid [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#hybrid-deployment "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") +- **Trust type:** key trust [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#key-trust "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") +- **Device registration type:** Azure AD join [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#azure-active-directory-join), [Hybrid Azure AD join](../identity-protection/hello-for-business/hello-how-it-works-technology.md#hybrid-azure-ad-join "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")
From ad25351f9f135d026319157ac0e7bcf6b6f1cfa3 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 7 Dec 2022 10:31:37 -0500 Subject: [PATCH 20/36] updates --- education/windows/edu-stickers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index ce16e09aaa..edfef3467b 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -13,7 +13,7 @@ ms.collection: This document describes Windows Hello for Business functionalities or scenarios that apply to: - **Deployment type:** hybrid [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#hybrid-deployment "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") - **Trust type:** key trust [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#key-trust "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") -- **Device registration type:** Azure AD join [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#azure-active-directory-join), [Hybrid Azure AD join](../identity-protection/hello-for-business/hello-how-it-works-technology.md#hybrid-azure-ad-join "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") +- **Device registration type:** Azure AD join [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#azure-active-directory-join "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust."), Hybrid Azure AD join [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#hybrid-azure-ad-join "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.")
From 3f0b549164f74976d411f1372916f680b5d50cb7 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 7 Dec 2022 10:39:38 -0500 Subject: [PATCH 21/36] updates --- education/windows/edu-stickers.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/education/windows/edu-stickers.md b/education/windows/edu-stickers.md index edfef3467b..ab2424149b 100644 --- a/education/windows/edu-stickers.md +++ b/education/windows/edu-stickers.md @@ -10,15 +10,6 @@ ms.collection: - education --- -This document describes Windows Hello for Business functionalities or scenarios that apply to: -- **Deployment type:** hybrid [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#hybrid-deployment "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") -- **Trust type:** key trust [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#key-trust "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") -- **Device registration type:** Azure AD join [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#azure-active-directory-join "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust."), Hybrid Azure AD join [:::image type="icon" source="images/icons/information.svg":::](../identity-protection/hello-for-business/hello-how-it-works-technology.md#hybrid-azure-ad-join "The Windows Hello for Business hybrid deployment is for organizations that have both on-premises and cloud resources that are accessed using a managed or federated identity that's synchronized with Azure AD. Hybrid deployments support devices that are Azure AD-registered, Azure AD-joined, and hybrid Azure AD-joined. The Hybrid deployment model supports three trust types for on-premises authentication: cloud Kerberos trust, key trust and certificate trust.") - -
- ---- - # Configure Stickers for Windows 11 SE Starting in **Windows 11 SE, version 22H2**, *Stickers* is a new feature that allows students to decorate their desktop with digital stickers. Students can choose from over 500 cheerful, education-friendly digital stickers. Stickers can be arranged, resized, and customized on top of the desktop background. Each student's stickers remain, even when the background changes. From 4107e0d024bac744b043c1988f8fee2491db969b Mon Sep 17 00:00:00 2001 From: Sarah Barrett Date: Thu, 8 Dec 2022 15:48:52 -0800 Subject: [PATCH 22/36] Turn off extendBreadcrumbs --- browsers/edge/docfx.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/browsers/edge/docfx.json b/browsers/edge/docfx.json index d786e0bbfb..d36533a87e 100644 --- a/browsers/edge/docfx.json +++ b/browsers/edge/docfx.json @@ -28,7 +28,7 @@ ], "globalMetadata": { "recommendations": true, - "breadcrumb_path": "/microsoft-edge/deploy/breadcrumb/toc.json", + "breadcrumb_path": "/microsoft-edge/breadcrumbs/toc.json", "ROBOTS": "INDEX, FOLLOW", "ms.technology": "microsoft-edge", "audience": "ITPro", From 929a0c56335be262a1565024000d86ee5a0c5c43 Mon Sep 17 00:00:00 2001 From: Sarah Barrett Date: Thu, 8 Dec 2022 15:52:12 -0800 Subject: [PATCH 23/36] Update breadcrumb --- browsers/edge/breadcrumb/toc.yml | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/browsers/edge/breadcrumb/toc.yml b/browsers/edge/breadcrumb/toc.yml index f417737985..83065b36a9 100644 --- a/browsers/edge/breadcrumb/toc.yml +++ b/browsers/edge/breadcrumb/toc.yml @@ -1,7 +1,3 @@ -- name: Docs - tocHref: / - topicHref: / - items: - - name: Microsoft Edge deployment - tocHref: /microsoft-edge/deploy - topicHref: /microsoft-edge/deploy/index \ No newline at end of file +- name: Microsoft Edge + tocHref: /microsoft-edge/ + topicHref: /microsoft-edge/index From c7332c5ac07c781313137999ade1a959ebe45c86 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Fri, 9 Dec 2022 13:31:54 -0800 Subject: [PATCH 24/36] Update windows-autopatch-wqu-overview.md --- .../windows-autopatch/operate/windows-autopatch-wqu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index 12c0848bd6..b834b4c886 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -60,7 +60,7 @@ When running an expedited release, the regular goal of 95% of devices in 21 days ### Opt out of expedited releases -Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Tenant administration** > **Windows Autopatch** > **Release management** blade. In the **Release management** blade, under the **Release Settings** tab, turn off the **Expedited Quality Updates** setting. +Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Tenant administration** > **Windows Autopatch** > **Release management** blade. In the **Release management** blade, under the **Release settings** tab, turn off the **Expedited Quality Updates** setting. | Release type | Group | Deferral | Deadline | Grace period | | ----- | ----- | ----- | ----- | ----- | From 33df09e23ef3072982c26897ca907c202fa580ec Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Fri, 9 Dec 2022 14:21:19 -0800 Subject: [PATCH 25/36] Update windows-autopatch-wqu-overview.md --- .../windows-autopatch/operate/windows-autopatch-wqu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index b834b4c886..2e1935639e 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -76,7 +76,7 @@ If Windows Autopatch detects a [significant issue with a release](../operate/win If we pause the release, a policy will be deployed which prevents devices from updating while the issue is investigated. Once the issue is resolved, the release will be resumed. -You can pause or resume a Windows quality update from the Release management tab in the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431). +You can pause or resume a Windows quality update from the **Release management** tab in the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431). ## Incidents and outages From f45f3082a84807015c31f10ef82140f3681ca4bf Mon Sep 17 00:00:00 2001 From: mounicabattula <95552440+mounicabattula@users.noreply.github.com> Date: Fri, 9 Dec 2022 14:28:31 -0800 Subject: [PATCH 26/36] Update windows-autopatch-wqu-overview.md Added changes for OOB --- .../operate/windows-autopatch-wqu-overview.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index 2e1935639e..6854aa174f 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -70,6 +70,12 @@ Windows Autopatch provides the option to opt out of service-driven expedited qua > [!NOTE] > Windows Autopatch doesn't allow customers to request expedited releases. +## Out of Band release + +Windows Autopatch schedules and deploys required Out of Band (OOB) updates released outside of the normal schedule. Customers can view the deployed OOB quality updates on the **Release Management** blade on the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)**. + +To view deployed OOB quality updates, customers can go to the Endpoint Manager admin center > Tenant administration > Windows Autopatch > Release management pane. Under the Release Announcements tab, customers can view the knowledge base (KB) articles corresponding to the deployed OOB quality updates. In case of a normal quality update release, KBs for the specific release will be available to the customers to view in the Release Announcements tab. Note that the announcements will be removed from the Release announcements tab when the next quality update is released. Further, if quality updates are paused for a ring, the OOB updates will also be paused. + ## Pausing and resuming a release If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-wqu-signals.md), we may decide to pause that release. From 16de507861983d6dbbe460f3a91dc7a82a8378bf Mon Sep 17 00:00:00 2001 From: mounicabattula <95552440+mounicabattula@users.noreply.github.com> Date: Fri, 9 Dec 2022 14:30:39 -0800 Subject: [PATCH 27/36] Adding Section for OOB Adding section for OOB --- .../windows-autopatch/operate/windows-autopatch-wqu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index 6854aa174f..d63d67b12a 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -74,7 +74,7 @@ Windows Autopatch provides the option to opt out of service-driven expedited qua Windows Autopatch schedules and deploys required Out of Band (OOB) updates released outside of the normal schedule. Customers can view the deployed OOB quality updates on the **Release Management** blade on the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)**. -To view deployed OOB quality updates, customers can go to the Endpoint Manager admin center > Tenant administration > Windows Autopatch > Release management pane. Under the Release Announcements tab, customers can view the knowledge base (KB) articles corresponding to the deployed OOB quality updates. In case of a normal quality update release, KBs for the specific release will be available to the customers to view in the Release Announcements tab. Note that the announcements will be removed from the Release announcements tab when the next quality update is released. Further, if quality updates are paused for a ring, the OOB updates will also be paused. +To view deployed OOB quality updates, customers can go to the Endpoint Manager admin center > Tenant administration > Windows Autopatch > Release management pane. Under the Release Announcements tab, customers can view the knowledge base (KB) articles corresponding to the deployed OOB quality updates. In case of a normal quality update release, KBs for the specific release will be available to the customers to view in the Release Announcements tab. Note that the announcements will be removed from the Release announcements tab when the next quality update is released. Further, if quality updates are paused for a ring , the OOB updates will also be paused. ## Pausing and resuming a release From eaa9a2321afbd02729743d1f552e98247441a06b Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Fri, 9 Dec 2022 14:36:55 -0800 Subject: [PATCH 28/36] Create windows-autopatch-wqu-overview.md Reviewed OOB --- .../operate/windows-autopatch-wqu-overview.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index d63d67b12a..f2968ce393 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -60,7 +60,7 @@ When running an expedited release, the regular goal of 95% of devices in 21 days ### Opt out of expedited releases -Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, customers can go to the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Tenant administration** > **Windows Autopatch** > **Release management** blade. In the **Release management** blade, under the **Release settings** tab, turn off the **Expedited Quality Updates** setting. +Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, you can go to the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Tenant administration** > **Windows Autopatch** > **Release management** blade. In the **Release management** blade, under the **Release settings** tab, turn off the **Expedited Quality Updates** setting. | Release type | Group | Deferral | Deadline | Grace period | | ----- | ----- | ----- | ----- | ----- | @@ -70,11 +70,17 @@ Windows Autopatch provides the option to opt out of service-driven expedited qua > [!NOTE] > Windows Autopatch doesn't allow customers to request expedited releases. -## Out of Band release +## Out of Band releases -Windows Autopatch schedules and deploys required Out of Band (OOB) updates released outside of the normal schedule. Customers can view the deployed OOB quality updates on the **Release Management** blade on the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)**. +Windows Autopatch schedules and deploys required Out of Band (OOB) updates released outside of the normal schedule. You can view the deployed OOB quality updates in the **Release Management** blade in the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)**. -To view deployed OOB quality updates, customers can go to the Endpoint Manager admin center > Tenant administration > Windows Autopatch > Release management pane. Under the Release Announcements tab, customers can view the knowledge base (KB) articles corresponding to the deployed OOB quality updates. In case of a normal quality update release, KBs for the specific release will be available to the customers to view in the Release Announcements tab. Note that the announcements will be removed from the Release announcements tab when the next quality update is released. Further, if quality updates are paused for a ring , the OOB updates will also be paused. +**To view deployed OOB quality updates:** + +1. Go to [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Tenant administration** > **Windows Autopatch** > **Release management**. +2. Under the **Release Announcements** tab, you can view the knowledge base (KB) articles corresponding to deployed OOB and normal Windows quality updates. + +> [!Note] +> Announcements will be **removed** from the Release announcements tab when the next quality update is released. Further, if quality updates are paused for a deployment ring, the OOB updates will also be paused. ## Pausing and resuming a release From d41e645589f28fa9113f1279cf95164c2dde48c5 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Fri, 9 Dec 2022 14:39:01 -0800 Subject: [PATCH 29/36] Update windows-autopatch-wqu-overview.md --- .../windows-autopatch/operate/windows-autopatch-wqu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index f2968ce393..0479ead7f6 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -77,7 +77,7 @@ Windows Autopatch schedules and deploys required Out of Band (OOB) updates relea **To view deployed OOB quality updates:** 1. Go to [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Tenant administration** > **Windows Autopatch** > **Release management**. -2. Under the **Release Announcements** tab, you can view the knowledge base (KB) articles corresponding to deployed OOB and normal Windows quality updates. +2. Under the **Release Announcements** tab, you can view the knowledge base (KB) articles corresponding to deployed OOB and regular Windows quality updates. > [!Note] > Announcements will be **removed** from the Release announcements tab when the next quality update is released. Further, if quality updates are paused for a deployment ring, the OOB updates will also be paused. From 8a3d76c6289ff66e5cdbdbbe0c44f65719db8c00 Mon Sep 17 00:00:00 2001 From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Date: Mon, 12 Dec 2022 12:39:31 -0800 Subject: [PATCH 30/36] Update windows-autopatch-wqu-overview.md Tweaks --- .../operate/windows-autopatch-wqu-overview.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md index 0479ead7f6..dd16d441df 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md @@ -58,9 +58,14 @@ Threat and vulnerability information about a new revision of Windows becomes ava When running an expedited 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 as quickly. -### Opt out of expedited releases +### Turn off service-driven expedited quality update releases -Windows Autopatch provides the option to opt out of service-driven expedited quality updates. To opt out of service-driven expedited quality updates, you can go to the **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Tenant administration** > **Windows Autopatch** > **Release management** blade. In the **Release management** blade, under the **Release settings** tab, turn off the **Expedited Quality Updates** setting. +Windows Autopatch provides the option to turn off of service-driven expedited quality updates. + +**To turn off service-driven expedited quality updates:** + +1. Go to **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Tenant administration**. +2. Under **Windows Autopatch** > **Release management**, go to the **Release settings** tab and turn off the **Expedited Quality Updates** setting. | Release type | Group | Deferral | Deadline | Grace period | | ----- | ----- | ----- | ----- | ----- | From 84eedfcc83419390ad6b885f5c7ec65e5184d91d Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Tue, 13 Dec 2022 15:01:07 -0800 Subject: [PATCH 31/36] Removing Preview addendum as per Harman. --- .openpublishing.redirection.json | 5 +++ .../windows-autopatch-preview-addendum.md | 33 ------------------- 2 files changed, 5 insertions(+), 33 deletions(-) delete mode 100644 windows/deployment/windows-autopatch/references/windows-autopatch-preview-addendum.md diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index ae5ef4686a..a3d37259c5 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -20280,5 +20280,10 @@ "redirect_url": "/windows/deployment/windows-autopatch/references/windows-autopatch-wqu-unsupported-policies", "redirect_document_id": true } + { + "source_path": "windows/deployment/windows-autopatch/references/windows-autopatch-preview-addendum.md", + "redirect_url": "/windows/deployment/windows-autopatch/overview/windows-autopatch-overview", + "redirect_document_id": true + } ] } diff --git a/windows/deployment/windows-autopatch/references/windows-autopatch-preview-addendum.md b/windows/deployment/windows-autopatch/references/windows-autopatch-preview-addendum.md deleted file mode 100644 index d0f3e5acba..0000000000 --- a/windows/deployment/windows-autopatch/references/windows-autopatch-preview-addendum.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Windows Autopatch Preview Addendum -description: This article explains the Autopatch preview addendum -ms.date: 05/30/2022 -ms.prod: windows-client -ms.technology: itpro-updates -ms.topic: reference -ms.localizationpriority: medium -author: tiaraquan -ms.author: tiaraquan -manager: dougeby -msreviewer: hathind ---- - -# Windows Autopatch Preview Addendum - -**This Windows Autopatch - Preview Addendum ("Addendum") to the Microsoft Product Terms** (as provided at: (the "**Product Terms**")) is entered into between Microsoft Corporation, a Washington corporation having its principal place of business at One Microsoft Way, Redmond, Washington, USA 98052-6399 (or based on where Customer lives, one of Microsoft's affiliates) ("**Microsoft**"), and you ("**Customer**"). - -## Background - -Microsoft desires to preview the Windows Autopatch service it is developing ("**Windows Autopatch Preview**") in order to evaluate it. Customer would like to particulate this Windows Autopatch Preview under the terms of the Product Terms and this Addendum. Windows Autopatch Preview consists of features and services that are in preview, beta, or other pre-release form. Windows Autopatch Preview is subject to the "preview" terms set forth in the Online Service sections of Product Terms. - -For good and valuable consideration, the receipt and sufficiency of which is acknowledged, the parties agree as follows: - -## Agreement - -### Definitions - -Capitalized terms used but not defined herein have the meanings given in the Product Terms. - -### Data Handling - -Windows Autopatch Preview integrates Customer Data from other Products, including Windows, Microsoft Intune, Azure Active Directory, and Office (collectively for purposes of this provision "Windows Autopatch Input Services"). Once Customer Data from Windows Autopatch Input Services is integrated into Windows Autopatch Preview, only the Product Terms and [DPA provisions)](https://www.microsoft.com/licensing/terms/product/Glossary/all) applicable to Windows Autopatch Preview apply to that data. From 98aa1e18ffd5145283de968f455b2442b829683d Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Tue, 13 Dec 2022 15:10:45 -0800 Subject: [PATCH 32/36] Stupid comma --- .openpublishing.redirection.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index a3d37259c5..5ac855eded 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -20279,7 +20279,7 @@ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-unsupported-policies.md", "redirect_url": "/windows/deployment/windows-autopatch/references/windows-autopatch-wqu-unsupported-policies", "redirect_document_id": true - } + }, { "source_path": "windows/deployment/windows-autopatch/references/windows-autopatch-preview-addendum.md", "redirect_url": "/windows/deployment/windows-autopatch/overview/windows-autopatch-overview", From dc206005f5fe70e0d6d11ac7303583e888abd17c Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Tue, 13 Dec 2022 21:12:14 -0800 Subject: [PATCH 33/36] Toc update. --- windows/deployment/windows-autopatch/TOC.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml index bc71c6def8..e5dc7cb910 100644 --- a/windows/deployment/windows-autopatch/TOC.yml +++ b/windows/deployment/windows-autopatch/TOC.yml @@ -100,8 +100,6 @@ href: references/windows-autopatch-changes-to-tenant.md - name: Privacy href: references/windows-autopatch-privacy.md - - name: Windows Autopatch preview addendum - href: references/windows-autopatch-preview-addendum.md - name: What's new href: items: From 0f9a185430b4bbd54cab85c0bea8d53239ebea9b Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Wed, 14 Dec 2022 08:46:11 -0800 Subject: [PATCH 34/36] Whats new 121422 --- .../whats-new/windows-autopatch-whats-new-2022.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md index ee1eb75dce..67df9f09a5 100644 --- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md +++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md @@ -24,6 +24,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed. | Article | Description | | ----- | ----- | +| [Windows quality updates](../operate/windows-autopatch-wqu-overview.md) | Added information about turning off service-driven expedited quality update releases and viewing deployed out of band releases | | [Roles and responsibilities](../overview/windows-autopatch-roles-responsibilities.md) | Added Roles and responsibilities article | | [Prerequisites](../prepare/windows-autopatch-prerequisites.md) | Added more licenses to the More about licenses section