Skip to content

Commit 94ee618

Browse files
Merge pull request #16755 from MicrosoftDocs/main
Publish main to live, Monday 10:30AM PST, 11/25
2 parents b624929 + 882a8db commit 94ee618

File tree

4 files changed

+10
-8
lines changed

4 files changed

+10
-8
lines changed

autopilot/requirements.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: frankroj
88
ms.author: frankroj
99
ms.reviewer: jubaptis
1010
manager: aaroncz
11-
ms.date: 09/06/2024
11+
ms.date: 11/25/2024
1212
ms.collection:
1313
- M365-modern-desktop
1414
- highpri
@@ -67,6 +67,7 @@ The following editions of Windows 11 are supported:
6767
- Windows 11 Pro for Workstations.
6868
- Windows 11 Enterprise.
6969
- Windows 11 Education.
70+
- [Windows 11 Enterprise LTSC](/windows/whats-new/ltsc/overview).
7071
7172
#### Windows 10
7273

memdocs/intune/protect/certificates-profile-scep.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ keywords:
55
author: lenewsad
66
ms.author: lanewsad
77
manager: dougeby
8-
ms.date: 11/19/2024
8+
ms.date: 11/25/2024
99
ms.topic: how-to
1010
ms.service: microsoft-intune
1111
ms.subservice: protect
@@ -55,7 +55,8 @@ Devices that run Android Enterprise might require a PIN before SCEP can provisio
5555
**Applies to**:
5656

5757
- Windows 10
58-
- Windows 11
58+
- Windows 11
59+
- Android
5960
- iOS
6061
- macOS
6162

@@ -101,7 +102,7 @@ For more information about the KDC's requirements and enforcement date for stron
101102

102103
1. Under Monitoring, certificate reporting isn't available for **Device Owner** SCEP certificate profiles.
103104
1. You can't use Intune to revoke certificates that were provisioned by SCEP certificate profiles for **Device Owners**. You can manage revocation through an external process or directly with the certification authority.
104-
1. SCEP certificate profiles are supported for Wi-Fi network configuration. VPN configuration profile support isn't available. A future update might include support for VPN configuration profiles.
105+
1. SCEP certificate profiles are supported for Wi-Fi network configuration. VPN configuration profile support isn't available. A future update might include support for VPN configuration profiles.
105106
1. The following variables aren't available for use on Android (AOSP) SCEP certificate profiles. Support for these variables will come in a future update.
106107
- onPremisesSamAccountName
107108
- OnPrem_Distinguished_Name

windows-365/link/deployment-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ ms.collection:
3131

3232
# Windows 365 Link deployment overview
3333

34-
Before users can use their Windows 365 Link to connect to their Cloud PC provided by their organization, admins must set up the organization's Microsoft Entra ID and Intune environments to manage, register, and enroll the device.
34+
Before users can use their Windows 365 Link to connect to their Cloud PC provided by their organization, admins must set up the organization's Microsoft Entra ID and Intune environments to join and enroll the device.
3535

3636
To set up your organization's environment to deploy and manage Windows 365 Link devices, admins must complete the following steps:
3737

@@ -40,7 +40,7 @@ To set up your organization's environment to deploy and manage Windows 365 Link
4040
3. [Configure Microsoft Entra Mobility settings to automatically enroll Windows 365 Link devices in Intune](intune-automatic-enrollment.md).
4141
4. [Create an Intune filter for Windows 365 Link devices](create-intune-filter.md) (optional).
4242
5. [Optimize enrollment restrictions to let Windows 365 Link devices enroll](enrollment-restrictions.md).
43-
6. [Synchronize conditional access policies](conditional-access-policies-synchronize.md).
43+
6. [Validate conditional access policies](conditional-access-policies-synchronize.md).
4444
7. [Suppress single sign-on consent prompt](single-sign-on-suppress.md) (recommended).
4545

4646
After setting up deployment for your Windows 365 Link devices, you can start [onboarding](onboarding.md) them.

windows-365/link/setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,13 +49,13 @@ Complete the following steps to set up your new device:
4949
4. On the **Let's connect you to a network** page, select a network > **Next**.
5050
![Screenshot of network connect page.](media/setup/connect-network.png)
5151
5. On the **Let's set things up for your work or school** page, type your work or school e-mail > **Next**
52-
6[Screenshot of e-mail sign in page.](media/setup/email-sign-in.png)
52+
![Screenshot of e-mail sign in page.](media/setup/email-sign-in.png)
5353
7. Authenticate your account as requested. Your organization defined the authentication method (FIDO2 security key, Passkey (FIDO2), Microsoft Authenticator app, and so on).
5454
8. You're connected to your Cloud PC with all of your context and apps just where you left off.
5555

5656
You can adjust additional settings prior to sign-in by using [Quick settings](quick-settings.md) in the bottom-right corner.
5757

58-
When you sign in for the first time, the Windows 365 Link automatically joins Microsoft Entra ID and enrolls the device into Microsoft Intune tenant associated with the account used to sign in. You organization's admins use Intune to manage both virtual machines and hardware devices, including Windows 365 Link.
58+
When you sign in for the first time, the Windows 365 Link automatically joins Microsoft Entra ID and enrolls the device into Microsoft Intune tenant associated with the account used to sign in. Your organization's admins use Intune to manage both virtual machines and hardware devices, including Windows 365 Link.
5959

6060
<!-- ########################## -->
6161
## Next steps

0 commit comments

Comments
 (0)