Merge pull request #273083 from MicrosoftDocs/main

4/23/2024 AM Publish

Author: Taojunshen

articles/ai-studio/how-to/deploy-models-llama.md

@@ -6,9 +6,10 @@ manager: scottpolly
 ms.service: azure-ai-studio
 ms.topic: how-to
 ms.date: 3/6/2024
-ms.reviewer: fasantia
-ms.author: mopeakande
-author: msakande
+ms.reviewer: shubhiraj
+reviewer: shubhirajMsft
+ms.author: ssalgado
+author: ssalgadodev
 ms.custom: [references_regions]
 ---
 
@@ -244,7 +245,7 @@ __Body__
 {
     "prompt": "What's the distance to the moon?",
     "temperature": 0.8,
-    "max_tokens": 512,
+    "max_tokens": 512
 }
 ```
 

articles/ai-studio/how-to/fine-tune-model-llama.md

@@ -6,9 +6,10 @@ manager: scottpolly
 ms.service: azure-ai-studio
 ms.topic: how-to
 ms.date: 12/11/2023
-ms.reviewer: eur
-ms.author: mopeakande
-author: msakande
+ms.reviewer: shubhiraj
+reviewer: shubhirajMsft
+ms.author: ssalgado
+author: ssalgadodev
 ms.custom: references_regions
 ---
 

articles/automation/python-packages.md

@@ -3,7 +3,7 @@ title: Manage Python 2 packages in Azure Automation
 description: This article tells how to manage Python 2 packages in Azure Automation.
 services: automation
 ms.subservice: process-automation
-ms.date: 08/21/2023
+ms.date: 04/23/2024
 ms.topic: conceptual
 ms.custom: devx-track-python
 ---

articles/azure-arc/vmware-vsphere/enable-guest-management-at-scale.md

@@ -2,7 +2,7 @@
 title: Install Arc agent at scale for your VMware VMs
 description: Learn how to enable guest management at scale for Arc enabled VMware vSphere VMs. 
 ms.topic: how-to
-ms.date: 03/27/2024
+ms.date: 04/23/2024
 ms.service: azure-arc
 ms.subservice: azure-arc-vmware-vsphere
 author: Farha-Bano
@@ -25,13 +25,16 @@ Ensure the following before you install Arc agents at scale for VMware VMs:
 - The user account must have permissions listed in Azure Arc VMware Administrator role.
 - All the target machines are:
     - Powered on and the resource bridge has network connectivity to the host running the VM.
-    - Running a [supported operating system](../servers/prerequisites.md#supported-operating-systems).
+    - Running a [supported operating system](../servers/prerequisites.md#supported-operating-systems).c
+    - VMware tools are installed on the machines. If VMware tools aren't installed, enable guest management operation is grayed out in the portal.  
+        >[!Note]
+        >You can use the [out-of-band method](./enable-guest-management-at-scale.md#approach-d-install-arc-agents-at-scale-using-out-of-band-approach) to install Arc agents if VMware tools aren't installed.  
     - Able to connect through the firewall to communicate over the internet, and [these URLs](../servers/network-requirements.md#urls) aren't blocked.
 
-      > [!NOTE]
-      > If you're using a Linux VM, the account must not prompt for login on sudo commands. To override the prompt, from a terminal, run `sudo visudo`, and add `<username> ALL=(ALL) NOPASSWD:ALL` at the end of the file. Ensure you replace `<username>`. <br> <br>If your VM template has these changes incorporated, you won't need to do this for the VM created from that template.
+   > [!NOTE]
+   > If you're using a Linux VM, the account must not prompt for login on sudo commands. To override the prompt, from a terminal, run `sudo visudo`, and add `<username> ALL=(ALL) NOPASSWD:ALL` at the end of the file. Ensure you replace `<username>`. <br> <br>If your VM template has these changes incorporated, you won't need to do this for the VM created from that template.
 
-## Install Arc agents at scale from portal
+## Approach A: Install Arc agents at scale from portal
 
 An admin can install agents for multiple machines from the Azure portal if the machines share the same administrator credentials.
 
@@ -53,6 +56,123 @@ An admin can install agents for multiple machines from the Azure portal if the m
 > [!NOTE]
 > For Windows VMs, the account must be part of local administrator group; and for Linux VM, it must be a root account.
 
+## Approach B: Install Arc agents using AzCLI commands
+
+The following Azure CLI commands can be used to install Arc agents.  
+
+```azurecli
+az connectedvmware vm guest-agent enable --password 
+
+                                         --resource-group 
+
+                                         --username 
+
+                                         --vm-name 
+
+                                         [--https-proxy] 
+
+                                         [--no-wait]
+```
+
+## Approach C: Install Arc agents at scale using helper script
+
+Arc agent installation can be automated using the helper script built using the AzCLI command provided [here](./enable-guest-management-at-scale.md#approach-b-install-arc-agents-using-azcli-commands). Download this [helper script](https://aka.ms/arcvmwarebatchenable) to enable VMs and install Arc agents at scale. In a single ARM deployment, the helper script can enable and install Arc agents on 200 VMs.  
+
+### Features of the script
+
+- Creates a log file (vmware-batch.log) for tracking its operations.
+
+- Generates a list of Azure portal links to all the deployments created `(all-deployments-<timestamp>.txt)`. 
+
+- Creates ARM deployment files `(vmw-dep-<timestamp>-<batch>.json)`.
+
+- Can enable up to 200 VMs in a single ARM deployment if guest management is enabled, else enables 400 VMs. 
+
+- Supports running as a cron job to enable all the VMs in a vCenter. 
+
+- Allows for service principal authentication to Azure for automation. 
+
+Before running this script, install az cli and the `connectedvmware` extension. 
+
+### Prerequisites 
+
+Before running this script, install: 
+
+- Azure CLI from [here](/cli/azure/install-azure-cli).
+
+- The `connectedvmware` extension for Azure CLI: Install it by running `az extension add --name connectedvmware`. 
+
+### Usage 
+
+1. Download the script to your local machine. 
+
+2. Open a PowerShell terminal and navigate to the directory containing the script. 
+
+3. Run the following command to allow the script to run, as it's an unsigned script (if you close the session before you complete all the steps, run this command again for the new session): `Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass`.
+
+4. Run the script with the required parameters. For example, `.\arcvmware-batch-enablement.ps1 -VCenterId "<vCenterId>" -EnableGuestManagement -VMCountPerDeployment 3 -DryRun`. Replace `<vCenterId>` with the ARM ID of your vCenter. 
+
+### Parameters
+
+- `VCenterId`: The ARM ID of the vCenter where the VMs are located. 
+
+- `EnableGuestManagement`: If this switch is specified, the script will enable guest management on the VMs. 
+
+- `VMCountPerDeployment`: The number of VMs to enable per ARM deployment. The maximum value is 200 if guest management is enabled, else it's 400. 
+
+- `DryRun`: If this switch is specified, the script will only create the ARM deployment files. Else, the script will also deploy the ARM deployments. 
+
+### Running as a Cron Job 
+
+You can set up this script to run as a cron job using the Windows Task Scheduler. Here's a sample script to create a scheduled task: 
+
+```azurecli
+$action = New-ScheduledTaskAction -Execute 'powershell.exe' -Argument '-File "C:\Path\To\vmware-batch-enable.ps1" -VCenterId "<vCenterId>" -EnableGuestManagement -VMCountPerDeployment 3 -DryRun' 
+$trigger = New-ScheduledTaskTrigger -Daily -At 3am 
+Register-ScheduledTask -Action $action -Trigger $trigger -TaskName "EnableVMs" 
+```
+
+Replace `<vCenterId>` with the ARM ID of your vCenter. 
+
+To unregister the task, run the following command: 
+
+```azurecli
+Unregister-ScheduledTask -TaskName "EnableVMs"
+```
+
+## Approach D: Install Arc agents at scale using out-of-band approach 
+
+Arc agents can be installed directly on machines without relying on VMware tools or APIs. By following the out-of-band approach, first onboard the machines as Arc-enabled Server resources with Resource type as Microsoft.HybridCompute/machines. After that, perform **Link to vCenter** operation to update the machine's Kind property as VMware, enabling virtual lifecycle operations.  
+
+1. **Connect the machines as Arc-enabled Server resources:** Install Arc agents using Arc-enabled Server scripts. 
+
+    You can use any of the following automation approaches to install Arc agents at scale:
+
+   - [Install Arc agents at scale using a Service Principal](../servers/onboard-service-principal.md).
+   - [Install Arc agents at scale using Configuration Manager script](../servers/onboard-configuration-manager-powershell.md).
+   - [Install Arc agents at scale with a Configuration Manager custom task sequence](../servers/onboard-configuration-manager-custom-task.md).
+   - [Install Arc agents at scale using Group policy](../servers/onboard-group-policy-powershell.md).
+   - [Install Arc agents at scale using Ansible playbook](../servers/onboard-ansible-playbooks.md).
+
+2. **Link Arc-enabled Server resources to the vCenter:** The following commands will update the Kind property of Hybrid Compute machines as **VMware**. Linking the machines to vCenter will enable virtual lifecycle operations and power cycle operations (start, stop, etc.) on the machines.  
+
+   - The following command scans all the Arc for Server machines that belong to the vCenter in the specified subscription and links the machines with that vCenter. 
+
+     ```azurecli
+     az connectedvmware vm create-from-machines --subscription contoso-sub --vcenter-id /subscriptions/fedcba98-7654-3210-0123-456789abcdef/resourceGroups/contoso-rg-2/providers/Microsoft.HybridCompute/vcenters/contoso-vcenter
+     ```
+
+   - The following command scans all the Arc for Server machines that belong to the vCenter in the specified Resource Group and links the machines with that vCenter. 
+
+     ```azurecli
+     az connectedvmware vm create-from-machines --resource-group contoso-rg --vcenter-id /subscriptions/fedcba98-7654-3210-0123-456789abcdef/resourceGroups/contoso-rg-2/providers/Microsoft.HybridCompute/vcenters/contoso-vcenter.
+     ```
+
+   - The following command can be used to link an individual Arc for Server resource to vCenter. 
+
+     ```azurecli
+     az connectedvmware vm create-from-machines --resource-group contoso-rg --name contoso-vm --vcenter-id /subscriptions/fedcba98-7654-3210-0123-456789abcdef/resourceGroups/contoso-rg-2/providers/Microsoft.HybridCompute/vcenters/contoso-vcenter
+     ```
 
 ## Next steps
 

articles/azure-arc/vmware-vsphere/support-matrix-for-arc-enabled-vmware-vsphere.md

@@ -2,7 +2,7 @@
 title: Plan for deployment
 description: Learn about the support matrix for Arc-enabled VMware vSphere including vCenter Server versions supported, network requirements, and more.
 ms.topic: how-to 
-ms.date: 03/27/2024
+ms.date: 04/23/2024
 ms.service: azure-arc
 ms.subservice: azure-arc-vmware-vsphere
 author: Farha-Bano
@@ -43,7 +43,7 @@ This account is used for the ongoing operation of Azure Arc-enabled VMware vSphe
 
 ### Resource bridge resource requirements
 
-For Arc-enabled VMware vSphere, resource bridge has the following minimum virtual hardware requirements
+For Arc-enabled VMware vSphere, resource bridge has the following minimum virtual hardware requirements:
 
 - 16 GB of memory
 - 4 vCPUs
@@ -62,6 +62,11 @@ In addition, VMware VSphere requires the following exception:
 | **Service** | **Port** | **URL** | **Direction** | **Notes**|
 | --- | --- | --- | --- | --- |
 | vCenter Server | 443 | URL of the vCenter server  | Appliance VM IP and control plane endpoint need outbound connection. | Used to by the vCenter server to communicate with the Appliance VM and the control plane.|
+| VMware Cluster Extension | 443 | `azureprivatecloud.azurecr.io` | Appliance VM IPs need outbound connection. | Pull container images for Microsoft.VMWare and Microsoft.AVS Cluster Extension.|
+| Azure CLI and Azure CLI Extensions | 443 | `*.blob.core.windows.net` | Management machine needs outbound connection. | Download Azure CLI Installer and Azure CLI extensions.|
+| Azure Resource Manager | 443 | `management.azure.com` | Management machine needs outbound connection. | Required to create/update resources in Azure using ARM.|
+| Helm Chart for Azure Arc Agents | 443 | `*.dp.kubernetesconfiguration.azure.com` | Management machine needs outbound connection. | Data plane endpoint for downloading the configuration information of Arc agents.|
+| Azure CLI | 443 | - `login.microsoftonline.com` <br> <br> - `aka.ms` | Management machine needs outbound connection. | Required to fetch and update Azure Resource Manager tokens.|
 
 For a complete list of network requirements for Azure Arc features and Azure Arc-enabled services, see [Azure Arc network requirements (Consolidated)](../network-requirements-consolidated.md).
 

articles/azure-monitor/agents/azure-monitor-agent-migration.md

@@ -12,12 +12,12 @@ ms.custom:
 
 # Migrate to Azure Monitor Agent from Log Analytics agent
 
-[Azure Monitor Agent (AMA)](./agents-overview.md) replaces the Log Analytics agent (also known as Microsoft Monitor Agent (MMA) and OMS) for Windows and Linux machines, in Azure and non-Azure environments, including on-premises and third-party clouds. The agent introduces a simplified, flexible method of configuring data dollection using [Data Collection Rules (DCRs)](../essentials/data-collection-rule-overview.md). This article provides guidance on how to implement a successful migration from the Log Analytics agent to Azure Monitor Agent.
+[Azure Monitor Agent (AMA)](./agents-overview.md) replaces the Log Analytics agent (also known as Microsoft Monitor Agent (MMA) and OMS) for Windows and Linux machines, in Azure and non-Azure environments, including on-premises and third-party clouds. The agent introduces a simplified, flexible method of configuring data collection using [Data Collection Rules (DCRs)](../essentials/data-collection-rule-overview.md). This article provides guidance on how to implement a successful migration from the Log Analytics agent to Azure Monitor Agent.
 
 If you're currently using the Log Analytics agent with Azure Monitor or [other supported features and services](#migrate-additional-services-and-features), start planning your migration to Azure Monitor Agent by using the information in this article. If you are using the Log Analytics Agent for SCOM, you need to [migrate to the SCOM Agent](../vm/scom-managed-instance-overview.md).
 
 The Log Analytics agent will be [retired on **August 31, 2024**](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). You can expect the following when you use the MMA or OMS agent after this date.
-> - **Data upload**: You can still upload data. At some point when major customer have finished migrating and data volumes significantly drop, upload will be suspended. You can expect this to take at least 6 to 9 months.  You will not receive a breaking change notification of the suspension. 
+> - **Data upload**: You can still upload data. At some point when major customers have finished migrating and data volumes significantly drop, upload will be suspended. You can expect this to take at least 6 to 9 months.  You will not receive a breaking change notification of the suspension. 
 > - **Install or reinstall**: You can still install and reinstall the legacy agents. You will not be able to get support for installing or reinstalling issues.
 > - **Customer Support**: You can expect support for MMA/OMS for security issues.
 
@@ -32,7 +32,7 @@ Before you begin migrating from the Log Analytics agent to Azure Monitor Agent,
 ### Before you begin 
 
 > [!div class="checklist"]
-> - **Check the [prerequisites](./azure-monitor-agent-manage.md#prerequisites) for installing Azure Monitor Agent.**<br>To monitor non-Azure and on-premises servers, you must [install the Azure Arc agent](../../azure-arc/servers/agent-overview.md). The Arc agent makes your on-premises servers visible as to Azure as a resource it can target. You won't incur any additional cost for installing the Azure Arc agent. 
+> - **Check the [prerequisites](./azure-monitor-agent-manage.md#prerequisites) for installing Azure Monitor Agent.**<br>To monitor non-Azure and on-premises servers, you must [install the Azure Arc agent](../../azure-arc/servers/agent-overview.md). The Arc agent makes your on-premises servers visible to Azure as a resource it can target. You won't incur any additional cost for installing the Azure Arc agent. 
 > - **Understand your current needs.**<br>Use the **Workspace overview** tab of the [AMA Migration Helper](./azure-monitor-agent-migration-tools.md#using-ama-migration-helper) to see connected agents and discover solutions enabled on your Log Analytics workspaces that use legacy agents, including per-solution migration recommendations. 
 > - **Verify that Azure Monitor Agent can address all of your needs.**<br>Azure Monitor Agent is General Availablity (GA) for data collection and is used for data collection by various Azure Monitor features and other Azure services. For details, see [Supported services and features](#migrate-additional-services-and-features). 
 > - **Consider installing Azure Monitor Agent together with a legacy agent for a transition period.**<br>Run Azure Monitor Agent alongside the legacy Log Analytics agent on the same machine to continue using existing functionality during evaluation or migration. Keep in mind that running two agents on the same machine doubles resource consumption, including but not limited to CPU, memory, storage space, and network bandwidth.<br>

articles/azure-resource-manager/bicep/add-template-to-azure-pipelines.md

@@ -63,7 +63,9 @@ You can use Azure Resource Group Deployment task or Azure CLI task to deploy a B
     name: Deploy Bicep files
 
     parameters:
-      azureServiceConnection: '<your-connection-name>'
+    - name: azureServiceConnection
+      type: string
+      default: '<your-connection-name>'
 
     variables:
       vmImageName: 'ubuntu-latest'