From 4e442c064c2a27a01458f1df2a90b0883f6141cb Mon Sep 17 00:00:00 2001 From: msarcletti <56821677+msarcletti@users.noreply.github.com> Date: Fri, 12 May 2023 12:49:18 +0200 Subject: [PATCH 01/11] Update-ProfileList-in-vpnv2-csp.md ProfileList - added some description, usage information and an example on how to use it. --- windows/client-management/mdm/vpnv2-csp.md | 41 +++++++++++++++++++--- 1 file changed, 36 insertions(+), 5 deletions(-) diff --git a/windows/client-management/mdm/vpnv2-csp.md b/windows/client-management/mdm/vpnv2-csp.md index 84b7a6c4ec..191bbe2977 100644 --- a/windows/client-management/mdm/vpnv2-csp.md +++ b/windows/client-management/mdm/vpnv2-csp.md @@ -2785,6 +2785,9 @@ Required for native profiles. Type of tunneling protocol used. | Automatic | Automatic. | | SSTP | SSTP. | | ProtocolList | ProtocolList. | + +> [!NOTE] +> Using ProtocolList requires additional configuration of the NativeProfile/ProtocolList parameter. @@ -2887,11 +2890,13 @@ True: Plumb traffic selectors as routes onto VPN interface, False: Do not plumb -List of inbox VPN protocols in priority order. +List of inbox VPN protocols in priority order. Up to 4 VPN protocols are supported. +> [!NOTE] +> A separate entry is needed for every VPN protocol. Please see the examples section for the format. @@ -2930,6 +2935,8 @@ List of inbox VPN protocols in priority order. +> [!NOTE] +> A separate entry is needed for every VPN protocol. Please see the examples section for the format. @@ -2969,6 +2976,8 @@ Inbox VPN protocols type. +> [!NOTE] +> A separate entry is needed for every VPN protocol. Please see the examples section for the format. @@ -3014,11 +3023,13 @@ Inbox VPN protocols type. -Default 168, max 500000. +Default 168, max 500000, min 0 +RetryTimeInHours specifies the length of time Windows will try to use the last succesful protocol first when making a new connection. +Setting this to 0 disables remembering the last successful protocol. @@ -7010,6 +7021,9 @@ Required for native profiles. Type of tunneling protocol used. | Automatic | Automatic. | | SSTP | SSTP. | | ProtocolList | ProtocolList. | + +> [!NOTE] +> Using ProtocolList requires additional configuration of the NativeProfile/ProtocolList parameter. @@ -7112,11 +7126,13 @@ True: Plumb traffic selectors as routes onto VPN interface, False: Do not plumb -List of inbox VPN protocols in priority order. +List of inbox VPN protocols in priority order. Up to 4 VPN protocols are supported. +> [!NOTE] +> A separate entry is needed for every VPN protocol. Please see the examples section for the format. @@ -7155,6 +7171,8 @@ List of inbox VPN protocols in priority order. +> [!NOTE] +> A separate entry is needed for every VPN protocol. Please see the examples section for the format. @@ -7194,6 +7212,8 @@ Inbox VPN protocols type. +> [!NOTE] +> A separate entry is needed for every VPN protocol. Please see the examples section for the format. @@ -7239,11 +7259,13 @@ Inbox VPN protocols type. -Default 168, max 500000. +Default 168, max 500000, min 0 +RetryTimeInHours specifies the length of time Windows will try to use the last succesful protocol first when making a new connection. +Setting this to 0 disables remembering the last successful protocol. @@ -8994,7 +9016,16 @@ Profile example VPN_Demo VPNServer.contoso.com - Automatic + ProtocolList + + + Ikev2 + + + Sstp + + 1 + Eap From 58b9af4295930cd2b4828ebd4765a08491432d2c Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Mon, 15 May 2023 11:08:38 -0700 Subject: [PATCH 02/11] Updates to Tenant management --- .../windows-autopatch-maintain-environment.md | 45 ++++++++++++++++--- .../windows-autopatch-whats-new-2023.md | 6 ++- 2 files changed, 43 insertions(+), 8 deletions(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md index 8ac2a90c62..bd1d000e00 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md @@ -1,7 +1,7 @@ --- title: Maintain the Windows Autopatch environment description: This article details how to maintain the Windows Autopatch environment -ms.date: 07/11/2022 +ms.date: 05/15/2023 ms.prod: windows-client ms.technology: itpro-updates ms.topic: how-to @@ -9,7 +9,10 @@ ms.localizationpriority: medium author: tiaraquan ms.author: tiaraquan manager: dougeby -ms.reviewer: hathind +ms.reviewer: smithcharles +ms.collection: + - highpri + - tier1 --- # Maintain the Windows Autopatch environment @@ -26,18 +29,20 @@ After you've completed enrollment in Windows Autopatch, some management settings | Setting | Description | | ----- | ----- | -| Deployment rings for Windows 10 or later | For any deployment rings for Windows 10 or later policies you've created, exclude the **Modern Workplace Devices - All** Azure AD group from each policy. For more information, see [Create and assign deployment rings](/mem/intune/protect/windows-10-update-rings#create-and-assign-update-rings).

Windows Autopatch will also have created some update ring policies. all of which The policies will have "**Modern Workplace**" in the name. For example:

  • Modern Workplace Update Policy [Broad]-[Windows Autopatch]
  • Modern Workplace Update Policy [Fast]-[Windows Autopatch]
  • Modern Workplace Update Policy [First]-[Windows Autopatch]
  • Modern Workplace Update Policy [Test]-[Windows Autopatch]

When you update your own policies, ensure that you don't exclude the **Modern Workplace Devices - All** Azure AD group from the policies that Windows Autopatch created.

**To resolve the Not ready result:**

After enrolling into Autopatch, make sure that any update ring policies you have **exclude** the **Modern Workplace Devices - All** Azure Active Directory (AD) group.For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).

