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] 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.")
 
 <br>
 
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 @@
+<svg id="bf97f450-0d91-4db3-8ea1-010780a2af52" xmlns="http://www.w3.org/2000/svg" width="18" height="18" viewBox="0 0 18 18">
+  <defs>
+    <linearGradient id="fe22bed8-8e36-415d-8032-3026ad9e8503" x1="8.56" y1="17.59" x2="8.56" y2="0.59" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#1988d9" />
+      <stop offset="0.22" stop-color="#218ddc" />
+      <stop offset="0.56" stop-color="#379ce5" />
+      <stop offset="0.9" stop-color="#54aef0" />
+    </linearGradient>
+  </defs>
+  <title>Icon-general-5</title>
+  <path id="b3492ff9-55dd-4864-be78-9e79f3547897" d="M13.77,15.81A8.5,8.5,0,0,1,3.35,2.37l.09-.06a8.5,8.5,0,0,1,10.33,13.5" fill="url(#fe22bed8-8e36-415d-8032-3026ad9e8503)" />
+  <path d="M8.56,6.17a1.24,1.24,0,0,1-.89-.33,1,1,0,0,1-.34-.79,1,1,0,0,1,.34-.79A1.31,1.31,0,0,1,8.56,4a1.28,1.28,0,0,1,.89.3,1,1,0,0,1,.35.79,1,1,0,0,1-.35.8A1.24,1.24,0,0,1,8.56,6.17Zm.64,8.05H7.89a.42.42,0,0,1-.42-.42V7.69a.42.42,0,0,1,.42-.42H9.2a.42.42,0,0,1,.42.42V13.8A.42.42,0,0,1,9.2,14.22Z" fill="#fff" />
+</svg>
\ No newline at end of file