Merge branch 'main' into release-aio-2507

Author: v-alje

articles/api-management/api-management-capacity.md

@@ -42,9 +42,6 @@ In the v2 tiers, the following metrics are available:
 
 * **Memory Percentage of Gateway** - The percentage of memory capacity used by the gateway units.
 
-    > [!NOTE]
-    > Currently, the Memory Percentage of Gateway metric isn't supported in the Premium v2 tier.
-
 Available aggregations for these metrics are as follows.
 
 * **Avg** - Average percentage of capacity used across gateway processes in every [unit](upgrade-and-scale.md) of an API Management instance. 

articles/api-management/api-management-region-availability.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 06/17/2025
+ms.date: 07/21/2025
 ms.author: danlep
 ms.custom:
   - references_regions
@@ -32,6 +32,7 @@ Information in the following table is updated regularly. Capacity availability i
 | Australia Southeast | ✅ | ✅ | | |
 | Brazil South | ✅ | ✅ | |  |
 | Central India  | ✅ | ✅ | |  |
+| Central US  | ✅ | ✅ | |  |
 | East Asia | ✅ | ✅ | | ✅ |
 | East US  | ✅ | ✅ |  |  |
 | East US 2 | ✅ | ✅ | ✅ | ✅ |
@@ -49,6 +50,7 @@ Information in the following table is updated regularly. Capacity availability i
 | Sweden Central | ✅ | ✅ | | |
 | South India | ✅ | ✅ |  |  |
 | Switzerland North | ✅ |✅ |  | |
+| UAE North | ✅ | ✅ | |  |
 | UK South | ✅  | ✅ | ✅ | ✅ |
 | UK West | ✅  | ✅ | | |
 | West Europe  | ✅ | ✅ | | ✅ |

articles/app-service/configure-authentication-provider-aad.md

@@ -301,7 +301,7 @@ Requests that fail these built-in checks get an HTTP `403 Forbidden` response.
 
 [fic-config]: #use-a-managed-identity-instead-of-a-secret-preview
 
-Instead of configuring a client secret for your app registration, you can [configure an application to trust a managed identity (preview)][entra-fic]. Using an identity instead of a secret means you don't have to manage a secret. You don't have secret expiration events to handle, and you don't have the same level of risk associated with possibly disclosing or leaking that secret.
+Instead of configuring a client secret for your app registration, you can [configure an application to trust a managed identity][entra-fic]. Using an identity instead of a secret means you don't have to manage a secret. You don't have secret expiration events to handle, and you don't have the same level of risk associated with possibly disclosing or leaking that secret.
 
 The identity allows you to create a *federated identity credential*, which can be used instead of a client secret as a *client assertion*. This approach is available only for workforce configurations. The built-in authentication feature currently supports federated identity credentials as a preview.
 
@@ -313,6 +313,7 @@ You can use the steps in this section to configure your App Service or Azure Fun
 
     > [!IMPORTANT]
     > The user-assigned managed identity that you create should only be assigned to the App Service or Azure Functions application through this registration. If you assign the identity to another resource, you're giving that resource unnecessary access to your app registration.