**To resolve the Advisory result:**

  1. Make sure that any update ring policies you have **exclude** the **Modern Workplace Devices - All** Azure Active Directory (AD) group.
  2. If you have assigned Azure AD user groups to these policies, make sure that any update ring policies you have also **exclude** the **Modern Workplace - All** Azure AD group that you add your Windows Autopatch users to (or an equivalent group).

For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).

| +| Deployment rings for Windows 10 or later | For any deployment rings for Windows 10 or later policies you've created, exclude the **Modern Workplace Devices - All** Azure AD group from each policy. For more information, see [Create and assign deployment rings](/mem/intune/protect/windows-10-update-rings#create-and-assign-update-rings).

Windows Autopatch creates some update ring policies. These policies have "**Modern Workplace**" in the name. For example:

  • Modern Workplace Update Policy [Broad]-[Windows Autopatch]
  • Modern Workplace Update Policy [Fast]-[Windows Autopatch]
  • Modern Workplace Update Policy [First]-[Windows Autopatch]
  • Modern Workplace Update Policy [Test]-[Windows Autopatch]

When you update your own policies, ensure that you don't exclude the **Modern Workplace Devices - All** Azure AD group from the policies that Windows Autopatch created.

**To resolve the Not ready result:**

After enrolling into Autopatch, make sure that any update ring policies you have **exclude** the **Modern Workplace Devices - All** Azure Active Directory (AD) group. For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).

**To resolve the Advisory result:**

  1. Make sure that any update ring policies you have **exclude** the **Modern Workplace Devices - All** Azure Active Directory (AD) group.
  2. If you have assigned Azure AD user groups to these policies, make sure that any update ring policies you have also **exclude** the **Modern Workplace - All** Azure AD group that you add your Windows Autopatch users to (or an equivalent group).

For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).

