From b7372caea40c7c63bc88606e65d45e41de620bc0 Mon Sep 17 00:00:00 2001 From: Payge Winfield Date: Fri, 28 Feb 2020 06:59:44 -0800 Subject: [PATCH 01/11] Changed App section --- devices/hololens/hololens-requirements.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md index 6c370939da..2a219c7555 100644 --- a/devices/hololens/hololens-requirements.md +++ b/devices/hololens/hololens-requirements.md @@ -33,7 +33,7 @@ This document also assumes that the HoloLens has been evaluated by security team Before deploying the HoloLens in your environment, it is important to first determine what features, apps, and type of identities are needed. It is also important to ensure that your security team has approved of the use of the HoloLens on the company's network. Please see [Frequently ask security questions](hololens-faq-security.md) for additional security information. -### Type of identity +### Type of Identity Determine the type of identity that will be used to sign into the device. @@ -66,13 +66,15 @@ There are two types of Kiosk Modes: Single app and multi-app. Single app kiosk m There are two main ways ([provisioning packages](hololens-kiosk.md#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803) and [MDM](hololens-kiosk.md#set-up-kiosk-mode-using-microsoft-intune-or-mdm-windows-10-version-1803)) to deploy kiosk mode for HoloLens. These options will be discussed later in the document; however, you can use the links above to jump to the respective sections in this doc. -### Apps +### Apps and App Specific Scenarios The majority of the steps found in this document will also apply to the following apps: -1. Remote Assist -2. Guides -3. Customer Apps +| App | App Specific Scenarios | +| --- | --- | +| Remote Assist | [Cross Tenant Communication]()| +| Guides | *Coming Soon* | +|Custom Apps | | ### Determine your enrollment method From 16f8744e4b9695302316c7def86320c04e28311a Mon Sep 17 00:00:00 2001 From: AmitEnoch <45037036+AmitEnoch@users.noreply.github.com> Date: Mon, 9 Mar 2020 16:40:28 +0200 Subject: [PATCH 02/11] Update mac-preferences.md Added a note for Tag settings. 1. It is possible to set only one value per tag. 2. Type of tags are unique, and can not be duplicated in the same configuration. --- .../microsoft-defender-atp/mac-preferences.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md b/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md index 4fc8a7c36e..d5d6e134b6 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md @@ -356,6 +356,10 @@ Specifies the value of tag | **Data type** | String | | **Possible values** | any string | + > [!NOTE] + > It is possible to set only one value per tag type. + > Type of tags are unique, and should not be repeated in the same configuration. + ## Recommended configuration profile To get started, we recommend the following configuration profile for your enterprise to take advantage of all protection features that Microsoft Defender ATP provides. From 45e9ded8d988cdc5ac876fc232ac14254b5b7a50 Mon Sep 17 00:00:00 2001 From: AmitEnoch <45037036+AmitEnoch@users.noreply.github.com> Date: Mon, 9 Mar 2020 16:46:26 +0200 Subject: [PATCH 03/11] Update mac-preferences.md --- .../microsoft-defender-atp/mac-preferences.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md b/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md index d5d6e134b6..02e92c2e0b 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md @@ -356,9 +356,9 @@ Specifies the value of tag | **Data type** | String | | **Possible values** | any string | - > [!NOTE] - > It is possible to set only one value per tag type. - > Type of tags are unique, and should not be repeated in the same configuration. +> [!IMPORTANT] +> * It is possible to set only one value per tag type. +> * Type of tags are unique, and should not be repeated in the same configuration profile. ## Recommended configuration profile From 018599c97326b7d302c26e362d213c5a4896c57d Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Mon, 9 Mar 2020 09:53:23 -0700 Subject: [PATCH 04/11] Update mac-preferences.md --- .../microsoft-defender-atp/mac-preferences.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md b/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md index 02e92c2e0b..76875534f3 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mac-preferences.md @@ -357,8 +357,8 @@ Specifies the value of tag | **Possible values** | any string | > [!IMPORTANT] -> * It is possible to set only one value per tag type. -> * Type of tags are unique, and should not be repeated in the same configuration profile. +> - Only one value per tag type can be set. +> - Type of tags are unique, and should not be repeated in the same configuration profile. ## Recommended configuration profile From f9aa9911147c47f12eee98f9da0b57bf73d26959 Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 9 Mar 2020 09:58:04 -0700 Subject: [PATCH 05/11] removed stray references to Windows Analytics --- windows/deployment/update/index.md | 2 +- .../update/update-compliance-delivery-optimization.md | 2 +- windows/deployment/update/waas-delivery-optimization-setup.md | 2 +- windows/deployment/update/waas-morenews.md | 1 - windows/deployment/update/windows-as-a-service.md | 2 -- windows/deployment/update/wufb-basics.md | 4 ++-- 6 files changed, 5 insertions(+), 8 deletions(-) diff --git a/windows/deployment/update/index.md b/windows/deployment/update/index.md index a81d83a38c..06ca9774d4 100644 --- a/windows/deployment/update/index.md +++ b/windows/deployment/update/index.md @@ -36,7 +36,7 @@ Windows as a service provides a new way to think about building, deploying, and | [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) | Explains the decisions you need to make in your servicing strategy. | | [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) | Explains how to make use of servicing branches and update deferrals to manage Windows 10 updates. | | [Assign devices to servicing branches for Windows 10 updates](https://docs.microsoft.com/windows/deployment/update/waas-servicing-channels-windows-10-updates) | Explains how to assign devices to the Semi-Annual Channel for feature and quality updates, and how to enroll devices in Windows Insider. | -| [Monitor Windows Updates with Update Compliance](update-compliance-monitor.md) | Explains how to use Windows Analytics: Update Compliance to monitor and manage Windows Updates on devices in your organization. | +| [Monitor Windows Updates with Update Compliance](update-compliance-monitor.md) | Explains how to use Update Compliance to monitor and manage Windows Updates on devices in your organization. | | [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) | Explains the benefits of using Delivery Optimization or BranchCache for update distribution. | | [Deploy updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md) | Explains updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile. | | [Deploy updates using Windows Update for Business](waas-manage-updates-wufb.md) | Explains how to use Windows Update for Business to manage when devices receive updates directly from Windows Update. Includes walkthroughs for configuring Windows Update for Business using Group Policy and Microsoft Intune. | diff --git a/windows/deployment/update/update-compliance-delivery-optimization.md b/windows/deployment/update/update-compliance-delivery-optimization.md index 612c44e92a..c3c6abb633 100644 --- a/windows/deployment/update/update-compliance-delivery-optimization.md +++ b/windows/deployment/update/update-compliance-delivery-optimization.md @@ -17,7 +17,7 @@ ms.topic: article # Delivery Optimization in Update Compliance ![DO status](images/UC_workspace_DO_status.png) -The Update Compliance solution of Windows Analytics provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days. +The Update Compliance solution provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days. ## Delivery Optimization Status diff --git a/windows/deployment/update/waas-delivery-optimization-setup.md b/windows/deployment/update/waas-delivery-optimization-setup.md index 61a6af8b7c..0794a4b894 100644 --- a/windows/deployment/update/waas-delivery-optimization-setup.md +++ b/windows/deployment/update/waas-delivery-optimization-setup.md @@ -183,7 +183,7 @@ Log entries are written to the PowerShell pipeline as objects. To dump logs to a ### Monitor with Update Compliance -The Update Compliance solution of Windows Analytics provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days. +Update Compliance provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days. ![DO status](images/UC_workspace_DO_status.png) diff --git a/windows/deployment/update/waas-morenews.md b/windows/deployment/update/waas-morenews.md index c7be3666ed..b23dfbb017 100644 --- a/windows/deployment/update/waas-morenews.md +++ b/windows/deployment/update/waas-morenews.md @@ -45,7 +45,6 @@ Here's more news about [Windows as a service](windows-as-a-service.md):
  • Reducing Windows 10 Package Size Downloads for x64 Systems - September 26, 2018
  • Windows 7 Servicing Stack Updates: Managing Change and Appreciating Cumulative Updates - September 21, 2018
  • Helping customers shift to a modern desktop - September 6, 2018
  • -
  • Windows Update for Business & Windows Analytics: a real-world experience - September 5, 2018
  • What's next for Windows 10 and Windows Server quality updates - August 16, 2018
  • Windows 10 monthly updates - August 1, 2018 (video)
  • Windows 10 update servicing cadence - August 1, 2018
  • diff --git a/windows/deployment/update/windows-as-a-service.md b/windows/deployment/update/windows-as-a-service.md index 613250332f..4a82dd3265 100644 --- a/windows/deployment/update/windows-as-a-service.md +++ b/windows/deployment/update/windows-as-a-service.md @@ -73,7 +73,6 @@ Learn more about Windows as a service and its value to your organization. Quick guide to Windows as a service -Windows Analytics overview What's new in Windows 10 deployment @@ -117,7 +116,6 @@ Secure your organization's deployment investment. Looking to learn more? These informative session replays from Microsoft Ignite 2018 (complete with downloadable slide decks) can provide some great insights on Windows as a service. -[BRK2417: What’s new in Windows Analytics: An Intro to Desktop Analytics](https://myignite.techcommunity.microsoft.com/sessions/64324#ignite-html-anchor) [BRK3018: Deploying Windows 10 in the enterprise using traditional and modern techniques](https://myignite.techcommunity.microsoft.com/sessions/64509#ignite-html-anchor) diff --git a/windows/deployment/update/wufb-basics.md b/windows/deployment/update/wufb-basics.md index 11483f0c9b..640a8d1800 100644 --- a/windows/deployment/update/wufb-basics.md +++ b/windows/deployment/update/wufb-basics.md @@ -16,7 +16,7 @@ ms.topic: article --- # Configure the Basic group policy for Windows Update for Business -For Windows Update for Business configurations to work, devices need to be configured with minimum [diagnostic data](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization) level of "Basic." Additionally, compliance reporting for configured devices is obtained using [Update Compliance in Windows Analytics](https://docs.microsoft.com/windows/deployment/update/update-compliance-monitor). To view your data in Update Compliance [diagnostics data must be enabled](https://docs.microsoft.com/windows/deployment/update/windows-analytics-get-started#set-diagnostic-data-levels) and the devices must be configured with a commercial ID, a unique GUID created for an enterprise at the time of onboarding to the Windows Analytics solution. +For Windows Update for Business configurations to work, devices need to be configured with minimum [diagnostic data](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization) level of "Basic." Additionally, compliance reporting for configured devices is obtained using [Monitor Windows Update with Update Compliance](https://docs.microsoft.com/windows/deployment/update/update-compliance-monitor). To view your data in Update Compliance [diagnostics data must be enabled](https://docs.microsoft.com/windows/deployment/update/windows-analytics-get-started#set-diagnostic-data-levels) and the devices must be configured with a commercial ID, a unique GUID created for an enterprise at the time of onboarding. |Policy name|Description | |-|-| @@ -28,4 +28,4 @@ For Windows Update for Business configurations to work, devices need to be confi |Policy|Location|Suggested configuration| |-|-|-| |Allow Telemetry |GPO: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Allow Telemetry |State: Enabled
    **Option**: 1-Basic| -|Configure Commercial ID|GPO: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Configure Commercial ID |State: Enabled
    **Commercial ID**: The GUID created for you at the time of onboarding to Windows Analytics| +|Configure Commercial ID|GPO: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Configure Commercial ID |State: Enabled
    **Commercial ID**: The GUID created for you at the time of onboarding| From d2cc08f41ba2f9a9a18ebc2db11e190fed496af5 Mon Sep 17 00:00:00 2001 From: pawinfie <59937840+pawinfie@users.noreply.github.com> Date: Mon, 9 Mar 2020 10:28:30 -0700 Subject: [PATCH 06/11] added likes to RA docs --- devices/hololens/hololens-licenses-requirements.md | 4 +++- devices/hololens/hololens-requirements.md | 6 ++++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/devices/hololens/hololens-licenses-requirements.md b/devices/hololens/hololens-licenses-requirements.md index c89587c100..7b843d3280 100644 --- a/devices/hololens/hololens-licenses-requirements.md +++ b/devices/hololens/hololens-licenses-requirements.md @@ -23,7 +23,7 @@ appliesto: If you plan on managing your HoloLens devices, you will need Azure AD and an MDM. Active Director (AD) cannot be used to manage HoloLens devices. If you plan on using an MDM other than Intune, an [Azure Active Directory Licenses](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) is required. -If you plan on using Intune as your MDM, you can acquire an [Enterprise Mobility + Security (EMS) suite (E3 or E5) licenses](https://www.microsoft.com/microsoft-365/enterprise-mobility-security/compare-plans-and-pricing). **Please note that Azure AD is included in both suites.** +If you plan on using Intune as your MDM, [here](https://docs.microsoft.com/intune/fundamentals/licenses) are a list of suites that includes Intune licenses. **Please note that Azure AD is included in the majority of these suites.** ## Identify the licenses needed for your scenario and products @@ -44,6 +44,8 @@ Make sure you have the required licensing and device. Updated licensing and prod 1. [Teams Freemium/Teams](https://products.office.com/microsoft-teams/free) 1. [Azure Active Directory (Azure AD) License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) +If you plan on implementing a cross-tenant communication scenario, you may need an [Information Barrier license](https://docs.microsoft.com/microsoft-365/compliance/information-barriers?view=o365-worldwide#required-licenses-and-permissions). Please visit the [Cross Tenant Communication Overview](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-licensing-implementation#step-1-determine-if-information-barriers-are-necessary) article to determine if an Information Barrier License is required for your scenario. + ### Guides License Requirements Updated licensing and device requirements can be found [here](https://docs.microsoft.com/dynamics365/mixed-reality/guides/requirements). diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md index 2a219c7555..86dc598515 100644 --- a/devices/hololens/hololens-requirements.md +++ b/devices/hololens/hololens-requirements.md @@ -41,6 +41,8 @@ Determine the type of identity that will be used to sign into the device. 2. **MSA:** This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device. 3. **Azure Active Directory (Azure AD) accounts:** This is an account created in Azure AD. This grants your corporation the ability to manage the HoloLens device. This will allow multiple users to log into the HoloLens 1st Gen Commercial Suite/the HoloLens 2 device. +For more detailed information about identity types, please visit our [HoloLens Identity](#hololens-identity.md) article. + ### Type of Features Your feature requirements will determine which HoloLens you need. One popular feature that we see deployed in customer environments frequently is Kiosk Mode. A list of HoloLens key features, and the editions of HoloLens that support them, can be found [here](hololens-commercial-features.md). @@ -72,9 +74,9 @@ The majority of the steps found in this document will also apply to the followin | App | App Specific Scenarios | | --- | --- | -| Remote Assist | [Cross Tenant Communication]()| +| Remote Assist | [Cross Tenant Communication](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-overview)| | Guides | *Coming Soon* | -|Custom Apps | | +|Custom Apps | *Coming Soon* | ### Determine your enrollment method From 8890c8a641588668ecc0b6673b112249826f5bfb Mon Sep 17 00:00:00 2001 From: pawinfie <59937840+pawinfie@users.noreply.github.com> Date: Mon, 9 Mar 2020 10:34:37 -0700 Subject: [PATCH 07/11] link to RA info barrier article --- devices/hololens/hololens-licenses-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/hololens/hololens-licenses-requirements.md b/devices/hololens/hololens-licenses-requirements.md index 7b843d3280..ef727bfc77 100644 --- a/devices/hololens/hololens-licenses-requirements.md +++ b/devices/hololens/hololens-licenses-requirements.md @@ -44,7 +44,7 @@ Make sure you have the required licensing and device. Updated licensing and prod 1. [Teams Freemium/Teams](https://products.office.com/microsoft-teams/free) 1. [Azure Active Directory (Azure AD) License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) -If you plan on implementing a cross-tenant communication scenario, you may need an [Information Barrier license](https://docs.microsoft.com/microsoft-365/compliance/information-barriers?view=o365-worldwide#required-licenses-and-permissions). Please visit the [Cross Tenant Communication Overview](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-licensing-implementation#step-1-determine-if-information-barriers-are-necessary) article to determine if an Information Barrier License is required for your scenario. +If you plan on implementing **[this cross-tenant scenario](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-overview#scenario-2-leasing-services-to-other-tenants)**, you may need an Information Barriers license. Please see [this article](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-licensing-implementation#step-1-determine-if-information-barriers-are-necessary) to determine if an Information Barrier License is required. ### Guides License Requirements From 6dcf585b5f69a123419ebb363bfce097a34e5d61 Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 9 Mar 2020 10:45:03 -0700 Subject: [PATCH 08/11] fixing a few metadata items --- windows/deployment/update/waas-delivery-optimization-setup.md | 1 - windows/deployment/update/windows-as-a-service.md | 4 ++-- windows/deployment/update/wufb-basics.md | 1 - 3 files changed, 2 insertions(+), 4 deletions(-) diff --git a/windows/deployment/update/waas-delivery-optimization-setup.md b/windows/deployment/update/waas-delivery-optimization-setup.md index 0794a4b894..ac14bcf549 100644 --- a/windows/deployment/update/waas-delivery-optimization-setup.md +++ b/windows/deployment/update/waas-delivery-optimization-setup.md @@ -6,7 +6,6 @@ description: Delivery Optimization is a new peer-to-peer distribution method in keywords: oms, operations management suite, wdav, updates, downloads, log analytics ms.prod: w10 ms.mktglfcycl: deploy - audience: itpro author: jaimeo ms.localizationpriority: medium diff --git a/windows/deployment/update/windows-as-a-service.md b/windows/deployment/update/windows-as-a-service.md index 4a82dd3265..6dca369b35 100644 --- a/windows/deployment/update/windows-as-a-service.md +++ b/windows/deployment/update/windows-as-a-service.md @@ -1,8 +1,8 @@ --- title: Windows as a service -ms.prod: windows-10 +ms.prod: w10 ms.topic: landing-page -ms.manager: elizapo +ms.manager: laurawi audience: itpro itproauthor: jaimeo author: jaimeo diff --git a/windows/deployment/update/wufb-basics.md b/windows/deployment/update/wufb-basics.md index 640a8d1800..719b115f4f 100644 --- a/windows/deployment/update/wufb-basics.md +++ b/windows/deployment/update/wufb-basics.md @@ -9,7 +9,6 @@ author: jaimeo ms.localizationprioauthor: jaimeo ms.audience: itpro author: jaimeo -ms.date: 06/20/2018 ms.reviewer: manager: laurawi ms.topic: article From 8b212f1226255a61f396e034e8f7db26e47a894f Mon Sep 17 00:00:00 2001 From: pawinfie <59937840+pawinfie@users.noreply.github.com> Date: Mon, 9 Mar 2020 10:48:34 -0700 Subject: [PATCH 09/11] fixed hololens identity link --- devices/hololens/hololens-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md index 86dc598515..6cfcb281b0 100644 --- a/devices/hololens/hololens-requirements.md +++ b/devices/hololens/hololens-requirements.md @@ -41,7 +41,7 @@ Determine the type of identity that will be used to sign into the device. 2. **MSA:** This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device. 3. **Azure Active Directory (Azure AD) accounts:** This is an account created in Azure AD. This grants your corporation the ability to manage the HoloLens device. This will allow multiple users to log into the HoloLens 1st Gen Commercial Suite/the HoloLens 2 device. -For more detailed information about identity types, please visit our [HoloLens Identity](#hololens-identity.md) article. +For more detailed information about identity types, please visit our [HoloLens Identity](hololens-identity.md) article. ### Type of Features From afe056556fce98c0776afed5a1b20eb7c30a2381 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Mon, 9 Mar 2020 11:23:09 -0700 Subject: [PATCH 10/11] add rss feed --- .../whats-new-in-microsoft-defender-atp.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/security/threat-protection/microsoft-defender-atp/whats-new-in-microsoft-defender-atp.md b/windows/security/threat-protection/microsoft-defender-atp/whats-new-in-microsoft-defender-atp.md index 2d9187a57f..689a9fe3d1 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/whats-new-in-microsoft-defender-atp.md +++ b/windows/security/threat-protection/microsoft-defender-atp/whats-new-in-microsoft-defender-atp.md @@ -27,6 +27,9 @@ The following features are generally available (GA) in the latest release of Mic For more information preview features, see [Preview features](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/preview-windows-defender-advanced-threat-protection). +RSS feed: Get notified when this page is updated by copying and pasting the following URL into your feed reader: +`https://docs.microsoft.com/api/search/rss?search=%22Lists+the+new+features+and+functionality+in+Microsoft+Defender+ATP%22&locale=en-us` + ## November-December 2019 - [Microsoft Defender ATP for Mac](microsoft-defender-atp-mac.md)
    Microsoft Defender ATP for Mac brings the next-generation protection to Mac devices. Core components of the unified endpoint security platform will now be available for Mac devices, including [endpoint detection and response](endpoint-detection-response-mac-preview.md). From 4b6f25aea9ad6f915de6a73bd5c09cb6c588b7c6 Mon Sep 17 00:00:00 2001 From: John Kaiser <35939694+CoveMiner@users.noreply.github.com> Date: Mon, 9 Mar 2020 14:19:54 -0700 Subject: [PATCH 11/11] Update surface-system-sku-reference.md Removes incorrect info --- devices/surface/surface-system-sku-reference.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/devices/surface/surface-system-sku-reference.md b/devices/surface/surface-system-sku-reference.md index dbcb9648b0..f74ee76e83 100644 --- a/devices/surface/surface-system-sku-reference.md +++ b/devices/surface/surface-system-sku-reference.md @@ -9,7 +9,7 @@ ms.sitesec: library author: dansimp ms.author: dansimp ms.topic: article -ms.date: 10/31/2019 +ms.date: 03/09/2020 ms.reviewer: manager: dansimp ms.localizationpriority: medium @@ -24,18 +24,15 @@ System Model and System SKU are variables that are stored in the System Manageme | Device | System Model | System SKU | | ---------- | ----------- | -------------- | -| AMD Surface Laptop 3 | Surface 3 | Surface_Laptop_3_1873 | -| Surface Laptop 3 | Surface 3 | Surface_Laptop_3_1867:1868 | -| Surface Laptop 3 | Surface 3 | Surface_3 | Surface 3 WiFI | Surface 3 | Surface_3 | | Surface 3 LTE AT&T | Surface 3 | Surface_3_US1 | | Surface 3 LTE Verizon | Surface 3 | Surface_3_US2 | | Surface 3 LTE North America | Surface 3 | Surface_3_NAG | -| Surface 3 LTE Outside of North America and Y!mobile In Japan | Surface 3 | Surface_3_ROW | +| Surface 3 LTE outside of North America and Y!mobile in Japan | Surface 3 | Surface_3_ROW | | Surface Pro | Surface Pro | Surface_Pro_1796 | | Surface Pro with LTE Advanced | Surface Pro | Surface_Pro_1807 | -| Surface Book 2 13inch | Surface Book 2 | Surface_Book_1832 | -| Surface Book 2 15inch | Surface Book 2 | Surface_Book_1793 | +| Surface Book 2 13" | Surface Book 2 | Surface_Book_1832 | +| Surface Book 2 15" | Surface Book 2 | Surface_Book_1793 | | Surface Go LTE Consumer | Surface Go | Surface_Go_1825_Consumer | | Surface Go LTE Commercial | System Go | Surface_Go_1825_Commercial | | Surface Go Consumer | Surface Go | Surface_Go_1824_Consumer |