When you move a virtual machine to a different subscription, you need to move all the resources that are associated with the virtual machine, such as the disks, the network interface, and the virtual network. You cannot move a virtual machine without moving its dependent resources. You also need to ensure that the target subscription supports the same region, resource type, and API version as the source subscription. Then, References: [Move a Windows VM to another Azure subscription or resource group]

Explanation:

To restore files or folders from the recovery point, go to the virtual machine and choose the desired recovery point.
Step 0. In the virtual machine ' s menu, click Backup to open the Backup dashboard.
Step 1. In the Backup dashboard menu, click File Recovery.
Step 2. From the Select recovery point drop-down menu, select the recovery point that holds the files you want. By default, the latest recovery point is already selected.
Step 3: To download the software used to copy files from the recovery point, click Download Executable (for Windows Azure VM) or Download Script (for Linux Azure VM, a python script is generated).
Step 4: Copy the files by using AzCopy
AzCopy is a command-line utility designed for copying data to/from Microsoft Azure Blob, File, and Table storage, using simple commands designed for optimal performance. You can copy data between a file system and a storage account, or between storage accounts.
References:
https://docs.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm
https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy

Explanation:

When deploying Azure Bastion using an Azure Resource Manager (ARM) template, Microsoft requires that the subnet dedicated to Bastion follows strict configuration guidelines. According to the Microsoft Azure Administrator documentation, the Azure Bastion service must be deployed within a specifically named subnet called "AzureBastionSubnet".
This subnet name is case-sensitive and mandatory - any deviation from this name (e.g., "BastionSubnet" or
"AzureBastion") will cause deployment failure.
Additionally, the subnet must have a minimum prefix of /27 to provide sufficient IP addresses for the Bastion- managed instances and scaling operations. Subnets smaller than /27 (such as /28 or /29) are not supported because Bastion requires multiple internal IP addresses for operations like scaling, management, and secure connectivity.
In the ARM template structure:
{
" type " : " Microsoft.Network/virtualNetworks " ,
" name " : " VNET1 " ,
" apiVersion " : " 2019-02-01 " ,
" location " : " [resourceGroup().location] " ,
" properties " : {
" addressSpace " : {
" addressPrefixes " : [ " 10.10.10.0/24 " ]
},
" subnets " : [
{
" name " : " AzureBastionSubnet " ,
" properties " : {
" addressPrefix " : " 10.10.10.0/27 "
}
},
{
" name " : " LAN02 " ,
" properties " : {
" addressPrefix " : " 10.10.10.128/25 "
}
}
]
}
}
This ensures that Azure Bastion can be deployed properly within the virtual network VNET1, providing secure RDP/SSH connectivity to VMs without exposing public IPs.
Extract from Microsoft Documentation:
"Azure Bastion must be deployed in a dedicated subnet named 'AzureBastionSubnet'. The subnet must be at least /27 or larger (/26, /25, etc.). This subnet is used exclusively by the Bastion host and cannot contain other resources." (Source: Microsoft Learn - Deploy Azure Bastion using Azure Resource Manager templates, and Azure Bastion service configuration requirements)

To enable a web app hosted in Azure App Service to connect securely to an on-premises SMB share (Share1), you must create hybrid network connectivity between your Azure environment and your on-premises network.
According to the Microsoft Azure Administrator Study Guide and Microsoft Learn documentation, Azure Web Apps running in an App Service Plan cannot directly access on-premises file shares over the public internet for security reasons. You must extend your on-premises network to Azure through a Virtual Network (VNet) and then integrate the web app with that network.
The Virtual Network Gateway is the component that enables this hybrid connectivity. It establishes a Site-to- Site VPN or ExpressRoute connection between the Azure VNet and the on-premises network, allowing the web app (after VNet integration) to access internal resources such as SMB shares, SQL Servers, or file servers.
Once the VPN gateway is configured and the web app is integrated with the VNet (Regional VNet Integration), the web app can securely access Share1 over the private network channel.
Official Microsoft Documentation Extract (Summary):
"To access on-premises resources from Azure App Service, configure VNet Integration and establish a Site-to- Site VPN or ExpressRoute connection using a Virtual Network Gateway. This allows Azure resources to securely communicate with on-premises systems such as SMB file shares or databases." (Source: Microsoft Learn - Connect an App Service app to an on-premises network using Azure VPN Gateway.)

Explanation: