Merge pull request #292549 from MicrosoftDocs/main

1/2/2025 AM Publish

Author: Albertyang0

articles/automation/automation-hrw-run-runbooks.md

@@ -3,7 +3,7 @@ title: Run Azure Automation runbooks on a Hybrid Runbook Worker
 description: This article describes how to run runbooks on machines in your local datacenter or other cloud provider with the Hybrid Runbook Worker.
 services: automation
 ms.subservice: process-automation
-ms.date: 09/09/2024
+ms.date: 01/01/2025
 ms.topic: how-to
 ms.custom: devx-track-azurepowershell, linux-related-content
 ms.service: azure-automation
@@ -13,7 +13,8 @@ ms.service: azure-automation
 
 
 > [!Important]
-> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) has retired on **31 August 2024** and is no longer supported. Follow the guidelines on how to [migrate from an existing Agent-based User Hybrid Runbook Workers to Extension-based Hybrid Workers](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md).
+> - Starting 1st April 2025, all jobs running on agent-based Hybrid Worker will be stopped. 
+> - Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) has retired on **31 August 2024** and is no longer supported. Follow the guidelines on how to [migrate from an existing Agent-based User Hybrid Runbook Workers to Extension-based Hybrid Workers](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md).
 
 > [!NOTE]
 > Azure Automation Run As Account has retired on September 30, 2023 and is replaced with Managed Identities. Follow the guidelines on [how to start migrating your runbooks to use managed identities](automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](migrate-run-as-accounts-managed-identity.md#sample-scripts).

articles/automation/automation-windows-hrw-install.md

@@ -3,7 +3,7 @@ title: Deploy an agent-based Windows Hybrid Runbook Worker in Automation
 description: This article tells how to deploy an agent-based Hybrid Runbook Worker that you can use to run runbooks on Windows-based machines in your local datacenter or cloud environment.
 services: automation
 ms.subservice: process-automation
-ms.date: 09/09/2024
+ms.date: 01/01/2025
 ms.topic: how-to
 ms.service: azure-automation
 ---

articles/automation/includes/agent-based-user-hybrid-runbook-worker-retirement.md

@@ -2,8 +2,9 @@
 author: SnehaSudhir
 ms.author: sudhirsneha
 ms.topic: include
-ms.date: 09/04/2024
+ms.date: 01/01/2025
 ---
 
 > [!Important]
-> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) has retired on **31 August 2024** and is no longer supported. Follow the guidelines on how to [migrate from an existing Agent-based User Hybrid Runbook Workers to Extension-based Hybrid Workers](../migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md).
+> - Starting 1st April 2025, all jobs running on agent-based Hybrid Worker will be stopped. 
+> - Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) has retired on **31 August 2024** and is no longer supported. Follow the guidelines on how to [migrate from an existing Agent-based User Hybrid Runbook Workers to Extension-based Hybrid Workers](../migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md).

articles/migrate/how-to-create-group-machine-dependencies-agentless.md

@@ -41,7 +41,7 @@ This article describes how to set up agentless dependency analysis using Azure M
 2. As you configure the appliance, you need to specify the following in the appliance configuration manager:
     - The details of the source environment (vCenter Server(s)/Hyper-V host(s) or cluster(s)/physical servers) which you want to discover.
     - Server credentials, which can be domain/ Windows (non-domain)/ Linux (non-domain) credentials. [Learn more](add-server-credentials.md) about how to provide credentials and how the appliance handles them.