+
 1. Note down the **Object ID** and **Client ID** values of the managed identity. You'll need the object ID to create a federated identity credential in the next step. You'll use the managed identity's client ID in a later step.
 
 1. Follow the Microsoft Entra ID [instructions to configure a federated identity credential on an existing application](/entra/workload-id/workload-identity-federation-config-app-trust-managed-identity#configure-a-federated-identity-credential-on-an-existing-application). Those instructions also include sections for updating application code, which you can skip.

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-versioning.md

@@ -8,7 +8,7 @@ ms.author: azfuncdf
 zone_pivot_groups: df-languages
 ---
 
-# Orchestration Versioning
+# Orchestration Versioning (preview)
 
 A key area to consider when using a durable orchestration system is how to handle the upgrading/downgrading of orchestrations. When an orchestration is interrupted and later resumed (for instance, during a host update), Durable Task Scheduler will replay the events of the orchestration. This is done to ensure reliability - the system replays to ensure all previous steps were executed successfully before the next step is taken - which is a core promise of the durable execution paradigm. So, if an orchestration changes between deployments, the steps it takes may no longer be the same. If this does happen, the system will throw a `NonDeterministicError` instead of allowing the orchestration to continue. 
 
@@ -44,7 +44,7 @@ In order for an orchestration to have a version, it must first be set in the cli
 ::: zone pivot="csharp"
 
 > [!NOTE]
-> Available in the .NET SDK since v1.9.0.
+> Available in the .NET SDK (Microsoft.DurableTask.Client.AzureManaged) since v1.9.0.
 
 ```csharp
 builder.Services.AddDurableTaskClient(builder =>
@@ -59,7 +59,7 @@ builder.Services.AddDurableTaskClient(builder =>
 ::: zone pivot="java"
 
 > [!NOTE]
-> Available in the Java SDK since v1.6.0.
+> Available in the Java SDK (com.microsoft:durabletask-client) since v1.6.0.
 
 ```java
 public DurableTaskClient durableTaskClient(DurableTaskProperties properties) {
@@ -166,6 +166,9 @@ Similar to the client versioning, these are all set via the standard host builde
 
 ::: zone pivot="csharp"
 
+> [!NOTE]
+> Available in the .NET SDK (Microsoft.DurableTask.Worker.AzureManaged) since v1.9.0.
+
 ```csharp
 builder.Services.AddDurableTaskWorker(builder =>
 {
@@ -185,6 +188,9 @@ builder.Services.AddDurableTaskWorker(builder =>
 
 ::: zone pivot="java"
 
+> [!NOTE]
+> Available in the Java SDK (com.microsoft:durabletask-client) since v1.6.0.
+
 ```java
 private static DurableTaskGrpcWorker createTaskHubServer() {
     DurableTaskGrpcWorkerBuilder builder = new DurableTaskGrpcWorkerBuilder();

articles/azure-vmware/azure-vmware-solution-platform-updates.md

@@ -4,19 +4,24 @@ description: Learn about the platform updates to Azure VMware Solution.
 ms.topic: reference
 ms.custom: "references_regions, engagement-fy23"
 ms.service: azure-vmware
-ms.date: 5/23/2025
+ms.date: 7/21/2025
 ---
 
 # What's new in Azure VMware Solution
 
 Microsoft regularly applies important updates to the Azure VMware Solution for new features and software lifecycle management. You should receive a notification through Azure Service Health that includes the timeline of the maintenance. For more information, see [Host maintenance and lifecycle management](azure-vmware-solution-host-remediation.md#host-maintenance-and-lifecycle-management).
 
-## May 2025
+## July 2025
+
+**Self-Service Maintenance Orchestrator (preview)**
 
+Public preview of Self-Service Capabilities for Planned Maintenance. [Learn more](https://techcommunity.microsoft.com/blog/azuremigrationblog/take-control-of-your-azure-vmware-solution-maintenance-schedule/4434496) 
+
+## May 2025
 
 **vSAN ESA (Express Storage Architecture) support**
 
-Azure VMware Solution will now support vSAN ESA (Express Storage Architecture) as the default vSAN architecture for AV48 (including Stretched Clusters) and AV64 (Gen 2) host types.
+Azure VMware Solution supports vSAN ESA (Express Storage Architecture) as the default vSAN architecture for AV48 (including Stretched Clusters) and AV64 (Gen 2) host types.
 
 **HCX Upgrade and Hybridity Depot Decommissioning**
 

articles/backup/azure-data-lake-storage-backup-overview.md

@@ -21,7 +21,7 @@ ms.custom: engagement-fy24
 
 Vaulted backup uses platform capabilities such as snapshots and object replication to copy data to the Backup vault. Object replication asynchronously copies block blobs from a source storage account to a destination backup storage account, including the blob's contents, versions, metadata, and properties.  
 
-When you configure protection, Azure Backup sets up a destination storage account within the Backup vault and applies an object replication policy at the container level for both source and destination accounts. During backup, Azure Backup places a recovery point marker on the source account and tracks its replication. After the marker is replicated to the destination, the recovery point is created.
+When you configure protection, Azure Backup sets up a destination storage account within the Backup vault and applies an object replication policy at the container level for both source and destination accounts. During backup, Azure Backup places a recovery point marker on the source account and tracks its replication. After the marker is replicated to the destination, the recovery point is created. Backup may take a minimum of 30–40 minutes, as backups rely on snapshots, and are taken every 15 minutes and require two snapshots to detect changes before triggering the backup.
 
 *The following diagram shows the recovery point creation process after the snapshot is taken:*
 

articles/backup/azure-data-lake-storage-configure-backup.md

@@ -112,7 +112,7 @@ To configure backup, follow these steps:
 
 1. Review the configuration details, and then select **Configure Backup**.
 
-You can track the progress of the backup configuration under **Backup instances**. After the configuration of backup is complete, Azure Backup triggers the backup operation as per the backup policy schedule to create the recovery points.
+You can track the progress of the backup configuration under **Backup instances**. After the configuration of backup is complete, Azure Backup triggers the backup operation as per the backup policy schedule to create the recovery points. Backup may take a minimum of 30–40 minutes, as backups rely on snapshots, which are taken every 15 minutes and require two snapshots to detect changes before triggering the backup.
 
 ## Next steps
 

articles/communication-services/quickstarts/email/includes/add-multiple-senders-net.md

@@ -29,13 +29,11 @@ dotnet add package Azure.ResourceManager.Communication
 Set the environment variable `AZURE_SUBSCRIPTION_ID` with the subscription ID of the subscription your Domain and Email resources are in. Run the code sample to initialize the management client.
 
 ```csharp
-using System;
-using System.Threading.Tasks;
 using Azure.Core;
 using Azure.Identity;
 using Azure.ResourceManager;
-using Azure.ResourceManager.Compute;
-using Azure.ResourceManager.Resources;
+using Azure.ResourceManager.Communication;
+using Azure;
 
 ArmClient client = new ArmClient(new DefaultAzureCredential());
 ```

articles/communication-services/quickstarts/email/includes/connect-domain-net.md

@@ -37,6 +37,8 @@ using Azure.Identity;
 using Azure.ResourceManager;
 using Azure.ResourceManager.Compute;
 using Azure.ResourceManager.Resources;
+using Azure.ResourceManager.Communication;
+using Azure.ResourceManager.Communication.Models;
 
 ArmClient client = new ArmClient(new DefaultAzureCredential());
 ```

articles/communication-services/quickstarts/sms/apply-for-toll-free-verification.md

@@ -58,7 +58,7 @@ This section requires you to provide information about your company and point of
 
 This section requires you to provide description of the SMS campaign, opt-in method (how you plan to get consent from the customer to receive SMS), and screenshots of the selected opt-in method.  
 
-:::image type="content" source="./media/apply-for-toll-free-verification/regulatory-screen-4.png" alt-text="Screenshot showing Program content section." lightbox="./media/apply-for-toll-free-verification/regulatory-screen-4.png":::
+:::image type="content" source="./media/apply-for-toll-free-verification/tfv-program-content-new.png" alt-text="Screenshot showing Program content section." lightbox="./media/apply-for-toll-free-verification/tfv-program-content-new.png":::
 
 ### Volume details
 
@@ -91,4 +91,4 @@ This program brief is automatically sent to the toll-free messaging aggregator f
 ## Related articles
 
 - Familiarize yourself with the [SMS SDK](../../concepts/sms/sdk-features.md)
-- Familiarize yourself with the [SMS FAQ](../../concepts/sms/sms-faq.md)
+- Familiarize yourself with the [SMS FAQ](../../concepts/sms/sms-faq.md)