| ## Windows Autopatch configurations Windows Autopatch deploys, manages and maintains all configurations related to the operation of the service, as described in [Changes made at tenant enrollment](../references/windows-autopatch-changes-to-tenant.md). Don't make any changes to any of the Windows Autopatch configurations. -## Windows Autopatch tenant actions +## Windows Autopatch tenant management -The **Tenant management** blade can be found by navigating to Tenant administration > Windows Autopatch > **Tenant management**. +### Windows Autopatch tenant actions + +The Tenant management blade presents IT admins with any actions that are required to maintain Windows Autopatch service health. The **Tenant management** blade can be found by navigating to **Tenant administration** > **Windows Autopatch** > **Tenant management**. > [!IMPORTANT] -> Starting October 12, 2022, Windows Autopatch will manage your tenant with our [enterprise applications](../references/windows-autopatch-changes-to-tenant.md#windows-autopatch-enterprise-applications). If your tenant is still using the [Windows Autopatch service accounts](../overview/windows-autopatch-privacy.md#service-accounts), your Global admin must go to the Tenant management blade to approve the configuration change. +> If you have any critical actions in your tenant, you must take action as soon as possible as the Windows Autopatch service might not be able to manage your tenant. When a critical action is active on your tenant, Windows Autopatch will consider your tenant as **[inactive](#inactive-status)**. The type of banner that appears depends on the severity of the action. Currently, only critical actions are listed. @@ -45,4 +50,30 @@ The type of banner that appears depends on the severity of the action. Currently | Severity | Description | | ----- | ----- | -| Critical | You must take action as soon as possible. If no action is taken, the Windows Autopatch service may be affected. | +| Critical | You must take action as soon as possible to avoid disruption to the Windows Autopatch service.

If no action is taken, Windows Autopatch might not be able to manage devices in your tenant, and the Windows Autopatch service may be marked as **inactive**.

To restore service health and return to an active status, all critical pending actions must be resolved.

