Merge branch 'main' into patch-24

This commit is contained in:
Daniel Simpson 2022-03-28 09:58:19 -07:00 committed by GitHub
commit c76eb68a99
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 25 additions and 14 deletions

View File

@ -51,8 +51,9 @@ Before you begin the process to add Update Compliance to your Azure subscription
## Add Update Compliance to your Azure subscription ## Add Update Compliance to your Azure subscription
Update Compliance is offered as an Azure Marketplace application which is linked to a new or existing [Azure Log Analytics](/azure/log-analytics/query-language/get-started-analytics-portal) workspace within your Azure subscription. To configure this, follow these steps: Update Compliance is offered as an Azure Marketplace application that is linked to a new or existing [Azure Log Analytics](/azure/log-analytics/query-language/get-started-analytics-portal) workspace within your Azure subscription. Note that, for the following steps, you must have either an Owner or Contributor [Azure role](/azure/role-based-access-control/rbac-and-directory-admin-roles#azure-roles) as a minimum in order to add the solution.
To configure this, follow these steps:
1. Go to the [Update Compliance page in the Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/Microsoft.WaaSUpdateInsights?tab=Overview). You might need to login to your Azure subscription to access this. 1. Go to the [Update Compliance page in the Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/Microsoft.WaaSUpdateInsights?tab=Overview). You might need to login to your Azure subscription to access this.
2. Select **Get it now**. 2. Select **Get it now**.
3. Choose an existing or configure a new Log Analytics Workspace, ensuring it is in a **Compatible Log Analytics region** from the following table. Although an Azure subscription is required, you won't be charged for ingestion of Update Compliance data. 3. Choose an existing or configure a new Log Analytics Workspace, ensuring it is in a **Compatible Log Analytics region** from the following table. Although an Azure subscription is required, you won't be charged for ingestion of Update Compliance data.
@ -60,6 +61,12 @@ Update Compliance is offered as an Azure Marketplace application which is linked
- [Azure Update Management](/azure/automation/automation-intro#update-management) users should use the same workspace for Update Compliance. - [Azure Update Management](/azure/automation/automation-intro#update-management) users should use the same workspace for Update Compliance.
4. After your workspace is configured and selected, select **Create**. You'll receive a notification when the solution has been successfully created. 4. After your workspace is configured and selected, select **Create**. You'll receive a notification when the solution has been successfully created.
Once the solution is in place, you can leverage one of the following Azure roles with Update Compliance:
- To edit and write queries we recommend the [Log Analytics Contributor](/azure/role-based-access-control/built-in-roles#log-analytics-contributor) role.
- To read and only view data we recommend the [Log Analytics Reader](/azure/role-based-access-control/built-in-roles#log-analytics-reader) role.
|Compatible Log Analytics regions | |Compatible Log Analytics regions |
| ------------------------------- | | ------------------------------- |
|Australia Central | |Australia Central |

View File

@ -88,7 +88,7 @@ If you already have Hyper-V and a Windows 10 VM, you can skip directly to the [C
- [Prepare the app for Intune](#prepare-the-app-for-intune) - [Prepare the app for Intune](#prepare-the-app-for-intune)
- [Create app in Intune](#create-app-in-intune) - [Create app in Intune](#create-app-in-intune)
- [Assign the app to your Intune profile](#assign-the-app-to-your-intune-profile) - [Assign the app to your Intune profile](#assign-the-app-to-your-intune-profile)
- [Add Office 365](#add-office-365) - [Add Office 365](#add-microsoft-365-apps)
- [Create app in Intune](#create-app-in-intune) - [Create app in Intune](#create-app-in-intune)
- [Assign the app to your Intune profile](#assign-the-app-to-your-intune-profile) - [Assign the app to your Intune profile](#assign-the-app-to-your-intune-profile)
- [Glossary](#glossary) - [Glossary](#glossary)
@ -508,7 +508,7 @@ Select **Next** to continue with the **Out-of-box experience (OOBE)** settings:
| Privacy Settings | Hide | | Privacy Settings | Hide |
| Hide change account options | Hide | | Hide change account options | Hide |
| User account type | Standard | | User account type | Standard |
| Allow White Glove OOBE | No | | Allow pre-provisioned deployment | No |
| Language (Region) | Operating system default | | Language (Region) | Operating system default |
| Automatically configure keyboard | Yes | | Automatically configure keyboard | Yes |
| Apply device name template | No | | Apply device name template | No |
@ -814,9 +814,9 @@ At this point, you have completed steps to add a Win32 app to Intune.
For more information on adding apps to Intune, see [Intune Standalone - Win32 app management](/intune/apps-win32-app-management). For more information on adding apps to Intune, see [Intune Standalone - Win32 app management](/intune/apps-win32-app-management).
### Add Office 365 ### Add Microsoft 365 Apps
#### Create app in Intune #### Create app in Microsoft Endpoint Manager
Log in to the Azure portal and select **Intune**. Log in to the Azure portal and select **Intune**.
@ -824,7 +824,7 @@ Go to **Intune > Clients apps > Apps**, and then select the **Add** button to cr
![Create app step 1.](images/app17.png) ![Create app step 1.](images/app17.png)
Under **App Type**, select **Office 365 Suite > Windows 10**: Under **App Type**, select **Microsoft 365 Apps > Windows 10 and later**:
![Create app step 2.](images/app18.png) ![Create app step 2.](images/app18.png)

View File

@ -6,7 +6,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library ms.sitesec: library
ms.pagetype: security ms.pagetype: security
author: dansimp author: dansimp
ms.date: 09/23/2021 ms.date: 03/22/2022
ms.reviewer: ms.reviewer:
manager: dansimp manager: dansimp
ms.author: dansimp ms.author: dansimp
@ -29,6 +29,9 @@ The credentials are placed in Credential Manager as a "\*Session" credential.
A "\*Session" credential implies that it is valid for the current user session. A "\*Session" credential implies that it is valid for the current user session.
The credentials are also cleaned up when the WiFi or VPN connection is disconnected. The credentials are also cleaned up when the WiFi or VPN connection is disconnected.
> [!NOTE]
> In Windows 10, version 21h2 and later, the "\*Session" credential is not visible in Credential Manager.
For example, if someone using Microsoft Edge tries to access a domain resource, Microsoft Edge has the right Enterprise Authentication capability. This allows [WinInet](/windows/win32/wininet/wininet-reference) to release the credentials that it gets from the Credential Manager to the SSP that is requesting it. For example, if someone using Microsoft Edge tries to access a domain resource, Microsoft Edge has the right Enterprise Authentication capability. This allows [WinInet](/windows/win32/wininet/wininet-reference) to release the credentials that it gets from the Credential Manager to the SSP that is requesting it.
For more information about the Enterprise Authentication capability, see [App capability declarations](/windows/uwp/packaging/app-capability-declarations). For more information about the Enterprise Authentication capability, see [App capability declarations](/windows/uwp/packaging/app-capability-declarations).
@ -93,4 +96,4 @@ Domain controllers must have appropriate KDC certificates for the client to trus
Domain controllers must be using certificates based on the updated KDC certificate template Kerberos Authentication. Domain controllers must be using certificates based on the updated KDC certificate template Kerberos Authentication.
This requires that all authenticating domain controllers run Windows Server 2016, or you'll need to enable strict KDC validation on domain controllers that run previous versions of Windows Server. This requires that all authenticating domain controllers run Windows Server 2016, or you'll need to enable strict KDC validation on domain controllers that run previous versions of Windows Server.
For more information, see [Enabling Strict KDC Validation in Windows Kerberos](https://www.microsoft.com/download/details.aspx?id=6382). For more information, see [Enabling Strict KDC Validation in Windows Kerberos](https://www.microsoft.com/download/details.aspx?id=6382).

View File

@ -16,6 +16,7 @@ ms.collection:
- M365-security-compliance - M365-security-compliance
- highpri - highpri
ms.topic: conceptual ms.topic: conceptual
adobe-target: true
--- ---
# Trusted Platform Module Technology Overview # Trusted Platform Module Technology Overview

View File

@ -9,9 +9,9 @@ ms.mktglfcycl:
ms.sitesec: library ms.sitesec: library
ms.pagetype: security ms.pagetype: security
ms.localizationpriority: medium ms.localizationpriority: medium
author: cabailey author: aczechowski
ms.author: cabailey ms.author: aaroncz
manager: laurawi manager: dougeby
audience: ITPro audience: ITPro
ms.collection: M365-security-compliance ms.collection: M365-security-compliance
ms.topic: conceptual ms.topic: conceptual
@ -33,7 +33,7 @@ In the **Website learning report**, you can view a summary of the devices that h
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431). 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
1. Click **Client apps** > **App protection status** > **Reports**. 1. Select **Apps** > **Monitor** > **App protection status** > **Reports**.
![Image showing the UI path to the WIP report.](images/access-wip-learning-report.png) ![Image showing the UI path to the WIP report.](images/access-wip-learning-report.png)

View File

@ -14,7 +14,7 @@ author: jgeurten
ms.reviewer: jsuther1974 ms.reviewer: jsuther1974
ms.author: dansimp ms.author: dansimp
manager: dansimp manager: dansimp
ms.date: 11/29/2021 ms.date: 03/22/2022
ms.technology: windows-sec ms.technology: windows-sec
--- ---
@ -26,7 +26,7 @@ In this article we explain:
1. File Rule Precedence Order 1. File Rule Precedence Order
2. Adding Allow Rules 2. Adding Allow Rules
3. Singe Policy Considerations 3. Single Policy Considerations
4. Multiple Policy Considerations 4. Multiple Policy Considerations
5. Best Practices 5. Best Practices
6. Tutorial 6. Tutorial