Merge pull request #302669 from MicrosoftDocs/main

7/14/2025 11:00 AM IST Publish

Author: ttorble

articles/azure-web-pubsub/howto-monitor-data-reference.md

@@ -25,6 +25,8 @@ Metrics provide insights into the operational state of the service. The availabl
 |Inbound Traffic|Bytes|Sum|The inbound traffic to the service.|No Dimensions|
 |Outbound Traffic|Bytes|Sum|The outbound traffic from the service.|No Dimensions|
 |Server Load|Percent|Max / Avg|The percentage of server load.|No Dimensions|
+|Rest API Response Time|Count|Sum|The response time of REST API request categorized by endpoint.|ResponseTime, RestApiCategory|
+|Client Request Status Code|Count|Sum|The status code of client connection requests.|ClientType, Status|
 
 For more information, see [Metrics](concept-metrics.md).
 

articles/operator-nexus/concepts-network-fabric-read-only-commands.md

@@ -57,6 +57,9 @@ To use Network Fabric read-only commands, complete the following steps:
     > [!NOTE]
     > The Storage URL must be located in a different region from the Network Fabric. For instance, if the Fabric is hosted in East US, the storage URL should be outside of East US. 
 
+>[!Note]
+> As part of our continued commitment to security and modernization, we are announcing the end of support for Shared Access Signature (SAS) URL–based access to customer-provided storage accounts Azure Operator Nexus 2508.1 release.
+
 ## Bring your own storage account 
 
 Users can bring your own storage for storing output files of runRO command by following the steps outlined in the [Bring Your Own Storage for Network Fabric](howto-configure-bring-your-own-storage-network-fabric.md) guide.

articles/operator-nexus/concepts-network-fabric-resource-update-commit.md

@@ -12,10 +12,14 @@ ms.custom:
   - build-2025
 ---
 
+
 # Update and commit Network Fabric resources
 
 Currently, Nexus Network Fabric resources require that you disable a parent resource (such as an L3Isolation domain) and reput the parent or child resource with updated values and execute the administrative post action to enable and configure the devices. Network Fabric's new resource update flow allows you to  batch and update a set of Network Fabric resources via a `commitConfiguration` POST action when resources are enabled. There's no change if you choose the current workflow of disabling L3 Isolation domain, making changes and the enabling L3 Isolation domain. 
 
+>[!Note]
+>As part of our continued efforts to improve operational efficiency and reliability, we are announcing that new Fabric Commit v2 workflow will become the default commit workflow starting with Azure Operator 2507.1 release and commit v1 is depricated. Refer [Commit Workflow v2 in Azure Operator Nexus - Network Fabric](./concepts-commit-workflow-v2.md)
+
 ## Network Fabric resource update overview
 
 Any Create, Update, Delete (CUD) operation on a child resource linked to an existing enabled parent resource or an update to an enabled parent resource property is considered an **Update** operation. A few examples would be a new Internal network, or a new subnet needs to be added to an existing enabled Layer 3 Isolation domain (Internal network is a child resource of Layer 3 isolation domain). A new route policy needs to be attached to existing internal network; both these scenarios qualify for an **Update** operation. 

articles/operator-nexus/how-to-validate-cables.md

@@ -15,6 +15,9 @@ This article explains the  Fabric cable validation, where the primary function o
 
 For BOM details, refer to [Azure Operator Nexus SKUs](./reference-operator-nexus-skus.md)
 
+>[!Note]
+> As part of our continued commitment to security and modernization, we are announcing the end of support for Shared Access Signature (SAS) URL–based access to customer-provided storage accounts in Azure Operator Nexus 2508.1 release.
+
 ## Prerequisites
 
 - Ensure the Nexus Network Fabric is successfully provisioned.

articles/static-web-apps/static-web-apps-cli.yml

@@ -1,6 +1,27 @@
 ### YamlMime:AzureCLIGroup
 uid: swa
 name: swa
+commands:
+- swa_login
+- swa_build
+- swa_start
+- swa_deploy
+- swa_db
+metadata:
+  description: Azure Static Web Apps CLI
+  globalParameters:
+  - name: --version, -v
+    summary: Display the version number.
+  - name: --verbose, --V [level]
+    summary: Enable verbose output. Level values include `silly`, `info`, `log` (default), and `silent`.
+  - name: --config, -c [path]
+    summary: Path to the swa-cli.config.json file.
+  - name: --config-name, -cn
+    summary: Configuration used by the CLI.
+  - name: --print-config, -g
+    summary: Print all resolved options. Default is `false`.
+  - name: --help, -h
+    summary: Show context-sensitive help.
 directCommands:
 - uid: swa_login
   name: swa login
@@ -448,24 +469,3 @@ directCommands:
     summary:  The container of your cosmosdb account you want to connect.
   - name: --help, -h
     summary: Display help for command.
-globalParameters:
-- name: --version, -v
-  summary: Display the version number.
-- name: --verbose, --V [level]
-  summary: Enable verbose output. Level values include `silly`, `info`, `log` (default), and `silent`.
-- name: --config, -c [path]
-  summary: Path to the swa-cli.config.json file.
-- name: --config-name, -cn
-  summary: Configuration used by the CLI.
-- name: --print-config, -g
-  summary: Print all resolved options. Default is `false`.
-- name: --help, -h
-  summary: Show context-sensitive help.
-commands:
-- swa_login
-- swa_build
-- swa_start
-- swa_deploy
-- swa_db
-metadata:
-  description: Azure Static Web Apps CLI

articles/update-manager/troubleshoot.md

@@ -24,7 +24,7 @@ The following troubleshooting steps apply to the Azure virtual machines (VMs) re
 
 To verify if the Microsoft Azure Virtual Machine agent (VM agent) is running and has triggered appropriate actions on the machine and the sequence number for the autopatching request, check the agent log for more information in `/var/log/waagent.log`. Every autopatching request has a unique sequence number associated with it on the machine. Look for a log similar to `2021-01-20T16:57:00.607529Z INFO ExtHandler`.
 
-The package directory for the extension is `/var/lib/waagent/Microsoft.CPlat.Core.Edp.LinuxPatchExtension-<version>`. The `/status` subfolder has a `<sequence number>.status` file. It includes a brief description of the actions performed during a single autopatching request and the status. It also includes a short list of errors that occurred while applying updates.
+The package directory for the extension is `/var/lib/waagent/Microsoft.CPlat.Core.LinuxPatchExtension-<version>`. The `/status` subfolder has a `<sequence number>.status` file. It includes a brief description of the actions performed during a single autopatching request and the status. It also includes a short list of errors that occurred while applying updates.
 
 To review the logs related to all actions performed by the extension, check for more information in `/var/log/azure/Microsoft.CPlat.Core.LinuxPatchExtension/`. It includes the following two log files of interest: