Merge pull request #301579 from MicrosoftDocs/main

6/19/2025 AM Publish

Author: Taojunshen

articles/app-service/app-service-configure-premium-v4-tier.md

@@ -3,7 +3,7 @@ title: Configure Premium V4 tier
 description: Learn how to better performance for your web, mobile, and API app in Azure App Service by scaling to the new Premium V4 pricing tier.
 keywords: app service, azure app service, scale, scalable, app service plan, app service cost
 ms.topic: article
-ms.date: 06/13/2025
+ms.date: 06/18/2025
 ms.author: msangapu
 author: msangapu-msft
 ms.custom:
@@ -98,14 +98,20 @@ Premium V4 is available in the following regions:
 
 - Australia East
 - Canada Central
+- Central US
 - East US
 - East US 2
 - France Central
+- North Central US
 - North Europe
+- Norway East
 - Southeast Asia
 - Sweden Central
+- Switzerland North
+- UK South
 - West Central US
 - West Europe
+- West US
 - West US 3
 
 ## Scale up from an unsupported resource group and region combination

articles/azure-app-configuration/howto-telemetry.md

@@ -6,7 +6,7 @@ ms.service: azure-app-configuration
 author: mrm9084
 ms.author: mametcal
 ms.topic: how-to
-ms.date: 03/05/2025
+ms.date: 06/19/2025
 ---
 
 # Enable telemetry for feature flags
@@ -33,7 +33,7 @@ These types of questions can be answered through the emission and analysis of fe
     > [!div class="mx-imgBorder"]
     > ![Screenshot of the Azure portal, connecting application insights.](./media/howto-telemetry/connect-to-app-insights.png)
 
-## Enable telemetry for a feature flag (preview)
+## Enable telemetry for a feature flag
 
 1. Open your App Configuration store in the Azure portal and select the **Feature manager** blade under the **Operations** section.
 1. Select the feature flag named Greeting. If you don't have it, follow the [instructions to create it](./manage-feature-flags.md). Then, right-click on the feature flag and select **Edit**.

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

@@ -80,7 +80,7 @@ export MY_SUBNET_ID="$(az network vnet subnet show \
 
 ## Set up the admin password
 
