Merge pull request #294974 from ju-shim/patch-1

Update quickstart-create-portal.md

Author: JillGrant615

articles/azure-compute-fleet/quickstart-create-portal.md

@@ -7,7 +7,7 @@ ms.topic: how-to
 ms.service: azure-compute-fleet
 ms.custom:
   - build-2024
-ms.date: 11/13/2024
+ms.date: 02/19/2025
 ms.reviewer: jushiman
 ---
 
@@ -16,7 +16,7 @@ ms.reviewer: jushiman
 > [!IMPORTANT]
 > Azure Compute Fleet is currently in preview. Previews are made available to you on the condition that you agree to the [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Some aspects of this feature may change prior to general availability (GA). 
 
-This article steps through using Azure portal to create a Compute Fleet.
+This article steps through using the Azure portal to create a Compute Fleet.
 
 
 ## Log in to Azure
@@ -28,20 +28,25 @@ Sign in to the [Azure portal](https://portal.azure.com).
 
 You can deploy a Compute Fleet with a Windows Server image or Linux image such as RHEL, CentOS, Ubuntu, or SLES.
 
-1. In the Azure portal search bar, search for **Azure Compute Fleet** and select the result under *Marketplace*.
+1. In the Azure portal search bar, search for **Compute Fleet** and select the result under *Marketplace*.
 1. Select **Create** on the **Compute Fleet** page. 
 
 1. In the **Basics** tab, under **Project details**, make sure the correct subscription is selected and create a new resource group called *myFleetResourceGroup*. 
 1. Under **Instance details**, set *myFleet* for your Compute Fleet name.
 1. Select a **Region** that is close to your area.
-1. Select a marketplace image for **Image**. 
+1. Select an option from **Availability zones** or a qualified availability zone will be automatically picked up for you.
+1. Select a **Security type** that is available for a Virtual Machine (VM).
+1. Select a marketplace image for **Image**.
+1. Select **Architecture** for your VM. Available options are `Arm64` or `x64`.  
 1. For **Virtual machine types**, select whether you're deploying Spot VMs, Standard VMs, or both. In this example, we select both. 
-1. Specify 3 to 15 virtual machine (VM) sizes for **Sizes**.
+1. Specify 3 to 15 VM sizes for **Sizes**.
 1. **For Spot fleet deployment:** Under **VM capacity**, specify your target capacity for Spot VM instance count between 1 and 10,000.
-1. **For Standard fleet deployment:** Under **VM capacity**, specify your target capacity for Standard VM instance count between 1 and 10,000. 
+1. **For Standard fleet deployment:** Under **VM capacity**, specify your target capacity for Standard VM instance count between 1 and 10,000.
+1. Select **Allocation strategy** to what factors you would like to prioritize when procuring VM size.
+1. Enter the **Max hourly price per Spot VM (USD)**. Note that Spot VMs above your maximum hourly price will be evicted. 
 
 1. Under **Administrator account** configure the admin username and set up an associated password or SSH public key.
-   - A **Password** must be at least 12 characters long and meet three out of the four following complexity requirements: one lower case character, one upper case character, one number, and one special character. For more information, see [username and password requirements](/azure/virtual-machines/windows/faq#what-are-the-password-requirements-when-creating-a-vm-).
+   - A **Password** must be at least 12 characters long and meet three out of the four following complexity requirements: one lowercase character, one uppercase character, one number, and one special character. For more information, see [username and password requirements](/azure/virtual-machines/windows/faq#what-are-the-password-requirements-when-creating-a-vm-).
    - If you select a Linux OS disk image, you can instead choose **SSH public key**. You can use an existing key or create a new one. In this example, Azure generates a new key pair for us. For more information on generating key pairs, see [create and use SSH keys](/azure/virtual-machines/linux/mac-create-ssh-keys).
 
 1. Select **Next: Networking** to move the networking configuration options. For this quickstart, leave the default networking configurations.