Merge pull request #301371 from MicrosoftDocs/main

6/16/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/09/2025
+ms.date: 06/13/2025
 ms.author: msangapu
 author: msangapu-msft
 ms.custom:
@@ -98,7 +98,6 @@ Premium V4 is available in the following regions:
 
 - Australia East
 - Canada Central
-- North Europe
 - East US
 - East US 2
 - France Central

articles/app-service/configure-ssl-certificate.md

@@ -38,8 +38,7 @@ The following table lists the options for you to add certificates in App Service
 
 The [free App Service managed certificate](#create-a-free-managed-certificate) and the [App Service certificate](configure-ssl-app-service-certificate.md) already satisfy the requirements of App Service. If you choose to upload or import a private certificate to App Service, your certificate must meet the following requirements:
 
-* Be exported as a [password-protected .pfx file](https://en.wikipedia.org/w/index.php?title=X.509&section=4#Certificate_filename_extensions), encrypted by using triple DES.
-* Contain a private key at least 2,048 bits long.
+* Be exported as a [password-protected PFX file](https://en.wikipedia.org/w/index.php?title=X.509&section=4#Certificate_filename_extensions).
 * Contain all intermediate certificates and the root certificate in the certificate chain.
 
 If you want to help secure a custom domain in a TLS binding, the certificate must meet these extra requirements:
@@ -48,7 +47,7 @@ If you want to help secure a custom domain in a TLS binding, the certificate mus
 * Be signed by a trusted certificate authority.
 
 > [!NOTE]
-> *Elliptic curve cryptography (ECC) certificates* work with App Service but aren't covered by this article. For the exact steps to create ECC certificates, work with your certificate authority.
+> **Elliptic Curve Cryptography (ECC) certificates** work with App Service when uploaded as a PFX, but currently cannot be imported from Key Vault. They aren't covered by this article. For the exact steps to create ECC certificates, work with your certificate authority.
 
 After you add a private certificate to an app, the certificate is stored in a deployment unit that's bound to the App Service plan's resource group, region, and operating system (OS) combination. Internally, it's called a *webspace*. That way, the certificate is accessible to other apps in the same resource group, region, and OS combination. Private certificates uploaded or imported to App Service are shared with app services in the same deployment unit.
 

articles/app-service/manage-backup.md

@@ -31,7 +31,7 @@ There are two types of backups in App Service. If your app is in a supported pri
 | Backup size | 30 GB. | 10 GB, 4 GB of which can be the linked database. |
 | Linked database | Not backed up. | **[Starting 3/31/2028, Azure App Service custom backups will no longer support backing up linked databases.](#deprecation-of-linked-database-backups)** <br><br>The following linked databases can be backed up: [SQL Database](/azure/azure-sql/database/), [Azure Database for MySQL](/azure/mysql/), [Azure Database for PostgreSQL](/azure/postgresql/), [MySQL in-app](https://azure.github.io/AppService/2016/08/18/Announcing-MySQL-in-app-for-Web-Apps-(Windows).html). Note that Azure DB for MySQL - **Flexible Server** and Azure DB for PostgreSQL - **Flexible Server** aren't supported in custom backups. |
 | [Storage account](../storage/index.yml) required | No. | Yes. |
-| Backup frequency | Hourly, not configurable. | Configurable. |
+| Backup frequency | Hourly, not configurable. | Configurable (every 2 hours minimum, up to 12 backups per day (manual + scheduled)). |
 | Retention | 30 days, not configurable. <br><br> Days 1-3: hourly backups retained.<br><br> Days 4-14: every third hourly backup retained.<br><br> Days 15-30: every sixth hourly backup retained. | 0-30 days or indefinite. |
 | Downloadable | No. | Yes, as Azure Storage blobs. |
 | Partial backups | Not supported. | Supported. |

articles/app-service/routine-maintenance.md

@@ -48,6 +48,9 @@ From left to right, the example shows:
 - Selecting the **Impacted Resources** tab.
 - The **More info** option.
 
+> [!NOTE]
+> Manual initiation of maintenance is not supported for App Service Plans. However, App Service Environments (ASE) do support manual maintenance preferences.
+
 :::image type="content" source="./media/routine-maintenance/routine-maintenance-more.png" alt-text="Screenshot of more info for a maintenance event in the Azure portal." lightbox="media/routine-maintenance/routine-maintenance-more.png":::
 
 This example shows:

articles/application-gateway/multiple-site-overview.md

@@ -31,7 +31,7 @@ For example, if you have 2 listeners with associated host names of `*.contoso.co
 
 The ordering of rules can be established by providing a **Priority** field value to the request routing rules associated with the listeners. You can specify an integer value from 1 to 20000 with 1 being the highest priority and 20000 being the lowest priority. If incoming client traffic matches with multiple listeners, the request routing rule with highest priority is used to serve the request. Each request routing rule must have a unique priority value.
 
-The priority field only impacts the order of evaluation of a request routing rule, this wont change the order of evaluation of path based rules within a `PathBasedRouting` request routing rule.
+The priority field only impacts the order of evaluation of a request routing rule, this won't change the order of evaluation of path based rules within a `PathBasedRouting` request routing rule.
 
 > [!NOTE]
 > To use rule priority, you must specify rule priority field values for all the existing request routing rules. Once the rule priority field is in use, any new routing rule that is created must have a rule priority field value as part of its configuration. 

articles/azure-web-pubsub/howto-configure-application-firewall.md

@@ -128,7 +128,7 @@ The application firewall rules only take effect when the access token contains t
 Below is an example to add userId and insert a unique placeholder in the access token:
 
 ```cs
-// The GUID role wont have any effect. But it ensures this token's uniqueness when using rule ThrottleByJwtSignatureRule.
+// The GUID role won't have any effect. But it ensures this token's uniqueness when using rule ThrottleByJwtSignatureRule.
 var url = service.GetClientAccessUri((userId: "user1" , roles: new string[] {  "webpubsub.joinLeaveGroup.group1", Guid.NewGuid().ToString()});
 ```
 

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

@@ -2,7 +2,7 @@
 title: Troubleshoot Blob backup and restore issues
 description: In this article, learn about symptoms, causes, and resolutions of Azure Backup failures related to the Azure Blob backups and restore.
 ms.topic: troubleshooting
-ms.date: 05/21/2025
+ms.date: 06/13/2025
 ms.service: azure-backup
 ms.reviewer: geg
 author: jyothisuri
@@ -151,7 +151,7 @@ This article provides troubleshooting information to address issues you encounte
 
 **Error message**: Incorrect containers selected for operation.
 
-**Recommendation**: This error may occur if one or more containers included in the scope of protection no longer exist in the protected storage account. We recommend you to re-trigger the operation after modifying the protected container list using the edit backup instance option.
+**Recommendation**: This error may occur if one or more containers included in the scope of protection no longer exist in the protected storage account. We recommend you to retrigger the operation after modifying the protected container list using the edit backup instance option.
 
 ### UserErrorPitrRestoreInProgress
 
@@ -250,30 +250,6 @@ This article provides troubleshooting information to address issues you encounte
 
 **Recommended action**: Track further progress on the operation in storage account activity log.
 
-### UserErrorVaultedBackupFeatureNotEnabled
-
-**Error code**: `UserErrorVaultedBackupFeatureNotEnabled`
-
-**Error message**: The subscription must be registered for the required features to use vaulted backup for blobs.
-
-**Recommended action**: Register your subscription for Microsoft.Storage/HardenBackup and Microsoft.DataProtection/BlobVaultedBackup.
-
-### ObjectReplicationPolicyCreationFailure
-
-**Error code**: `ObjectReplicationPolicyCreationFailure`
-
-**Error message**: Failed to create object replication policy on the storage account.
-
-**Recommended action**: Failed to create object replication policy. Wait for a few minutes and then try the operation again. If the issue persists, please contact Microsoft support.
-
-### UserErrorRequiredStorageFeaturesDisabled 
-
-**Error code**: `UserErrorRequiredStorageFeaturesDisabled`
-
-**Error message**: The operation failed due to required storage feature(s) being disabled on the storage account.
-
-**Recommended action**: Enable required features for Azure backup on source Storage account.
-
 ### UserErrorSelectedContainerPartOfAnotherORPolicy
 
 **Error code**: `UserErrorSelectedContainerPartOfAnotherORPolicy`
@@ -312,31 +288,31 @@ This article provides troubleshooting information to address issues you encounte
 
 **Error message**: Requested operation failed due to throttling by the Azure service. Azure Storage account management list operations limit reached.
 
-**Recommended action&&: Wait for a few minutes and then try the operation again.
+**Recommended action**: Wait for a few minutes and then try the operation again.
 
 ### UserErrorBlobVersionDeletedDuringBackup 
 
 **Error code**: `UserErrorBlobVersionDeletedDuringBackup`
 
 **Error message**: The backup failed due to one or more blob versions getting deleted in the backup job duration.
 
-**Recommended action**: We recommend you to avoid tampering with blob versions while a backup job is in  progress. Ensure the minimum retention configured for versions in the life cycle management policy is 7 days.
+**Recommended action**: We recommend you to avoid tampering with blob versions while a backup job is in  progress. Ensure the minimum retention configured for versions in the life cycle management policy is seven days.
 
 ### UserErrorBlobVersionArchivedDuringBackup
 
 **Error code**: `UserErrorBlobVersionArchivedDuringBackup`
 
 **Error message**: The backup failed due to one or more blob versions moving to the archive tier in the backup job duration.
 
-**Recommended action**: We recommend you to avoid tampering with blob versions while a backup job is in  progress. Ensure the minimum retention configured for versions in the life cycle management policy is *7 days*.
+**Recommended action**: We recommend you to avoid tampering with blob versions while a backup job is in  progress. Ensure the minimum retention configured for versions in the life cycle management policy is *seven days*.
 
 ### UserErrorBlobVersionArchivedAndDeletedDuringBackup
 
 **Error code**: `UserErrorBlobVersionArchivedAndDeletedDuringBackup`
 
 **Error message**: The backup failed due to one or more blob versions moving to the archive tier or getting deleted in the backup job duration.
 
-**Recommended action**: We recommend you to avoid tampering with blob versions while a backup job is in  progress. Ensure the minimum retention configured for versions in the life cycle management policy is 7 days.
+**Recommended action**: We recommend you to avoid tampering with blob versions while a backup job is in  progress. Ensure the minimum retention configured for versions in the life cycle management policy is seven days.
 
 ### UserErrorContainerHasImmutabilityPolicyDuringRestore
 
@@ -396,8 +372,180 @@ This article provides troubleshooting information to address issues you encounte
 
 ### LinkedAuthorizationFailed
 
-*Error code**: `LinkedAuthorizationFailed`
+**Error code**: `LinkedAuthorizationFailed`
 
 **Error message**: The client [user name] with object ID has permissions to perform the required action [operation name] on scope [vault name], however, it does not have the required permissions to perform action(s) [operation name] on the linked scope [datasource name].
 
 **Recommended action**: Ensure that you have read access on the datasource associated with this backup instance to be able to trigger the restore operation. Once the required permissions are provided, retry the operation. 
+
+## UserErrorConflictingOperationInProgress
+
+**Error code**: `UserErrorConflictingOperationInProgress`
+
+**Error message**: This operation on Storage Account requires exclusive access.
+
+**Recommended action**: Ensure that there is no conflicting operation in progress, and then retry the operation. 
+
+##  UserErrorStorageAccountContainerNotFound
+
+**Error code**: `UserErrorStorageAccountContainerNotFound`
+
+**Error message**:  The specified container isn't found.
+
+**Cause**: This error can occur if required container is deleted while operation is in progress.
+
+**Recommended action**: Retry the operation and wait for completion before attempting container delete operation.
+
+## UserErrorBlobContainerDeletedDuringBackup
+
+**Error code**: `UserErrorBlobContainerDeletedDuringBackup`
+
+**Error message**:  The backup failed due to one or more blob containers deleted in the backup job duration.
+
+**Recommended action**: We recommend to avoid tampering with blob containers while a backup job is in  progress.
+
+## UserErrorBlobVersionArchivedAndContainerDeletedDuringBackup
+
+**Error code**: `UserErrorBlobVersionArchivedAndContainerDeletedDuringBackup`
+
+**Error message**: The backup failed due to one or more blob versions are moving to the archive tier and one or more containers deleted in the backup job duration.
+
+**Recommended action**: We recommend to avoid tampering with blob versions and blob containers while a backup job is in  progress.
+
+## UserErrorBlobVersionDeletedAndContainerDeletedDuringBackup
+
+**Error code**: `UserErrorBlobVersionDeletedAndContainerDeletedDuringBackup`
+
+**Error message** - The backup failed due to one or more blob versions getting deleted or container getting deleted in the backup job duration.
+
+**Recommended action**: We recommend to avoid tampering with blob versions and containers while a backup job is in  progress. Ensure the minimum retention configured for versions in lifecycle management policy is seven days.
+
+## UserErrorBlobVersionArchivedDeletedAndContainerDeletedDuringBackup
+
+**Error code**: `UserErrorBlobVersionArchivedDeletedAndContainerDeletedDuringBackup`
+
+**Error message**: The backup failed due to one or more blob versions moving to the archive tier, blob version getting deleted, and container getting deleted in the backup job duration.
+
+**Recommended action**: We recommend to avoid tampering with blob versions and containers while a backup job is in  progress. Ensure the minimum retention configured for versions in lifecycle management policy is seven days.
+
+## LongRunningOperationTrackingFailure
+
+**Error code**: `LongRunningOperationTrackingFailure`
+
+**Error message**: Failed to track the long-running operation. The operation is still running and is expected to complete. 
+
+This error is usually seen for operational tier restore failure due to PITR still running in background. And potentially should complete.
+
+**Recommended action**: Track further progress on the operation in storage account activity log.
+
+## UserErrorConflictingFeatureHardDeleteEnabled 
+
+**Error code**: `UserErrorConflictingFeatureHardDeleteEnabled `
+
+**Error message**: Conflicting feature permanent delete is enabled which is causing the operation failure.
+
+**Recommended action**: Please disable permanent delete setting on the storage account and retry the operation. [Learn more](https://aka.ms/UserErrorConflictingFeatureHardDeleteEnabled).
+
+##  UserErrorConflictingFeatureNSPEnabled
+
+**Error code**: `UserErrorConflictingFeatureNSPEnabled`
+
+**Error message**: Conflicting feature network security perimeter is enabled which is causing the operation failure.
+
+**Recommended action**: Remove network security perimeter from the storage account and retry the operation. 
+
+## 641508, UserErrorConflictingOperationInProgress
+
+**Error code**: `641508, UserErrorConflictingOperationInProgress`
+
+**Error message**: This operation on Storage Account requires exclusive access.
+
+**Recommended action**: Retry after ensuring there is no conflicting operation in progress.
+
+## 641539, UserErrorCrossTenantOrsPolicyDisabled
+
+**Error code**: `641539, UserErrorCrossTenantOrsPolicyDisabled`
+
+**Error message**: Cross tenant object replication policy is disabled.
+
+**Recommended action**: Enable cross tenant object replication policy on storage account and trigger the operation again.
+
+##  641541, UserErrorPitrRestoreFailedLeasedBlob
+
+**Error code**: `641541, UserErrorPitrRestoreFailedLeasedBlob`
+
+**Error message**: The point in time operation failed because of a lease on the blob.
+
+**Recommended action**: Break the lease on blob before retrying.
+
+##  641560, UserErrorStorageAccountAndDatasourceLocationNotSame
+
+**Error code**: `641560, UserErrorStorageAccountAndDatasourceLocationNotSame`
+
+**Error message**: Operation failed because, Storage Account and Datasource are not in the same location.
+
+**Recommended action**: Check the DataSource location in protection input and make sure it is same as the location of Storage account
+
+##  641561, UserErrorKeyVaultWasNotFound
+
+**Error code**: `641561, UserErrorKeyVaultWasNotFound`
+
+**Error message**: Operation failed because key vault is not found to unwrap the encryption key for storage account.
+
+**Recommended action**: Check the key vault settings used for storage account encryption.
+
+## 641562, UserErrorBackupOperationNotSupportedOnOperationalTier
+
+**Error code**: `641562, UserErrorBackupOperationNotSupportedOnOperationalTier`
+
+**Error message**: Backup isn't supported on this tier.
+
+**Recommended action**: Change policy to allow backups to run only on supported tiers.
+
+## 641563, UserErrorMaxLimitReachedForObjectReplicationPoliciesOnStorageAccount
+
+**Error code**: `641563, UserErrorMaxLimitReachedForObjectReplicationPoliciesOnStorageAccount`
+
+**Error message**: Number of Object Replication Policies exceeded the max limit on a given storage account.
+
+**Recommended action**: Remove at least one object replication policy.
+
+## 641564, UserErrorLegalHoldOnContainer
+
+**Error code**: `641564, UserErrorLegalHoldOnContainer`
+
+**Error message**: Operation failed because the container(s) have legal hold.
+
+**Recommended action**: Remove legal hold from containers or remove container with legal hold from protection for operation to succeed.
+
+## 641565, UserErrorSubscriptionFrozen
+
+**Error code**: `641565, UserErrorSubscriptionFrozen`
+
+**Error message**: Operation failed because subscription frozen due to inactivity.
+
+**Recommended action**: Contact Microsoft support to unfreeze the subscription.
+
+## 641566, UserErrorDenyAssignmentWithBlueprint
+
+**Error code**: `641566, UserErrorDenyAssignmentWithBlueprint`
+
+**Error message**: Operation failed because the access is denied due to deny assigmented created by Azure blueprint assignment.
+
+**Recommended action**: Remove the deny assignment created by Azure blueprint assignment.
+
+## 641568, UserErrorRestoreObjectReplicationPolicyCreationFailure
+
+**Error code**: `641568, UserErrorRestoreObjectReplicationPolicyCreationFailure`
+
+**Error message**: Failed to create object replication policy on the storage account, restore storage account or the object replication policy created by Azure Backup may have been deleted.
+
+**Recommended action**:  Use the valid restore storage account then try the operation again.
+
+## UserErrorMaxSubmissionLimitReached
+
+**Error code**: `UserErrorMaxSubmissionLimitReached`
+
+**Error message**: Limit reached for maximum number of operations within a time range is reached.
+
+**Recommended action**: The daily backup count has reached the maximum limit of five for the instance. Trigger a new backup after 24 hours.