-    - Verify the permissions required to perform agentless dependency analysis. For Windows servers, you need to provide domain or non-domain (local) account with administrative permissions. For Linux servers, provide a sudo user account with permissions to execute ls and netstat commands or create a user account that has the CAP_DAC_READ_SEARCH and CAP_SYS_PTRACE permissions on /bin/netstat and /bin/ls files. If you're providing a sudo user account, ensure that you enabled NOPASSWD for the account to run the required commands without prompting for a password every time sudo command is invoked.
+    - Verify the permissions required to perform agentless dependency analysis. For Windows servers, you need to provide domain or non-domain (local) account with administrative permissions. For Linux servers, provide a sudo user account with permissions to execute ls and netstat (or `ss` depending on OS version) commands or create a user account that has the CAP_DAC_READ_SEARCH and CAP_SYS_PTRACE permissions on /bin/netstat and /bin/ls (or /bin/ss depending on OS version) files. If you're providing a sudo user account, ensure that you enabled NOPASSWD for the account to run the required commands without prompting for a password every time sudo command is invoked.
 
 ### Add credentials and initiate discovery
 
@@ -244,4 +244,4 @@ Azure Migrate offers a Power BI template that you can use to visualize network c
 
 ## Next steps
 
-[Group servers](how-to-create-a-group.md) for assessment.
+[Group servers](how-to-create-a-group.md) for assessment.

articles/migrate/vmware/migrate-support-matrix-vmware.md

