Merge branch 'MicrosoftDocs:main' into FixingCloudBursting

Author: Padmalathas

articles/api-management/api-management-howto-api-inspector.md

@@ -97,7 +97,7 @@ Detailed steps follow.
 
     ```json
     {
-        "credentialsExpireAfter": PT1H,
+        "credentialsExpireAfter": "PT1H",
         "apiId": "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/apis/{apiId}",
         "purposes": ["tracing"]
     }

articles/azure-netapp-files/application-volume-group-manage-volumes-oracle.md

@@ -4,15 +4,10 @@ description: Describes how to manage a volume from its application volume group
 services: azure-netapp-files
 documentationcenter: ''
 author: b-hchen
-manager: ''
-editor: ''
-
-ms.assetid:
 ms.service: azure-netapp-files
 ms.workload: storage
-ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 04/19/2024
+ms.date: 04/17/2025
 ms.author: anfdocs
 ---
 # Manage volumes in an application volume group for Oracle
@@ -39,7 +34,7 @@ You can manage a volume from its volume group. You can resize, delete, or change
         > Changing the protocol type involves reconfiguration at the Linux host. When using dNFS, it's not recommended to mix volumes using NFSv3 and NFSv4.1.  
 
         > [!NOTE] 
-        > Using Azure NetApp Files built-in automated snapshots doesn't create database consistent backups. Instead, use data protection software such as [AzAcSnap](azacsnap-introduction.md) that supports snapshot-based data protection for Oracle. 
+        > Using Azure NetApp Files built-in automated snapshots doesn't create database consistent backups. Instead, use data protection software such as [SnapCenter](https://docs.netapp.com/us-en/snapcenter/protect-azure/protect-applications-azure-netapp-files.html) and [AzAcSnap](azacsnap-introduction.md) that supports snapshot-based data protection for Oracle. 
 
     * **Change Throughput**   
         You can adapt the throughput of the volume.

articles/azure-resource-manager/bicep/modules.md

@@ -65,9 +65,9 @@ Use the symbolic name to reference the module in another part of the Bicep file.
 
 The path can be either a local file or a file in a registry. The local file can be either a Bicep file or an ARM template for JSON. For more information, see [Path to a module](#path-to-a-module).
 
-The `name` property is required. It becomes the name of the nested deployment resource in the generated template.
+The `name` property is optional. It becomes the name of the nested deployment resource in the generated template. If no name is provided, a GUID will be generated as the name for the nested deployment resource.
 
-If a module with a static name is deployed concurrently to the same scope, there's the potential for one deployment to interfere with the output from the other deployment. For example, if two Bicep files use the same module with the same static name (`examplemodule`) and are targeted to the same resource group, one deployment might show the wrong output. If you're concerned about concurrent deployments to the same scope, give your module a unique name.
+If a module with a static name is deployed concurrently to the same scope, there's the potential for one deployment to interfere with the output from the other deployment. For example, if two Bicep files use the same module with the same static name (`examplemodule`) and are targeted to the same resource group, one deployment might show the wrong output. If you're concerned about concurrent deployments to the same scope, give your module a unique name. Another way to ensure unique module names is to leave out the `name` property, an unique module name will be generated automatically.
 
 The following example concatenates the deployment name to the module name. If you provide a unique name for the deployment, the module name is also unique.
 
@@ -78,6 +78,14 @@ module stgModule 'storageAccount.bicep' = {
 }
 ```
 
+Not providing any module name is also valid. A GUID will be generate as the module name.
+
+```bicep
+module stgModule 'storageAccount.bicep' = {
+  scope: resourceGroup('demoRG')
+}
+```
+
 If you need to *specify a scope* that's different than the scope for the main file, add the scope property. For more information, see [Set module scope](#set-module-scope).
 
 ```bicep

articles/batch/TOC.yml

@@ -120,6 +120,8 @@
       href: batch-custom-image-pools-to-azure-compute-gallery-migration-guide.md
     - name: Low-priority virtual machines
       href: low-priority-vms-retirement-migration-guide.md
+    - name: Classic compute node communication model
+      href: batch-pools-to-simplified-compute-node-communication-model-migration-guide.md
 - name: How-to guides
   items:
   - name: Manage Batch accounts
@@ -155,7 +157,7 @@
       href: credential-access-key-vault.md
     - name: Role-based access control for Azure Batch service
       displayName: rbac, access control
-      href: batch-role-based-access-control.md      
+      href: batch-role-based-access-control.md
   - name: Copy files and applications to pool nodes
     items:
     - name: Copying applications and data to pool nodes
@@ -232,7 +234,7 @@
       displayName: release, job release
       href: batch-job-prep-release.md
     - name: Configure Container Data Isolation Task
-      href: batch-container-isolation-task.md  
+      href: batch-container-isolation-task.md
     - name: Concurrent node tasks
       displayName: variable, maximize
       href: batch-parallel-node-tasks.md