| + +### Critical actions + +| Action type | Severity | Description | +| ----- | ----- | ----- | +| Maintain tenant access | Critical | Required licenses have expired. The licenses include:
  • Microsoft Intune
  • Azure Active Directory Premium
  • Windows 10/11 Enterprise E3 or higher
    • For more information about specific services plans, see [Windows Autopatch Prerequisites](../prepare/windows-autopatch-prerequisites.md)

    To take action on missing licenses, you can visit the Microsoft 365 admin center or contact your Microsoft account manager. Until you have renewed the required licenses to run the service, Windows Autopatch marks your tenant as **inactive**. For more information, see [Microsoft 365 - What happens after my subscription expires?](/microsoft-365/commerce/subscriptions/what-if-my-subscription-expires)

    | +| Maintain tenant access | Critical | Address tenant access issues. Windows Autopatch currently can’t manage your tenant. Until you take action, your tenant is marked as **inactive**, and you have only limited access to the Windows Autopatch portal.

    Reasons for tenant access issues:

    • You haven't yet migrated to the new [Windows Autopatch enterprise application](../references/windows-autopatch-changes-to-tenant#windows-autopatch-enterprise-applications). Windows Autopatch uses this enterprise application to run the service.
    • You have blocked or removed the permissions required for the Windows Autopatch enterprise application.

    Take action by consenting to allow Windows Autopatch to make the appropriate changes on your behalf. You must be a Global Administrator to consent to this action. Once you provide consent, Windows Autopatch remediates this critical action for you.

    For more information, see [Windows Autopatch enterprise applications](../overview/windows-autopatch-privacy.md#tenant-access).

    | + +### Inactive status + +> [!NOTE] +> Only the Windows Autopatch sections of your tenant will be marked as **inactive** if you must perform of the [critical actions](#critical-actions-in-windows-autopatch). + +When Windows Autopatch is **inactive**, you're alerted with banners on all Windows Autopatch blades. You only have access to the Tenant management and Support requests blades. All other blades return an error message and redirect you to Tenant management blade. + +To be taken out of the **inactive** status, you must [resolve any critical actions shown in the Tenant management blade](#critical-actions). + +> [!NOTE] +> Once critical actions are resolved, it can take up to two hours for Windows Autopatch to return to an **active** state. + +#### Impact to your tenant + +| Impact area | Description | +| ----- | ----- | +| Management | Windows Autopatch isn’t able to manage your tenant and perform non-interactive actions we use to run the service. Non-interactive actions include:
    • Managing the Windows Autopatch service
    • Publishing the baseline configuration updates to your tenant’s devices
    • Maintaining overall service health

    For more information, see [Windows Autopatch enterprise applications](../references/windows-autopatch-changes-to-tenant#windows-autopatch-enterprise-applications)

    | +| Device updates | Changes to Windows Autopatch policies aren't pushed to your devices. The existing configurations on these devices remain unchanged, and they continue receiving updates. | diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md index a279da8f47..d8f62e1e64 100644 --- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md +++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md @@ -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: 05/01/2023 +ms.date: 05/15/2023 ms.prod: windows-client ms.technology: itpro-updates ms.topic: whats-new @@ -10,6 +10,9 @@ author: tiaraquan ms.author: tiaraquan manager: dougeby ms.reviewer: hathind +ms.collection: + - highpri + - tier1 --- # What's new 2023 @@ -24,6 +27,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed. | Article | Description | | ----- | ----- | +| [Maintain the Windows Autopatch environment](../operate/windows-autopatch-maintain-environment.md) | Updated the following sections:
    • Tenant actions
    • Tenant action severity types
    • Critical actions

    Added the [Inactive status](../operate/windows-autopatch-maintain-environment.md#inactive-status) section

    | [Device registration overview](../deploy/windows-autopatch-device-registration-overview.md) | Updated article to include Windows Autopatch groups. The Windows Autopatch groups feature is in public preview | | [Register your devices](../deploy/windows-autopatch-register-devices.md) | Updated article to include Windows Autopatch groups. The Windows Autopatch groups feature is in public preview | | [Windows Autopatch groups overview](../deploy/windows-autopatch-groups-overview.md) | New article for the Windows Autopatch groups experience. Windows Autopatch groups is in public preview | From 8bcb4574d97a92e9478c7b090a6c71097959b030 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Mon, 15 May 2023 11:10:36 -0700 Subject: [PATCH 03/11] Tweak --- .../operate/windows-autopatch-maintain-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md index bd1d000e00..dc68beb3ff 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md @@ -62,7 +62,7 @@ The type of banner that appears depends on the severity of the action. Currently ### Inactive status > [!NOTE] -> Only the Windows Autopatch sections of your tenant will be marked as **inactive** if you must perform of the [critical actions](#critical-actions-in-windows-autopatch). +> Only the Windows Autopatch sections of your tenant will be marked as **inactive**. When Windows Autopatch is **inactive**, you're alerted with banners on all Windows Autopatch blades. You only have access to the Tenant management and Support requests blades. All other blades return an error message and redirect you to Tenant management blade. From 9737d36883973246537a139910aa0eceacbbdebd Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Mon, 15 May 2023 11:20:04 -0700 Subject: [PATCH 04/11] Fixed link --- .../operate/windows-autopatch-maintain-environment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md index dc68beb3ff..a68d16d1f0 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md @@ -57,7 +57,7 @@ The type of banner that appears depends on the severity of the action. Currently | Action type | Severity | Description | | ----- | ----- | ----- | | Maintain tenant access | Critical | Required licenses have expired. The licenses include:
    • Microsoft Intune
    • Azure Active Directory Premium
    • Windows 10/11 Enterprise E3 or higher
      • For more information about specific services plans, see [Windows Autopatch Prerequisites](../prepare/windows-autopatch-prerequisites.md)

      To take action on missing licenses, you can visit the Microsoft 365 admin center or contact your Microsoft account manager. Until you have renewed the required licenses to run the service, Windows Autopatch marks your tenant as **inactive**. For more information, see [Microsoft 365 - What happens after my subscription expires?](/microsoft-365/commerce/subscriptions/what-if-my-subscription-expires)

      | -| Maintain tenant access | Critical | Address tenant access issues. Windows Autopatch currently can’t manage your tenant. Until you take action, your tenant is marked as **inactive**, and you have only limited access to the Windows Autopatch portal.

      Reasons for tenant access issues:

      • You haven't yet migrated to the new [Windows Autopatch enterprise application](../references/windows-autopatch-changes-to-tenant#windows-autopatch-enterprise-applications). Windows Autopatch uses this enterprise application to run the service.
      • You have blocked or removed the permissions required for the Windows Autopatch enterprise application.

      Take action by consenting to allow Windows Autopatch to make the appropriate changes on your behalf. You must be a Global Administrator to consent to this action. Once you provide consent, Windows Autopatch remediates this critical action for you.

      For more information, see [Windows Autopatch enterprise applications](../overview/windows-autopatch-privacy.md#tenant-access).

      | +| Maintain tenant access | Critical | Address tenant access issues. Windows Autopatch currently can’t manage your tenant. Until you take action, your tenant is marked as **inactive**, and you have only limited access to the Windows Autopatch portal.

      Reasons for tenant access issues:

      • You haven't yet migrated to the new [Windows Autopatch enterprise application](../references/windows-autopatch-changes-to-tenant.md#windows-autopatch-enterprise-applications). Windows Autopatch uses this enterprise application to run the service.
      • You have blocked or removed the permissions required for the Windows Autopatch enterprise application.

      Take action by consenting to allow Windows Autopatch to make the appropriate changes on your behalf. You must be a Global Administrator to consent to this action. Once you provide consent, Windows Autopatch remediates this critical action for you.

      For more information, see [Windows Autopatch enterprise applications](../overview/windows-autopatch-privacy.md#tenant-access).

      | ### Inactive status @@ -75,5 +75,5 @@ To be taken out of the **inactive** status, you must [resolve any critical actio | Impact area | Description | | ----- | ----- | -| Management | Windows Autopatch isn’t able to manage your tenant and perform non-interactive actions we use to run the service. Non-interactive actions include:
      • Managing the Windows Autopatch service
      • Publishing the baseline configuration updates to your tenant’s devices
      • Maintaining overall service health

      For more information, see [Windows Autopatch enterprise applications](../references/windows-autopatch-changes-to-tenant#windows-autopatch-enterprise-applications)

      | +| Management | Windows Autopatch isn’t able to manage your tenant and perform non-interactive actions we use to run the service. Non-interactive actions include:
      • Managing the Windows Autopatch service
      • Publishing the baseline configuration updates to your tenant’s devices
      • Maintaining overall service health

      For more information, see [Windows Autopatch enterprise applications](../references/windows-autopatch-changes-to-tenant.md#windows-autopatch-enterprise-applications)

      | | Device updates | Changes to Windows Autopatch policies aren't pushed to your devices. The existing configurations on these devices remain unchanged, and they continue receiving updates. | From 96277b0cd8cad7fb7c4ecde2ef3ab5a7c01aff2d Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Mon, 15 May 2023 11:27:17 -0700 Subject: [PATCH 05/11] Added MC post number --- .../whats-new/windows-autopatch-whats-new-2023.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md index d8f62e1e64..748ea707ab 100644 --- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md +++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md @@ -27,7 +27,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed. | Article | Description | | ----- | ----- | -| [Maintain the Windows Autopatch environment](../operate/windows-autopatch-maintain-environment.md) | Updated the following sections:
      • Tenant actions
      • Tenant action severity types
      • Critical actions

      Added the [Inactive status](../operate/windows-autopatch-maintain-environment.md#inactive-status) section

      +| [Maintain the Windows Autopatch environment](../operate/windows-autopatch-maintain-environment.md) | Updated the following sections:
      • Tenant actions
      • Tenant action severity types
      • Critical actions

      Added the [Inactive status](../operate/windows-autopatch-maintain-environment.md#inactive-status) section

      • [MC536881](https://admin.microsoft.com/adminportal/home#/MessageCenter)
      | | [Device registration overview](../deploy/windows-autopatch-device-registration-overview.md) | Updated article to include Windows Autopatch groups. The Windows Autopatch groups feature is in public preview | | [Register your devices](../deploy/windows-autopatch-register-devices.md) | Updated article to include Windows Autopatch groups. The Windows Autopatch groups feature is in public preview | | [Windows Autopatch groups overview](../deploy/windows-autopatch-groups-overview.md) | New article for the Windows Autopatch groups experience. Windows Autopatch groups is in public preview | @@ -75,7 +75,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed. | ----- | ----- | | [Windows quality update communications](../operate/windows-autopatch-windows-quality-update-communications.md#standard-communications) | Added guidance on how to [opt out of receiving emails for standard communications](../operate/windows-autopatch-windows-quality-update-communications.md#opt-out-of-receiving-emails-for-standard-communications) (public preview) | | [Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md) |
      • Added support for subscription versions of Microsoft Project and Visio desktop apps
      • Updated device eligibility criteria
      • Clarified update controls
      | -| [Customize Windows Update settings](../operate/windows-autopatch-windows-update.md) | New [Customize Windows Update settings](../operate/windows-autopatch-windows-update.md) feature. This feature is in public preview
    • [MC524715](https://admin.microsoft.com/adminportal/home#/MessageCenter)
      • | +| [Customize Windows Update settings](../operate/windows-autopatch-windows-update.md) | New [Customize Windows Update settings](../operate/windows-autopatch-windows-update.md) feature. This feature is in public preview
      • [MC524715](https://admin.microsoft.com/adminportal/home#/MessageCenter)
      | ### March service release From e4d037a9f6dd9047cd340a54df0607cc68656871 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Mon, 15 May 2023 11:29:05 -0700 Subject: [PATCH 06/11] MC post number --- .../whats-new/windows-autopatch-whats-new-2023.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md index 748ea707ab..b4fb65849a 100644 --- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md +++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md @@ -6,7 +6,7 @@ ms.prod: windows-client ms.technology: itpro-updates ms.topic: whats-new ms.localizationpriority: medium -author: tiaraquan +author: tiaraquan ms.author: tiaraquan manager: dougeby ms.reviewer: hathind From b4f8948ac9c600516fc3964a8ff4c26c48cc2dfd Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Mon, 15 May 2023 11:39:46 -0700 Subject: [PATCH 07/11] Nitpicky --- .../operate/windows-autopatch-maintain-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md index a68d16d1f0..cab93e35da 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md +++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-maintain-environment.md @@ -75,5 +75,5 @@ To be taken out of the **inactive** status, you must [resolve any critical actio | Impact area | Description | | ----- | ----- | -| Management | Windows Autopatch isn’t able to manage your tenant and perform non-interactive actions we use to run the service. Non-interactive actions include:
      • Managing the Windows Autopatch service
      • Publishing the baseline configuration updates to your tenant’s devices
      • Maintaining overall service health

      For more information, see [Windows Autopatch enterprise applications](../references/windows-autopatch-changes-to-tenant.md#windows-autopatch-enterprise-applications)

      | +| Management | Windows Autopatch isn’t able to manage your tenant and perform non-interactive actions we use to run the service. Non-interactive actions include:
      • Managing the Windows Autopatch service
      • Publishing the baseline configuration updates to your tenant’s devices
      • Maintaining overall service health

      For more information, see [Windows Autopatch enterprise applications](../references/windows-autopatch-changes-to-tenant.md#windows-autopatch-enterprise-applications).

      | | Device updates | Changes to Windows Autopatch policies aren't pushed to your devices. The existing configurations on these devices remain unchanged, and they continue receiving updates. | From e0e5efed6d8f7a50ed1afc2f75a05884bd7263c2 Mon Sep 17 00:00:00 2001 From: msarcletti <56821677+msarcletti@users.noreply.github.com> Date: Tue, 16 May 2023 17:15:20 +0200 Subject: [PATCH 08/11] Update vpnv2-csp.md --- windows/client-management/mdm/vpnv2-csp.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/client-management/mdm/vpnv2-csp.md b/windows/client-management/mdm/vpnv2-csp.md index 191bbe2977..54e08d2b0f 100644 --- a/windows/client-management/mdm/vpnv2-csp.md +++ b/windows/client-management/mdm/vpnv2-csp.md @@ -2763,6 +2763,8 @@ Required for native profiles. Type of tunneling protocol used. +> [!NOTE] +> Using ProtocolList requires additional configuration of the NativeProfile/ProtocolList parameter. @@ -2786,8 +2788,6 @@ Required for native profiles. Type of tunneling protocol used. | SSTP | SSTP. | | ProtocolList | ProtocolList. | -> [!NOTE] -> Using ProtocolList requires additional configuration of the NativeProfile/ProtocolList parameter. @@ -9024,7 +9024,7 @@ Profile example Sstp - 1 + 168 Eap From 7d8344d4ade56ab516b48fbeec6afe859315d7e1 Mon Sep 17 00:00:00 2001 From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com> Date: Tue, 16 May 2023 12:41:00 -0400 Subject: [PATCH 09/11] Update vpnv2-csp.md --- windows/client-management/mdm/vpnv2-csp.md | 31 ++++++++++------------ 1 file changed, 14 insertions(+), 17 deletions(-) diff --git a/windows/client-management/mdm/vpnv2-csp.md b/windows/client-management/mdm/vpnv2-csp.md index 54e08d2b0f..26bfbe35e2 100644 --- a/windows/client-management/mdm/vpnv2-csp.md +++ b/windows/client-management/mdm/vpnv2-csp.md @@ -2764,7 +2764,7 @@ Required for native profiles. Type of tunneling protocol used. > [!NOTE] -> Using ProtocolList requires additional configuration of the NativeProfile/ProtocolList parameter. +> Using NativeProtocolType the NativeProfile/ProtocolList node. @@ -2896,7 +2896,7 @@ List of inbox VPN protocols in priority order. Up to 4 VPN protocols are support > [!NOTE] -> A separate entry is needed for every VPN protocol. Please see the examples section for the format. +> A separate entry is needed for every VPN protocol. For a sample format, see [Examples](#examples). @@ -2936,7 +2936,7 @@ List of inbox VPN protocols in priority order. Up to 4 VPN protocols are support > [!NOTE] -> A separate entry is needed for every VPN protocol. Please see the examples section for the format. +> A separate entry is needed for every VPN protocol. For a sample format, see [Examples](#examples). @@ -2977,7 +2977,7 @@ Inbox VPN protocols type. > [!NOTE] -> A separate entry is needed for every VPN protocol. Please see the examples section for the format. +> A separate entry is needed for every VPN protocol. For a sample format, see [Examples](#examples). @@ -3023,13 +3023,12 @@ Inbox VPN protocols type. -Default 168, max 500000, min 0 +Default 168, max 500000. -RetryTimeInHours specifies the length of time Windows will try to use the last succesful protocol first when making a new connection. -Setting this to 0 disables remembering the last successful protocol. +RetryTimeInHours specifies the length of time Windows tries to use the last succesful protocol when making a new connection. Setting this value to 0 disables remembering the last successful protocol. @@ -6999,6 +6998,8 @@ Required for native profiles. Type of tunneling protocol used. +> [!NOTE] +> Using NativeProtocolType requires additional configuration of the NativeProfile/ProtocolList parameter. @@ -7021,9 +7022,6 @@ Required for native profiles. Type of tunneling protocol used. | Automatic | Automatic. | | SSTP | SSTP. | | ProtocolList | ProtocolList. | - -> [!NOTE] -> Using ProtocolList requires additional configuration of the NativeProfile/ProtocolList parameter. @@ -7126,13 +7124,13 @@ True: Plumb traffic selectors as routes onto VPN interface, False: Do not plumb -List of inbox VPN protocols in priority order. Up to 4 VPN protocols are supported. +List of inbox VPN protocols in priority order. > [!NOTE] -> A separate entry is needed for every VPN protocol. Please see the examples section for the format. +> Up to 4 VPN protocols are supported. A separate entry is needed for every VPN protocol. For a sample format, see [Examples](#examples). @@ -7172,7 +7170,7 @@ List of inbox VPN protocols in priority order. Up to 4 VPN protocols are support > [!NOTE] -> A separate entry is needed for every VPN protocol. Please see the examples section for the format. +> A separate entry is needed for every VPN protocol. For a sample format, see [Examples](#examples). @@ -7213,7 +7211,7 @@ Inbox VPN protocols type. > [!NOTE] -> A separate entry is needed for every VPN protocol. Please see the examples section for the format. +> A separate entry is needed for every VPN protocol. For a sample format, see [Examples](#examples). @@ -7259,13 +7257,12 @@ Inbox VPN protocols type. -Default 168, max 500000, min 0 +Default 168, max 500000. -RetryTimeInHours specifies the length of time Windows will try to use the last succesful protocol first when making a new connection. -Setting this to 0 disables remembering the last successful protocol. +RetryTimeInHours specifies the length of time Windows tries to use the last succesful protocol when making a new connection. Setting this value to 0 disables remembering the last successful protocol. From dae9769c4f4f981270d3ff3ceb71b389278ba6d7 Mon Sep 17 00:00:00 2001 From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com> Date: Tue, 16 May 2023 12:42:55 -0400 Subject: [PATCH 10/11] Update vpnv2-csp.md --- windows/client-management/mdm/vpnv2-csp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/vpnv2-csp.md b/windows/client-management/mdm/vpnv2-csp.md index 26bfbe35e2..3a4374ad36 100644 --- a/windows/client-management/mdm/vpnv2-csp.md +++ b/windows/client-management/mdm/vpnv2-csp.md @@ -2764,7 +2764,7 @@ Required for native profiles. Type of tunneling protocol used. > [!NOTE] -> Using NativeProtocolType the NativeProfile/ProtocolList node. +> Using NativeProtocolType requires additional configuration of the NativeProfile/ProtocolList parameter. From 5676cc0e475c8f9e038229899246d4c8de60b930 Mon Sep 17 00:00:00 2001 From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com> Date: Tue, 16 May 2023 12:44:51 -0400 Subject: [PATCH 11/11] Update vpnv2-csp.md --- windows/client-management/mdm/vpnv2-csp.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/windows/client-management/mdm/vpnv2-csp.md b/windows/client-management/mdm/vpnv2-csp.md index 3a4374ad36..842a59643a 100644 --- a/windows/client-management/mdm/vpnv2-csp.md +++ b/windows/client-management/mdm/vpnv2-csp.md @@ -2787,7 +2787,6 @@ Required for native profiles. Type of tunneling protocol used. | Automatic | Automatic. | | SSTP | SSTP. | | ProtocolList | ProtocolList. | - @@ -2890,13 +2889,13 @@ True: Plumb traffic selectors as routes onto VPN interface, False: Do not plumb -List of inbox VPN protocols in priority order. Up to 4 VPN protocols are supported. +List of inbox VPN protocols in priority order. > [!NOTE] -> A separate entry is needed for every VPN protocol. For a sample format, see [Examples](#examples). +> Up to 4 VPN protocols are supported. A separate entry is needed for every VPN protocol. For a sample format, see [Examples](#examples).