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/16] 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/16] 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 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 03/16] 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 04/16] 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 05/16] 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 06/16] 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 07/16] 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 08/16] 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 09/16] 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 10/16] 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 11/16] 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 12/16] 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 13/16] 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 14/16] 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 15/16] 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 16/16] 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.