-Set up a password that meets the [password requirements for Azure VMs](https://learn.microsoft.com/azure/virtual-machines/windows/faq#what-are-the-password-requirements-when-creating-a-vm-).
+Set up a password that meets the [password requirements for Azure VMs](/azure/virtual-machines/windows/faq#what-are-the-password-requirements-when-creating-a-vm-).
 
 ```bash
 export ADMIN_PASSWORD="Azure compliant password"

articles/azure-netapp-files/network-attached-storage-protocols.md

@@ -119,7 +119,7 @@ Some organizations have pure Windows or pure UNIX environments (homogeneous) in
 * SMB and [NTFS](/windows-server/storage/file-server/ntfs-overview) file security
 * NFS and UNIX file security - mode bits or [NFSv4.x access control lists (ACLs)](https://wiki.linux-nfs.org/wiki/index.php/ACLs)
 
-However, many sites must enable data sets to be accessed from both Windows and UNIX clients (heterogenous). For environments with these requirements, Azure NetApp Files has native dual-protocol NAS support. After the user is authenticated on the network and has both appropriate share or export permissions and the necessary file-level permissions, the user can access the data from UNIX hosts using NFS or from Windows hosts using SMB.
+However, many sites must enable data sets to be accessed from both Windows and UNIX clients (heterogeneous). For environments with these requirements, Azure NetApp Files has native dual-protocol NAS support. After the user is authenticated on the network and has both appropriate share or export permissions and the necessary file-level permissions, the user can access the data from UNIX hosts using NFS or from Windows hosts using SMB.
 
 ### Reasons for using dual-protocol volumes
 

articles/azure-netapp-files/performance-virtual-machine-sku.md

@@ -25,7 +25,7 @@ Storage performance involves more than the speed of the storage itself. The proc
 For the most consistent performance when selecting virtual machines, select from SKUs with a single type of chipset – newer SKUs are preferred over the older models where available. Keep in mind that, aside from using a dedicated host, predicting correctly which type of hardware the E_v3 or D_v3 virtual machines land on is unlikely. When using the E_v3 or D_v3 SKU:
 
 * When a virtual machine is turned off, deallocated, and then turned on again, the virtual machine is likely to change hosts and as such hardware models.
-* When applications are deployed across multiple virtual machines, expect the virtual machines to run on heterogenous hardware.
+* When applications are deployed across multiple virtual machines, expect the virtual machines to run on heterogeneous hardware.
 
 ## Differences within and between SKUs
 

articles/azure-resource-manager/bicep/bicep-core-diagnostics.md

@@ -7,7 +7,7 @@ ms.custom:
   - devx-track-bicep
   - devx-track-arm-template
   - build-2025
-ms.date: 06/06/2025
+ms.date: 06/19/2025
 ---
 
 # Bicep core diagnostics
@@ -399,6 +399,9 @@ If you need more information about a particular diagnostic code, select the **Fe
 | <a id='BCP417' />BCP417 | Error | The spread operator `{ellipsis}` cannot be used inside objects with property for-expressions.    |
 | <a id='BCP418' />BCP418 | Error | Extensions cannot be referenced here. Extensions can only be referenced by module extension configurations.   |
 | <a id='BCP419' />BCP419 | Error | Namespace name `{name}` cannot be used as an extension name.|
+| <a id='BCP420' />BCP420 | Error | The scope could not be resolved at compile time because the supplied expression is ambiguous or too complex. Scoping expressions must be reducible to a specific kind of scope without knowledge of parameter values. |
+| <a id='BCP421' />BCP421 | Error | Module `{moduleName}` contains one or more secure outputs, which are not supported with `{LanguageConstants.TargetScopeKeyword}` set to `{LanguageConstants.TargetScopeTypeLocal}`.|
+| <a id='BCP422' />BCP422 | Error | A resource of type `{baseType}` may or may not exist when this function is called, which could cause the deployment to fail.|
 
 ## Next steps
 

articles/azure-resource-manager/management/request-limits-and-throttling.md

@@ -123,6 +123,9 @@ Microsoft Compute implements throttling to provide an optimal experience for Vir
 
 [Azure Resource Graph](../../governance/resource-graph/overview.md) limits the number of requests to its operations. The steps in this article to determine the remaining requests and how to respond when the limit is reached also apply to Resource Graph. However, Resource Graph sets its own limit and reset rate. For more information, see [Resource Graph throttling headers](../../governance/resource-graph/concepts/guidance-for-throttled-requests.md#understand-throttling-headers).
 
+Azure Resource Graph also has a solution that enables an additional mechanism for getting resource data when you have reached resource provider throttling limits by seamlessly integrating with existing Azure Resource Manager control plane GET and LIST APIs—offering a powerful, scalable solution for resource data access. For more information, see [ARG GET/LIST API](../../governance/resource-graph/concepts/arg-get-list-api.md)
+
+
 ### Other resource providers
 
 For information about throttling in other resource providers, see:

articles/backup/backup-azure-arm-restore-vms.md

@@ -3,7 +3,7 @@ title: Restore VMs by using the Azure portal using Azure Backup
 description: Restore an Azure virtual machine from a recovery point by using the Azure portal, including the Cross Region Restore feature.
 ms.reviewer: nikhilsarode
 ms.topic: how-to
-ms.date: 06/18/2025
+ms.date: 06/19/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
@@ -40,7 +40,7 @@ Some details about storage accounts:
 - **Replace disk**: When replacing a managed disk from a Vault-Standard recovery point that's **< 4 TB** or a VM containing **< 16 disks**, a VHD file is created in the specified storage account. After replacement, source VM disks remain in the designated Resource Group, and VHDs stay in the storage account; you can delete or retain the source disk and the VHDs as needed.
 - **Storage account location**: The storage account must be in the same region as the vault. Only these accounts are displayed. If there are no storage accounts in the location, you need to create one.
 - **Storage type**: Blob Storage account isn't supported because the Premium Storage account  it requires is excluded for cost optimization.
-- **Storage redundancy**: Zone redundant storage (ZRS) isn't supported. The replication and redundancy information for the account is shown in parentheses after the account name.
+- **Storage redundancy**: Zone redundant storage (ZRS) is supported. The replication and redundancy information for the account is shown in parentheses after the account name.
 - **Premium storage**:
   - When you restore non-premium VMs, premium storage accounts aren't supported.
   - When you restore managed VMs, premium storage accounts configured with network rules aren't supported.

articles/backup/backup-azure-vm-migrate-enhanced-policy.md

@@ -2,7 +2,7 @@
 title: Move VM backup - standard to enhanced policy in Azure Backup
 description: Learn how to trigger Azure VM backups migration from standard  policy to enhanced policy, and then monitor the configuration backup migration job.
 ms.topic: reference
-ms.date: 06/17/2025
+ms.date: 06/19/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
@@ -25,7 +25,7 @@ Azure Backup now supports migration to the enhanced policy for Azure VM backups
 - Before you start the migration, ensure that there are no ongoing backup jobs for the VM that you plan to migrate.
 - Migration is supported for Managed VMs only and isn’t supported for Classic or unmanaged VMs.
 - Once the migration is complete, you can’t change the backup policy back to standard policy.
-- Migration operations trigger a backup job as part of the migration process and might take up to several hours to complete for large VMs.
+- When you migrate a VM Backup Item from Standard to Enhanced policy, the process triggers a backup job that might take several hours for large VMs. This precautionary backup uses managed disk snapshots — starting with a full disk copy for instant restore, which increases backup time. Later snapshots are incremental, storing only changes since the last snapshot. If you're using unmanaged disks, make sure the storage account hosting the snapshot or VHD files allows public network access or similar settings; otherwise, the system falls back to a standard recovery point restore, which slows down recovery.
 - The change from standard policy to enhanced policy can result in extra costs. [Learn More](backup-instant-restore-capability.md#cost-impact).
 
 >[!Note]
@@ -140,4 +140,4 @@ To trigger bulk migration of VMs protected using Standard policy to an Enhanced
 
 - Learn about [Standard VM backup policy](backup-during-vm-creation.md#create-a-vm-with-backup-configuration).
 - Learn how to [back up an Azure VM using Enhanced policy](backup-azure-vms-enhanced-policy.md).
-- [Troubleshoot backup policy migration issue](backup-azure-vms-troubleshoot.md#migration-from-standard-to-enhanced-policy-issue).
+- [Troubleshoot backup policy migration issue](backup-azure-vms-troubleshoot.md#migration-from-standard-to-enhanced-policy-issue).

articles/backup/backup-azure-vms-troubleshoot.md

@@ -3,7 +3,7 @@ title: Troubleshoot backup errors with Azure VMs
 description: In this article, learn how to troubleshoot errors encountered with backup and restore of Azure virtual machines.
 ms.reviewer: srinathv
 ms.topic: troubleshooting
-ms.date: 06/02/2025
+ms.date: 06/19/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
@@ -556,15 +556,15 @@ Verify the VM Agent version on Windows VMs:
 
 VM backup relies on issuing snapshot commands to underlying storage. Not having access to storage or delays in a snapshot task run can cause the backup job to fail. The following conditions can cause snapshot task failure:
 
-* **VMs with SQL Server backup configured can cause snapshot task delay**. By default, VM backup creates a VSS full backup on Windows VMs. VMs that run SQL Server, with SQL Server backup configured, can experience snapshot delays. If snapshot delays cause backup failures, set following registry key:
+* **VMs with SQL Server backup configured can cause snapshot task delay**. To avoid that, currently VM backup creates a VSS full backup (Copy-Only) on Windows VMs. If you need a VSS Full backup (Non-copy Only) then add the following registry key on the Windows VM:
 
    ```console
    REG ADD "HKLM\SOFTWARE\Microsoft\BcdrAgent" /v UseVssFullBackup /t REG_SZ /d True /f
    
    ```
 
   >[!Note]
-  >From December 12, 2022, Azure VM backup automatically sets the registry key in the existing protected Azure VMs that are registered as SQL VMs. Now, you don't need  to explicitly set this registry key. This ensures that snapshots aren't delayed and any log chains managed by other backup products are also not broken. Azure VM backup now also set the registry key in any new SQL VMs automatically during the configuration of backup.
+  >**Copy-Only** backups ensure that snapshots aren't delayed, and any log chains managed by other backup products are also not broken.
 
 * **VM status is reported incorrectly because the VM is shut down in RDP**. If you used the remote desktop to shut down the virtual machine, verify that the VM status in the portal is correct. If the status isn't correct, use the **Shutdown** option in the portal VM dashboard to shut down the VM.
 * **If more than four VMs share the same cloud service, spread the VMs across multiple backup policies**. Stagger the backup times, so no more than four VM backups start at the same time. Try to separate the start times in the policies by at least an hour.