Merge pull request #293267 from MicrosoftDocs/main

1/20/2025 AM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -3,7 +3,7 @@ title: Using a system-assigned managed identity for an Azure Automation account
 description: This article describes how to set up managed identity for Azure Automation accounts.
 services: automation
 ms.subservice: process-automation
-ms.date: 09/09/2024
+ms.date: 01/20/2025
 ms.topic: how-to 
 ms.custom: devx-track-azurepowershell
 ms.service: azure-automation
@@ -23,7 +23,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 
 - An Azure resource that you want to access from your Automation runbook. This resource needs to have a role defined for the managed identity, which helps the Automation runbook authenticate access to the resource. To add roles, you need to be an owner for the resource in the corresponding Microsoft Entra tenant.
 
-- If you want to execute hybrid jobs using a managed identity, update the agent-based Hybrid Runbook Worker to the latest version. There is no minimum version requirement for extension-based Hybrid Runbook Worker, and all the versions would work. The minimum required versions for the agent-based Hybrid Worker are:
+- There is no minimum version requirement for extension-based Hybrid Runbook Worker, and all the versions would work. The minimum required versions for the agent-based Hybrid Worker are:
 
     - Windows Hybrid Runbook Worker: version 7.3.1125.0
     - Linux Hybrid Runbook Worker: version 1.7.4.0
@@ -67,7 +67,7 @@ $automationAccount = "automationAccountName"
 ```
 
 > [!IMPORTANT]
-> The new Automation account-level identity overrides any previous VM-level system-assigned identities which are described in [Use runbook authentication with managed identities](./automation-hrw-run-runbooks.md#runbook-auth-managed-identities). If you're running hybrid jobs on Azure VMs that use a VM's system-assigned identity to access runbook resources, then the Automation account identity will be used for the hybrid jobs. This means your existing job execution may be affected if you've been using the Customer Managed Keys (CMK) feature of your Automation account.<br/><br/>If you wish to continue using the VM's managed identity, you shouldn't enable the Automation account-level identity. If you've already enabled it, you can disable the Automation account system-assigned managed identity. See [Disable your Azure Automation account managed identity](./disable-managed-identity-for-automation.md).
+> The new Automation account-level identity overrides any previous VM-level system-assigned identities which are described in [Use runbook authentication with managed identities](./automation-hrw-run-runbooks.md#runbook-auth-managed-identities). If you're running hybrid jobs on Azure VMs that use a VM's system-assigned identity to access runbook resources, then the Automation account identity will be used for the hybrid jobs. <br/><br/>If you wish to continue using the VM's managed identity, you shouldn't enable the Automation account-level identity. If you've already enabled it, you can disable the Automation account system-assigned managed identity. See [Disable your Azure Automation account managed identity](./disable-managed-identity-for-automation.md).
 
 ### Enable using the Azure portal
 
@@ -258,7 +258,7 @@ Perform the following steps.
 
 An Automation account can use its system-assigned managed identity to get tokens to access other resources protected by Microsoft Entra ID, such as Azure Key Vault. These tokens don't represent any specific user of the application. Instead, they represent the application that's accessing the resource. In this case, for example, the token represents an Automation account.
 
-Before you can use your system-assigned managed identity for authentication, set up access for that identity on the Azure resource where you plan to use the identity. To complete this task, assign the appropriate role to that identity on the target Azure resource.
+Before you can use your system-assigned managed identity to perform any actions within Azure, set up access for that identity on the Azure resource where you plan to use the identity. To complete this task, assign the appropriate role to that identity on the target Azure resource.
 
 Follow the principal of least privilege and carefully assign permissions only required to execute your runbook. For example, if the Automation account is only required to start or stop an Azure VM, then the permissions assigned to the Run As account or managed identity needs to be only for starting or stopping the VM. Similarly, if a runbook is reading from blob storage, then assign read-only permissions.
 

articles/automation/enable-managed-identity-for-automation.md

@@ -34,6 +34,7 @@ The following diagram demonstrates how customer-managed keys work with Azure Net
 * Applying Azure network security groups on the private link subnet to Azure Key Vault isn't supported for Azure NetApp Files customer-managed keys. Network security groups don't affect connectivity to Private Link unless `Private endpoint network policy` is enabled on the subnet. It's _required_ to keep this option disabled.
 * If Azure NetApp Files fails to create a customer-managed key volume, error messages are displayed. Refer to the [Error messages and troubleshooting](#error-messages-and-troubleshooting) section for more information.
 * Do not make any changes to the underlying Azure Key Vault or Azure Private Endpoint after creating a customer-managed keys volume. Making changes can make the volumes inaccessible.
+* Azure NetApp Files supports the ability to [seamlessly transition existing volumes from platform-managed keys to customer-managed-keys](#transition-volumes).
 * If Azure Key Vault becomes inaccessible, Azure NetApp Files loses its access to the encryption keys and the ability to read or write data to volumes enabled with customer-managed keys. In this situation, create a support ticket to have access manually restored for the affected volumes.
 * Azure NetApp Files supports customer-managed keys on source and data replication volumes with cross-region replication or cross-zone replication relationships.
 

articles/azure-netapp-files/configure-customer-managed-keys.md

@@ -2,7 +2,7 @@
 title: Support Matrix for Azure file share backup by using Azure Backup
 description: Provides a summary of support settings and limitations when backing up Azure file shares.
 ms.topic: reference
-ms.date: 01/06/2025
+ms.date: 01/20/2025
 ms.custom: references_regions, engagement-fy24
 ms.service: azure-backup
 author: AbhishekMallick-MS
@@ -55,7 +55,7 @@ Cross Subscription Backup (CSB) for Azure File share (preview) is currently avai
 
 | Storage account details | Support |
 | --- | --- |
-| Account Kind | Azure Backup supports Azure file shares present in general-purpose v2, and file storage type storage accounts. |
+| Account Kind | Azure Backup supports Azure file shares present in general-purpose v2, and file storage type storage accounts. <br><br> Storage accounts configured with private endpoints are supported. However, a private endpoint on the vault doesn't apply to Azure Files backup scenarios.  |
 
 >[!Important]
 >The source Storage Account must have the **Allow storage account key access** setting enabled for successful Azure Files backup and restore.

articles/backup/azure-file-share-support-matrix.md

@@ -596,33 +596,33 @@
 - name: Troubleshoot
   items:
     - name: Troubleshooting overview, feedback, and support
-      href: troubleshoot-set-up-overview.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-set-up-overview?context=/azure/virtual-desktop/context/context
     - name: Host pools and session hosts
       items:
       - name: Host pool creation
         displayName: troubleshooting
-        href: troubleshoot-set-up-issues.md
+        href: /troubleshoot/azure/virtual-desktop/troubleshoot-set-up-issues?context=/azure/virtual-desktop/context/context
       - name: Session host update
         displayName: troubleshooting, vms
-        href: troubleshoot-session-host-update.md
+        href: /troubleshoot/azure/virtual-desktop/troubleshoot-session-host-configuration-update?context=/azure/virtual-desktop/context/context
       - name: Session host virtual machine configuration
         displayName: troubleshooting, vms
-        href: troubleshoot-vm-configuration.md
+        href: /troubleshoot/azure/virtual-desktop/troubleshoot-vm-configuration?context=/azure/virtual-desktop/context/context
       - name: Session host statuses and health checks
         displayName: troubleshooting
         href: troubleshoot-statuses-checks.md
     - name: Management issues
       displayName: troubleshooting
-      href: troubleshoot-management-issues.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-management-issues?context=/azure/virtual-desktop/context/context
     - name: Azure Virtual Desktop PowerShell
       displayName: troubleshooting, command line
-      href: troubleshoot-powershell.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-powershell?context=/azure/virtual-desktop/context/context
     - name: Azure Virtual Desktop Agent
       displayName: troubleshooting
-      href: troubleshoot-agent.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-agent?context=/azure/virtual-desktop/context/context
     - name: Service connections
       displayName: troubleshooting, rdp
-      href: troubleshoot-service-connection.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-service-connection?context=/azure/virtual-desktop/context/context
     - name: Remote Desktop app
       items:
         - name: Windows Desktop client basic troubleshooting
@@ -654,34 +654,34 @@
       href: remotefx-graphics-performance-counters.md
     - name: Connections to Microsoft Entra joined VMs
       displayName: troubleshooting, identity
-      href: troubleshoot-azure-ad-connections.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-azure-ad-connections?context=/azure/virtual-desktop/context/context
     - name: Device redirections
       displayName: troubleshooting, rdp apps, clients
-      href: troubleshoot-device-redirections.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-device-redirections?context=/azure/virtual-desktop/context/context
     - name: Azure Virtual Desktop Insights
       displayName: troubleshooting, avd insights, avdi
-      href: troubleshoot-insights.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-insights?context=/azure/virtual-desktop/context/context
     - name: Azure Files authorization
       displayName: troubleshooting
-      href: troubleshoot-authorization.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-authorization?context=/azure/virtual-desktop/context/context
     - name: Connection quality issues
       displayName: troubleshooting, network, monitoring
-      href: troubleshoot-connection-quality.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-connection-quality?context=/azure/virtual-desktop/context/context
     - name: RDP Shortpath
       displayName: troubleshooting, network, udp
-      href: troubleshoot-rdp-shortpath.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-rdp-shortpath?context=/azure/virtual-desktop/context/context
     - name: Multimedia redirection
       displayName: troubleshooting, mmr
-      href: troubleshoot-multimedia-redirection.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-multimedia-redirection?context=/azure/virtual-desktop/context/context
     - name: Microsoft Teams
       displayName: troubleshooting
       href: troubleshoot-teams.md
     - name: Custom image templates
       displayName: troubleshooting, virtual machines, vms, images, vhd, vhdx
-      href: troubleshoot-custom-image-templates.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-custom-image-templates?context=/azure/virtual-desktop/context/context
     - name: App attach
       displayName: troubleshooting, apps, remoteapp
-      href: troubleshoot-app-attach.md
+      href: /troubleshoot/azure/virtual-desktop/troubleshoot-app-attach?context=/azure/virtual-desktop/context/context
 - name: Reference
   items:
     - name: Azure CLI

articles/virtual-desktop/TOC.yml

@@ -43,7 +43,7 @@ The agent update normally lasts 2-3 minutes on a new VM and shouldn't cause your
 
 Now that you have a better understanding of the Azure Virtual Desktop agent, here are some resources that might help you:
 
-- If you're experiencing agent or connectivity-related issues, check out the [Azure Virtual Desktop Agent issues troubleshooting guide](troubleshoot-agent.md).
+- If you're experiencing agent or connectivity-related issues, check out the [Azure Virtual Desktop Agent issues troubleshooting guide](/troubleshoot/azure/virtual-desktop/troubleshoot-agent).
 - To schedule agent updates, see the [Scheduled Agent Updates document](scheduled-agent-updates.md).
 - To set up diagnostics for this feature, see the [Scheduled Agent Updates Diagnostics guide](agent-updates-diagnostics.md).
 - To find information about the latest and previous agent versions, see the [Agent Updates version notes](whats-new-agent.md).

articles/virtual-desktop/agent-overview.md

@@ -75,4 +75,4 @@ For more information about Scheduled Agent Updates and the agent components, che
 - To learn how to schedule agent updates, see [Scheduled Agent Updates](scheduled-agent-updates.md).
 - For more information about the Azure Virtual Desktop agent, side-by-side stack, and Geneva Monitoring agent, see [Getting Started with the Azure Virtual Desktop Agent](agent-overview.md).
 - Learn more about the latest and previous agent versions at [What's new in the Azure Virtual Desktop agent](whats-new-agent.md).
-- If you're experiencing agent or connectivity-related issues, see the [Azure Virtual Desktop Agent issues troubleshooting guide](troubleshoot-agent.md).
+- If you're experiencing agent or connectivity-related issues, see the [Azure Virtual Desktop Agent issues troubleshooting guide](/troubleshoot/azure/virtual-desktop/troubleshoot-agent).

articles/virtual-desktop/agent-updates-diagnostics.md

@@ -224,7 +224,7 @@ Each session host mounts application images from the file share. You need to con
 
 - For Azure NetApp Files, you can [create an SMB volume](../azure-netapp-files/azure-netapp-files-create-volumes-smb.md) and configure NTFS permissions to give read access to each session host's computer object. Your session hosts need to be joined to Active Directory Domain Services or Microsoft Entra Domain Services.
 
-You can verify the permissions are correct by using [PsExec](/sysinternals/downloads/psexec). For more information, see [Check file share access](troubleshoot-app-attach.md#check-file-share-access).
+You can verify the permissions are correct by using [PsExec](/sysinternals/downloads/psexec). For more information, see [Check file share access](/troubleshoot/azure/virtual-desktop/troubleshoot-app-attach#check-file-share-access).
 
 ### Performance
 

articles/virtual-desktop/app-attach-overview.md

@@ -125,6 +125,6 @@ To use a smart card in your session, make sure you've installed the smart card d
 ## Next steps
 
 - Curious about other ways to keep your deployment secure? Check out [Security best practices](security-guide.md).
-- Having issues connecting to Microsoft Entra joined VMs? Look at [Troubleshoot connections to Microsoft Entra joined VMs](troubleshoot-azure-ad-connections.md).
-- Having issues with in-session passwordless authentication? See [Troubleshoot WebAuthn redirection](troubleshoot-device-redirections.md#webauthn-redirection).
+- Having issues connecting to Microsoft Entra joined VMs? Look at [Troubleshoot connections to Microsoft Entra joined VMs](/troubleshoot/azure/virtual-desktop/troubleshoot-azure-ad-connections).
+- Having issues with in-session passwordless authentication? See [Troubleshoot WebAuthn redirection](/troubleshoot/azure/virtual-desktop/troubleshoot-device-redirections#webauthn-redirection).
 - Want to use smart cards from outside your corporate network? Review how to set up a [KDC Proxy server](key-distribution-center-proxy.md).

articles/virtual-desktop/authentication.md

@@ -93,4 +93,4 @@ Now that you've deployed some Microsoft Entra joined VMs, we recommend enabling
 - [Create a profile container with Azure Files and Microsoft Entra ID](create-profile-container-azure-ad.yml)
 - [Connect with the Windows Desktop client](users/connect-windows.md)
 - [Connect with the web client](users/connect-web.md)
-- [Troubleshoot connections to Microsoft Entra joined VMs](troubleshoot-azure-ad-connections.md)
+- [Troubleshoot connections to Microsoft Entra joined VMs](/troubleshoot/azure/virtual-desktop/troubleshoot-azure-ad-connections)