Skip to content

Commit ac25630

Browse files
Merge pull request #270340 from wenxiangMS/main
Delete statement for requesting feature flag as it is globally enabled
2 parents 5389edf + e2d034b commit ac25630

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

articles/batch/batch-upgrade-policy.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,13 @@
22
title: Provision a pool with Auto OS Upgrade
33
description: Learn how to create a Batch pool with Auto OS Upgrade so that customers can have control over their OS upgrade strategy to ensure safe, workload-aware OS upgrade deployments.
44
ms.topic: how-to
5-
ms.date: 02/29/2024
5+
ms.date: 03/27/2024
66
ms.custom:
77
---
88

99
# Create an Azure Batch pool with Automatic Operating System (OS) Upgrade
1010

1111
> [!IMPORTANT]
12-
> - Support for pools with Auto OS Upgrade in Azure Batch is currently in public preview, and is currently controlled by an account-level feature flag. If you want to use this feature, please start a [support request](../azure-portal/supportability/how-to-create-azure-support-request.md) and provide your batch account to request its activation.
1312
> - This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
1413
> - For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
1514
@@ -209,10 +208,6 @@ public async Task CreateUpgradePolicyPool()
209208

210209
## FAQs
211210

212-
- How can I enable Auto OS Upgrade?
213-
214-
Start a [support request](../azure-portal/supportability/how-to-create-azure-support-request.md) and provide your batch account to request its activation.
215-
216211
- Will my tasks be disrupted if I enabled Auto OS Upgrade?
217212

218213
Tasks won't be disrupted when *automaticOSUpgradePolicy.osRollingUpgradeDeferral* is set to 'true'. In that case, the upgrade will be postponed until node becomes idle. Otherwise, node will upgrade when it receives a new OS version, regardless of whether it is currently running a task or not. So we strongly advise enabling *automaticOSUpgradePolicy.osRollingUpgradeDeferral*.

0 commit comments

Comments
 (0)