@@ -338,7 +338,7 @@ Azure Government | Agent-based dependency analysis isn't supported.
 Requirement | Details
 --- | ---
 Project limits | You can create multiple Azure Migrate projects in an Azure subscription.<br /><br /> You can discover and assess up to 50,000 servers in a VMware environment in a single [project](../migrate-support-matrix.md#project). A project can include physical servers and servers from a Hyper-V environment, up to the assessment limits.
-Discovery | The Azure Migrate appliance can discover up to 10,000 servers running across multiple vCenter Servers.<br /><br /> The appliance supports adding multiple vCenter Servers. You can add up to 10 vCenter Servers per appliance.<br /><br /> This amount is valid for Azure VMware Solution as well.
+Discovery | The Azure Migrate appliance can discover up to 10,000 servers running across multiple vCenter Servers.<br /><br /> The appliance supports adding multiple vCenter Servers. You can add up to 10 vCenter Servers per appliance.<br /><br /> This amount is valid for Azure VMware Solution as well.<br /><br />The same vCenter can be discovered by multiple appliances within the same project, but individual VMs cannot be simultaneously discovered by multiple appliances. More details on how to set [discovery scope](./set-discovery-scope.md).
 Assessment | You can add up to 35,000 servers in a single group.<br /><br /> You can assess up to 35,000 servers in a single assessment.
 
 Learn more about [assessments](../concepts-assessment-calculation.md).

articles/openshift/howto-deploy-java-jboss-enterprise-application-platform-app.md

@@ -90,7 +90,7 @@ The following steps show you how to find the offer and fill out the **Basics** p
 
 1. On the **Basics** pane, ensure that the value shown in the **Subscription** field is the same one that has the roles listed in the prerequisites section.
 
-1. You must deploy the offer in an empty resource group. In the **Resource group** field, select **Create new** and fill in a value for the resource group. Because resource groups must be unique within a subscription, pick a unique name. An easy way to have unique names is to use a combination of your initials, today's date, and some identifier. For example, *eaparo033123rg*.
+1. In the **Resource group** field, select **Create new** and fill in a value for the resource group. Because resource groups must be unique within a subscription, pick a unique name. An easy way to have unique names is to use a combination of your initials, today's date, and some identifier. For example, *eaparo033123rg*.
 
 1. Under **Instance details**, select the region for the deployment. For a list of Azure regions where OpenShift operates, see [Regions for Red Hat OpenShift 4.x on Azure](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=openshift&regions=all).
 

articles/virtual-desktop/rbac.md

@@ -21,6 +21,8 @@ For a full list of all the built-in roles available, see [Azure built-in roles](
 
 The Desktop Virtualization Contributor role allows managing all your Azure Virtual Desktop resources, apart from user or group assignment. If you want to assign user accounts or user groups to resources, you also need the *User Access Administrator* role. The Desktop Virtualization Contributor role doesn't grant users access to compute resources.
 
+**ID**: 082f0a83-3be5-4ba1-904c-961cca79b387
+
 | Action type | Permissions |
 |--|--|
 | actions | <ul><li>Microsoft.DesktopVirtualization/\*</li><li>Microsoft.Resources/subscriptions/resourceGroups/read</li><li>Microsoft.Resources/deployments/\*</li><li>Microsoft.Authorization/\*/read</li><li>Microsoft.Insights/alertRules/\*</li><li>Microsoft.Support/\*</li></ul> |

articles/virtual-desktop/whats-new-multimedia-redirection.md

@@ -10,11 +10,11 @@ ms.custom: docs_inherited
 
 # What's new in multimedia redirection?
 
-This article has the latest updates for host component of multimedia redirection for Azure Virtual Desktop.
+This article has the latest updates for the host component of multimedia redirection for Azure Virtual Desktop, which is installed on session hosts. To learn how to install and configure multimedia redirection, see [Multimedia redirection for video playback and calls in a remote session](multimedia-redirection.md).
 
 ## Latest available version
 
-The following table shows the latest available version of multimedia redirection for Azure Virtual Desktop. For setup instructions, see [Multimedia redirection for video playback and calls in a remote session](multimedia-redirection.md).
+The following table shows the latest available version of multimedia redirection for Azure Virtual Desktop.
 
 | Release | Latest version | Download |
 |---------|----------------|----------|

includes/storage-files-file-share-management-concepts.md

@@ -13,6 +13,6 @@ Azure file shares are deployed into *storage accounts*, which are top-level obje
 
 There are two main types of storage accounts you will use for Azure Files deployments: 
 - **General purpose version 2 (GPv2) storage accounts**: GPv2 storage accounts allow you to deploy Azure file shares on standard/hard disk-based (HDD-based) hardware. In addition to storing Azure file shares, GPv2 storage accounts can store other storage resources such as blob containers, queues, or tables. 
-- **FileStorage storage accounts**: FileStorage storage accounts allow you to deploy Azure file shares on premium/solid-state disk-based (SSD-based) hardware. FileStorage accounts can only be used to store Azure file shares; no other storage resources (blob containers, queues, tables, etc.) can be deployed in a FileStorage account. Only FileStorage accounts can deploy both SMB and NFS file shares.
+- **FileStorage storage accounts**: FileStorage storage accounts allow you to deploy Azure file shares on premium/solid-state disk-based (SSD-based) hardware. FileStorage accounts can only be used to store Azure file shares; no other storage resources (blob containers, queues, tables, etc.) can be deployed in a FileStorage account. Only FileStorage accounts can deploy both SMB and NFS file shares, as NFS is only supported in Premium file shares.
 
-There are several other storage account types you may come across in the Azure portal, PowerShell, or CLI. Two storage account types, BlockBlobStorage and BlobStorage storage accounts, cannot contain Azure file shares. The other two storage account types you may see are general purpose version 1 (GPv1) and classic storage accounts, both of which can contain Azure file shares. Although GPv1 and classic storage accounts may contain Azure file shares, most new features of Azure Files are available only in GPv2 and FileStorage storage accounts. We therefore recommend to only use GPv2 and FileStorage storage accounts for new deployments, and to upgrade GPv1 and classic storage accounts if they already exist in your environment.  
+There are several other storage account types you may come across in the Azure portal, PowerShell, or CLI. Two storage account types, BlockBlobStorage and BlobStorage storage accounts, cannot contain Azure file shares. The other two storage account types you may see are general purpose version 1 (GPv1) and classic storage accounts, both of which can contain Azure file shares. Although GPv1 and classic storage accounts may contain Azure file shares, most new features of Azure Files are available only in GPv2 and FileStorage storage accounts. We therefore recommend to only use GPv2 and FileStorage storage accounts for new deployments, and to upgrade GPv1 and classic storage accounts if they already exist in your environment.