Merge pull request #302876 from MicrosoftDocs/main

Auto Publish – main to live - 2025-07-17 05:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -6879,6 +6879,11 @@
       "redirect_url": "/azure/sre-agent/troubleshoot-azure-container-apps",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/sre-agent/permissions.md",
+      "redirect_url": "/azure/sre-agent/security-context",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/reliability/whats-new.md",
       "redirect_url": "/azure/reliability/overview",

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

@@ -56,6 +56,8 @@ Available aggregations for these metrics are as follows.
 
 In the Developer, Basic, Standard, and Premium tiers, the **Capacity** metric is available for making decisions about scaling or upgrading an API Management instance. Its construction is complex and imposes certain behavior.
 
+[!INCLUDE [capacity-change.md](../../includes/api-management-capacity-change.md)]
+
 Available aggregations for this metric are as follows.
 
 * **Avg** - Average percentage of capacity used across gateway processes in every [unit](upgrade-and-scale.md) of an API Management instance. 
@@ -171,6 +173,7 @@ Use capacity metrics for making decisions whether to scale an API Management ins
 + Ignore sudden spikes that are most likely not related to an increase in load (see [Capacity metric behavior](#capacity-metric-behavior) section for explanation).
 + As a general rule, upgrade or scale your instance when a capacity metric value exceeds **60% - 70%** for a long period of time (for example, 30 minutes). Different values may work better for your service or scenario.
 + If your instance or workspace gateway is configured with only 1 unit, upgrade or scale it when a capacity metric value exceeds **40%** for a long period. This recommendation is based on the need to reserve capacity for guest OS updates in the underlying service platform.
++ Use [available diagnostics](monitor-api-management.md) to monitor the response times of API calls. Consider adjusting scaling thresholds if you notice degraded response times with increasing value of capacity metric. 
 
 > [!TIP]  
 > If you are able to estimate your traffic beforehand, test your API Management instance or workspace gateway on workloads you expect. You can increase the request load gradually and monitor the value of the capacity metric that corresponds to your peak load. Follow the steps from the previous section to use Azure portal to understand how much capacity is used at any given time.

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

@@ -55,7 +55,7 @@ You can add up to 1,000 private certificates per webspace.
 
 ## Create a free managed certificate
 
-The free App Service managed certificate is a turn-key solution for helping to secure your custom DNS name in App Service. Without any action from you, this TLS/SSL server certificate is fully managed by App Service and is automatically renewed continuously in six-month increments, 45 days before expiration, as long as the prerequisites that you set up stay the same. All the associated bindings are updated with the renewed certificate. You create and bind the certificate to a custom domain, and let App Service do the rest.
+The free App Service managed certificate is a turn-key solution for helping to secure your custom DNS name in App Service. Without any action from you, this TLS/SSL server certificate is fully managed by App Service and is automatically renewed, as long as the prerequisites that you set up stay the same. All the associated bindings are updated with the renewed certificate. You create and bind the certificate to a custom domain, and let App Service do the rest.
 
 Before you create a free managed certificate, make sure that you [meet the prerequisites](#prerequisites) for your app.
 

articles/application-gateway/configuration-http-settings.md

@@ -32,7 +32,7 @@ Azure Application Gateway uses gateway-managed cookies for maintaining user sess
 This feature is useful when you want to keep a user session on the same server and when session state is saved locally on the server for a user session. If the application can't handle cookie-based affinity, you can't use this feature. To use it, make sure that the clients support cookies.
 
 > [!NOTE]
-> Some vulnerability scans may flag the Application Gateway affinity cookie because the Secure or HttpOnly flags are not set. These scans don't take into account that the data in the cookie is generated using a one-way hash. The cookie doesn't contain any user information and is used purely for routing. 
+> Some vulnerability scans may flag the Application Gateway affinity cookie because the Secure or HttpOnly flags aren't set. These scans don't take into account that the data in the cookie is generated using a one-way hash. The cookie doesn't contain any user information and is used purely for routing. 
 
 
 The [Chromium browser](https://www.chromium.org/Home) [v80 update](https://chromiumdash.appspot.com/schedule) brought a mandate where HTTP cookies without [SameSite](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-03#rfc.section.5.3.7) attribute have to be treated as SameSite=Lax. For CORS (Cross-Origin Resource Sharing) requests, if the cookie has to be sent in a third-party context, it has to use *SameSite=None; Secure* attributes and it should be sent over HTTPS only. Otherwise, in an HTTP only scenario, the browser doesn't send the cookies in the third-party context. The goal of this update from Chrome is to enhance security and to avoid Cross-Site Request Forgery (CSRF) attacks. 
@@ -78,7 +78,7 @@ By default, the Application Gateway resource includes popular CA certificates, a
 
 ### Request timeout
 
-This setting is the number of seconds that the application gateway waits to receive a response from the backend server. The default value is 20 seconds. However, you may wish to adjust this setting to the needs of your application.
+This setting is the number of seconds that the application gateway waits to receive a response from the backend server. The default value is 20 seconds. However, you may wish to adjust this setting to the needs of your application. Acceptable values are from 1 second to 86400 seconds (24 hours).
 
 ### Override backend path
 
@@ -152,7 +152,7 @@ This setting specifies the port where the backend servers listen to traffic from
 
 ### Timeout
 
-This setting is the number of seconds that the application gateway waits before closing the frontend and backend connections in case there is no transmission of any data.
+This setting is the number of seconds that the application gateway waits before closing the frontend and backend connections in case there's no transmission of any data. Acceptable values are from 1 second to 86400 seconds (24 hours).
 
 ### Trusted root certificate 
 

articles/backup/azure-elastic-san-backup-configure.md

@@ -2,9 +2,9 @@
 title: Configure Azure Elastic SAN backup using Azure portal (preview)
 description: Learn how to configure Azure Elastic SAN backup (preview) using Azure portal.
 ms.topic: how-to
-ms.date: 06/20/2025
-author: jyothisuri
-ms.author: jsuri
+ms.date: 07/15/2025
+author: AbhishekMallick-MS
+ms.author: v-mallicka
 # Customer intent: "As an IT administrator, I want to configure backup for Azure Elastic SAN using the Azure portal, so that I can ensure data protection and recovery for my storage resources."
 ---
 
@@ -39,7 +39,7 @@ To create a backup policy for Elastic SAN from Azure Business Continuity Center,
 1. On the **Schedule + retention** tab, under the **Backup schedule** section, set the schedule for creating recovery points for backups.
 
    >[!Note]
-   >Azure Backup currently supports **Daily** backup frequency only, which is selected by default.
+   >Azure Backup currently supports **Daily** and **Weekly**backup frequency. **Daily** backup is selected by default.
 
    :::image type="content" source="./media/azure-elastic-storage-area-network-backup-configure/set-backup-schedule.png" alt-text="Screenshot shows how to configure the backup schedule." lightbox="./media/azure-elastic-storage-area-network-backup-configure/set-backup-schedule.png":::
 

articles/backup/azure-elastic-san-backup-overview.md

@@ -2,9 +2,9 @@
 title: About Azure Elastic SAN backup (preview)
 description: Learn how the Elastic SAN backup (preview) works.
 ms.topic: overview
-ms.date: 06/20/2025
-author: jyothisuri
-ms.author: jsuri
+ms.date: 07/15/2025
+author: AbhishekMallick-MS
+ms.author: v-mallicka
 ms.custom: engagement-fy24
 --- 
 
@@ -26,7 +26,7 @@ Elastic SAN backup includes the following key features:
 - **Region availability**: The feature is currently [available in specific regions](azure-elastic-storage-area-network-backup-support-matrix.md#supported-regions) only. 
 - **Snapshot export**: Exports the selected Elastic SAN to an independent managed disk incremental snapshot (operational tier) at a given point in time.
 - **Storage and resiliency**: Managed Disk incremental snapshot is stored in Locally redundant storage (LRS) resiliency (in LRS-[supported regions](azure-elastic-storage-area-network-backup-support-matrix.md#supported-regions)), independent of the Elastic SAN lifecycle.
-- **Recovery points**: Supports up to **450 recovery points**, with backup frequency of **24 hours**.
+- **Recovery points**: Supports up to **450** recovery points, which allows you customize **daily** or **weekly** schedules to align your backup strategy with business continuity and compliance needs.
 - **Backup tier**: Supports operational tier.
 
   >[!Note]

articles/backup/azure-elastic-san-backup-support-matrix.md

@@ -2,11 +2,11 @@
 title: Support matrix for Azure Elastic SAN Backup (preview)
 description: Learn about the  regional availability, supported scenarios, and limitations for Elastic SAN backup (preview).
 ms.topic: reference
-ms.date: 06/20/2025
+ms.date: 07/15/2025
 ms.custom: references_regions, engagement-fy24
 ms.service: azure-backup
-author: jyothisuri
-ms.author: jsuri
+author: AbhishekMallick-MS
+ms.author: v-mallicka
 # Customer intent: "As a cloud administrator, I want to understand the support matrix for Azure Elastic SAN backup, so that I can effectively plan and execute backup and restore operations while adhering to the supported scenarios and limitations."
 ---
 
@@ -24,7 +24,7 @@ Elastic SAN backup has the following supported and unsupported scenarios:
 
 - Operational-tier backup is supported for Elastic SAN; vault-tier isn't currently supported. So, the security-related settings ([immutability](backup-azure-immutable-vault-concept.md?tabs=backup-vault), [soft-delete](backup-azure-security-feature-cloud.md?tabs=azure-portal), [Multi-user authorization](multi-user-authorization-concept.md?tabs=backup-vault), and [customer-managed keys](encryption-at-rest-with-cmk.md?tabs=portal)) that are applicable for vault-tier aren't supported.
 - Same volume can't be protected multiple times as part of multiple backup instances.
-- Hourly backups aren't supported; only daily backups are available.
+- Hourly backups aren't supported; only daily and weekly backups are available.
 - The Original Location Recovery (OLR) is currently not supported; only Alternate Location Recovery (ALR) is supported.
 - Azure [subscription and service](/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-virtual-machine-disk-limits) limits apply to the total number of disk snapshots per region per subscription.
 - The Backup vault and the volumes to be backed up must be in the same subscription and region.

articles/backup/whats-new.md

@@ -2,12 +2,12 @@
 title: What's new in the Azure Backup service
 description: Learn about the new features in the Azure Backup service.
 ms.topic: release-notes
-ms.date: 06/02/2025
+ms.date: 07/15/2025
 ms.service: azure-backup
 ms.custom:
   - ignite-2023
-author: jyothisuri
-ms.author: jsuri
+author: AbhishekMallick-MS
+ms.author: v-mallicka
 # Customer intent: "As a cloud administrator, I want to stay informed about new features and enhancements in Azure Backup, so that I can effectively manage data protection and ensure compliance within my organization's cloud infrastructure."
 ---
 
@@ -132,13 +132,13 @@ For more information, see [Migrate Azure VM backups from Standard to Enhanced po
 
 ## Operational backup support for Azure Elastic SAN (preview)
 
-Azure Backup now allows secure backup and restoration for Azure Elastic storage area network (SAN) volumes through Azure Backup vault, ensuring seamless data protection. This fully managed solution seamlessly allows you to schedule backups, set expiration timelines for restore points, and restore data to a new volume.
+Azure Backup now allows secure backup and restoration for Azure Elastic SAN volumes through Azure Backup vault, ensuring seamless data protection. This fully managed solution seamlessly allows you to schedule backups, set expiration timelines for restore points, and restore data to a new volume.
 
 Key features include:
 
 - Protects against accidental deletions, ransomware attacks, and application updates.
 - Captures Elastic SAN volumes at specific points in time as independent Managed Disk incremental snapshots with Locally redundant storage (LRS) resiliency.
-- Stores up to **450 restore points**, with backup frequencies from **4 hours** to **24 hours**.
+- Stores up to **450** recovery points, which allows you customize **daily** or **weekly** schedules to align your backup strategy with business continuity and compliance needs.
 
 >[!Note]
 >This feature is in preview and [available in specific Azure regions](azure-elastic-storage-area-network-backup-support-matrix.md#supported-regions).

articles/connectors/connectors-create-api-oracledatabase.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 06/12/2024
+ms.date: 07/16/2025
 ---
 
 # Connect to Oracle Database from Azure Logic Apps

articles/cyclecloud/how-to/flex-scalesets.md

@@ -2,39 +2,40 @@
 title: Using Flex ScaleSets
 description: Create VMs using VMSS Flex
 author: dougclayton
-ms.date: 11/02/2022
+ms.date: 07/01/2025
 ms.author: doclayto
 monikerRange: '>= cyclecloud-8'
 ---
 
 # Using Flex ScaleSets
 
-As of 8.3.0, CycleCloud can use [Flex orchestration](https://go.microsoft.com/fwlink/?LinkId=2156742) for scale sets. 
-This works differently than the automatic usage of Uniform scale sets that is standard in CycleCloud. 
+As of version 8.3.0, CycleCloud can use [Flex orchestration](https://go.microsoft.com/fwlink/?LinkId=2156742) for scale sets. 
+This orchestration works differently than the automatic usage of Uniform scale sets that is standard in CycleCloud. 
 In this mode, you create a Flex scale set outside of CycleCloud, and you specify which nodes should use it. 
-CycleCloud creates and deletes VMs in that scale set. This works for both head nodes and execute nodearrays.
+CycleCloud creates and deletes VMs in that scale set. This setup works for both head nodes and execute node arrays.
 
-To use Flex orchestration, you must use a CycleCloud credential that is locked to a given resource group (which must be created). 
-This is because VMs in a Flex scale set must be in the same resource group as the scale set. 
-You can use the az CLI to create the resource group, if you don't have one to use already:
+To use Flex orchestration, you must use a CycleCloud credential that is locked to a given resource group (which you must create). 
+This requirement exists because VMs in a Flex scale set must be in the same resource group as the scale set. 
+You can use the az CLI to create the resource group if you don't already have one:
 
 ```azurecli-interactive
 az group create --location REGIONNAME --resource-group RESOURCEGROUP
 ```
 
-The scaleset must be created in Flex orchestration mode, and any VM settings on it (e.g., VM size or image) are ignored. 
-Because of this, it is easiest to create it through the az CLI:
+You must create the scale set in Flex orchestration mode. The creation process ignores any VM settings on the scale set, such as the VM size or image.
+
+Because of this limitation, it's easiest to create the scale set through Azure CLI:
 
 ```azurecli-interactive
 az vmss create --orchestration-mode Flexible --resource-group RESOURCEGROUP --name SCALESET --platform-fault-domain-count 1
 ```
 
-Finally, specify the fully qualified id for this scaleset on the node or nodearray that should use it on the cluster template:
+Finally, specify the fully qualified ID for this scale set on the node or node array that should use it in the cluster template:
 
 ```ini
 [nodearray execute]
 FlexScaleSetId = /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/RESOURCEGROUP/providers/Microsoft.Compute/virtualMachineScaleSets/SCALESET
 ```
 
 > [!NOTE]
-> Scale sets have limitations on size (currently 1000 VMs). To scale larger than that, you must create multiple scale sets and assign them to different nodearrays.
+> Scale sets have limitations on size (currently 1,000 VMs). To scale larger than that size, you must create multiple scale sets and assign them to different node arrays.