mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 20:33:42 +00:00
Merge branch 'main' of github.com:MicrosoftDocs/windows-docs-pr into pm-7847341-bitlocker-refresh
This commit is contained in:
Paolo Matarazzo
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Microsoft 365 Apps for enterprise
|
||||
description: This article explains how Windows Autopatch manages Microsoft 365 Apps for enterprise updates
|
||||
ms.date: 06/23/2023
|
||||
ms.date: 10/27/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -81,7 +81,15 @@ Windows Autopatch doesn't allow you to pause or roll back an update in the Micro
|
||||
|
||||
## Allow or block Microsoft 365 App updates
|
||||
|
||||
For organizations seeking greater control, you can allow or block Microsoft 365 App updates for Windows Autopatch-enrolled devices. When the Microsoft 365 App update setting is set to **Block**, Windows Autopatch doesn't provide Microsoft 365 App updates on your behalf, and your organizations have full control over these updates. For example, you can continue to receive updates from [channels](/deployoffice/overview-update-channels) other than the default [Monthly Enterprise Channel](/deployoffice/overview-update-channels#monthly-enterprise-channel-overview).
|
||||
> [!IMPORTANT]
|
||||
> You must be an Intune Administrator to make changes to the setting.
|
||||
|
||||
For organizations seeking greater control, you can allow or block Microsoft 365 App updates for Windows Autopatch-enrolled devices.
|
||||
|
||||
| Microsoft 365 App setting | Description |
|
||||
| ----- | ----- |
|
||||
| **Allow** | When set to **Allow**, Windows Autopatch moves all Autopatch managed devices to the [Monthly Enterprise Channel](/deployoffice/overview-update-channels#monthly-enterprise-channel-overview) and manages updates automatically. To manage updates manually, set the Microsoft 365 App update setting to **Block**. |
|
||||
| **Block** | When set to **Block**, Windows Autopatch doesn't provide Microsoft 365 App updates on your behalf, and your organizations have full control over these updates. You can continue to receive updates from [channels](/deployoffice/overview-update-channels) other than the default [Monthly Enterprise Channel](/deployoffice/overview-update-channels#monthly-enterprise-channel-overview). |
|
||||
|
||||
**To allow or block Microsoft 365 App updates:**
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2023
|
||||
description: This article lists the 2023 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 10/19/2023
|
||||
ms.date: 10/27/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: whats-new
|
||||
@ -23,6 +23,12 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
|
||||
## October 2023
|
||||
|
||||
### October feature releases or updates
|
||||
|
||||
| Article | Description |
|
||||
| ----- | ----- |
|
||||
| [Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#microsoft-365-apps-for-enterprise-update-controls) | Added more information about the Allow setting in the [Microsoft 365 Apps for enterprise update controls](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#microsoft-365-apps-for-enterprise-update-controls) section |
|
||||
|
||||
## October service release
|
||||
|
||||
| Message center post number | Description |
|
||||
|
||||
@ -190,7 +190,7 @@ sections:
|
||||
Windows Hello for Business is two-factor authentication based on the observed authentication factors of: *something you have*, *something you know*, and *something that's part of you*. Windows Hello for Business incorporates two of these factors: something you have (the user's private key protected by the device's security module) and something you know (your PIN). With the proper hardware, you can enhance the user experience by introducing biometrics. By using biometrics, you can replace the "something you know" authentication factor with the "something that is part of you" factor, with the assurances that users can fall back to the "something you know factor".
|
||||
|
||||
> [!NOTE]
|
||||
> The Windows Hello for Business key meets Azure AD multifactor authentication (MFA) requirements and reduces the number of MFA prompts users will see when accessing resources. For more information, see [What is a Primary Refresh Token](/azure/active-directory/devices/concept-primary-refresh-token#when-does-a-prt-get-an-mfa-claim).
|
||||
> The Windows Hello for Business key meets Microsoft Entra multifactor authentication (MFA) requirements and reduces the number of MFA prompts users will see when accessing resources. For more information, see [What is a Primary Refresh Token](/azure/active-directory/devices/concept-primary-refresh-token#when-does-a-prt-get-an-mfa-claim).
|
||||
- question: Which is a better or more secure for of authentication, key or certificate?
|
||||
answer: |
|
||||
Both types of authentication provide the same security; one is not more secure than the other.
|
||||
|
||||
@ -31,7 +31,7 @@ Microsoft Entra joined devices authenticate to Microsoft Entra ID during sign-in
|
||||
|
||||
## Microsoft Entra join authentication to Active Directory using cloud Kerberos trust
|
||||
|
||||
|
||||
|
||||
|
||||
| Phase | Description |
|
||||
| :----: | :----------- |
|
||||
|
||||
@ -42,7 +42,7 @@ Hybrid Windows Hello for Business needs two directories:
|
||||
- An on-premises Active Directory
|
||||
- A Microsoft Entra tenant
|
||||
|
||||
The two directories must be synchronized with [Microsoft Entra Connect Sync][AZ-1], which synchronizes user accounts from the on-premises Active Directory to Azure AD.\
|
||||
The two directories must be synchronized with [Microsoft Entra Connect Sync][AZ-1], which synchronizes user accounts from the on-premises Active Directory to Microsoft Entra ID.\
|
||||
During the Window Hello for Business provisioning process, users register the public portion of their Windows Hello for Business credential with Microsoft Entra ID. *Microsoft Entra Connect Sync* synchronizes the Windows Hello for Business public key to Active Directory.
|
||||
|
||||
> [!NOTE]
|
||||
|
||||
@ -25,7 +25,7 @@ This article describes how to configure Web sign-in and the supported key scenar
|
||||
To use web sign-in, the clients must meet the following prerequisites:
|
||||
|
||||
- Windows 11, version 22H2 with [5030310][KB-1], or later
|
||||
- Must be Microsoft Entra joined
|
||||
- Must be [Microsoft Entra joined](/entra/identity/devices/concept-directory-join)
|
||||
- Must have Internet connectivity, as the authentication is done over the Internet
|
||||
|
||||
[!INCLUDE [federated-sign-in](../../../../includes/licensing/web-sign-in.md)]
|
||||
|
||||
Reference in New Issue
Block a user