Merge branch 'main' into release-migrate-new-structure

Author: v-alje

articles/active-directory-b2c/add-api-connector.md

@@ -629,7 +629,7 @@ Ensure that:
 * Your API explicitly checks for null values of received claims that it depends on.
 * Your API implements an authentication method outlined in [secure your API Connector](secure-rest-api.md).
 * Your API responds as quickly as possible to ensure a fluid user experience.
-    * Azure AD B2C will wait for a maximum of *20 seconds* to receive a response. If none is received, it will make *one more attempt (retry)* at calling your API.
+    * Azure AD B2C will wait for a maximum of *10 seconds* to receive a response. If none is received, it will make *one more attempt (retry)* at calling your API.
     * If using a serverless function or scalable web service, use a hosting plan that keeps the API "awake" or "warm" in production. For Azure Functions, it's recommended to use at minimum the [Premium plan](../azure-functions/functions-scale.md) in production.
 * Ensure high availability of your API.
 * Monitor and optimize performance of downstream APIs, databases, or other dependencies of your API.

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

@@ -93,7 +93,7 @@ Detailed steps follow.
     POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/gateways/managed/listDebugCredentials?api-version=2023-05-01-preview
     ```
     
-    In the request body, pass the full resource ID of the API that you want to trace, and specify `purposes` as `tracing`. By default the token credential returned in the response expires after 1 hour, but you can specify a different value in the payload. For example:
+    In the request body, pass the full resource ID of the API that you want to trace, and specify `purposes` as `tracing`. By default the token credential returned in the response expires after 1 hour, but you can specify a different value in the payload. Note that the expiry time is limited to a maximum of 1 hour. For example:
 
     ```json
     {

articles/api-management/virtual-network-reference.md

@@ -65,7 +65,7 @@ When an API Management service instance is hosted in a VNet, the ports in the fo
 | Inbound | Internet | * | VirtualNetwork|  [80], 443                   | TCP                | Allow            | **Client communication to API Management**                     | External only          |
 | Inbound | ApiManagement | * | VirtualNetwork | 3443                     |  TCP                | Allow       | **Management endpoint for Azure portal and PowerShell**       | External & Internal  |
 | Outbound | VirtualNetwork | * | Storage | 443                  |  TCP                | Allow             | **Dependency on Azure Storage**                             | External & Internal  |
-| Outbound | VirtualNetwork | * |  AzureActiveDirectory | 443                    | TCP                | Akkiw | [Microsoft Entra ID, Microsoft Graph,](api-management-howto-aad.md) and Azure Key Vault dependency  (optional)                | External & Internal  |
+| Outbound | VirtualNetwork | * |  AzureActiveDirectory | 443                    | TCP                | Allow | [Microsoft Entra ID, Microsoft Graph,](api-management-howto-aad.md) and Azure Key Vault dependency  (optional)                | External & Internal  |
 | Outbound | VirtualNetwork | * | AzureKeyVault| 443                     |  TCP                | Allow                | Access to Azure Key Vault for [named values](api-management-howto-properties.md) integration (optional)                         | External & Internal  |
 | Outbound | VirtualNetwork | * | AzureConnectors | 443                  |  TCP                | Allow | [managed connections](credentials-overview.md) dependency (optional)              | External & Internal  |
 | Outbound | VirtualNetwork| * | Sql | 1433                     |  TCP                | Allow                 | **Access to Azure SQL endpoints**                           | External & Internal  |

articles/app-service/environment/auto-migration.md

@@ -147,7 +147,7 @@ The following are notable changes in App Service Environment v3:
 
 There's no cost associated with auto-migrating your App Service Environment. You stop being charged for your previous App Service Environment as soon as it shuts down during the migration process. You begin getting charged for your new App Service Environment v3 as soon as it gets deployed. For more information about App Service Environment v3 pricing, see the [pricing details](overview.md#pricing).
 
-When you migrate to App Service Environment v3 from previous versions, there are scenarios that you should consider that can potentially reduce your monthly cost. Consider [reservations](../../cost-management-billing/reservations/reservation-discount-app-service.md#how-reservation-discounts-apply-to-isolated-v2-instances) and [savings plans](../../cost-management-billing/savings-plan/savings-plan-compute-overview.md) to further reduce your costs. For information on cost saving opportunities, see [Cost saving opportunities after upgrading to App Service Environment v3](upgrade-to-asev3.md#cost-saving-opportunities-after-upgrading-to-app-service-environment-v3).
+When you migrate to App Service Environment v3 from previous versions, there are scenarios that you should consider that can potentially reduce your monthly cost. Consider [reservations](../../cost-management-billing/reservations/reservation-discount-app-service.md#how-reservation-discounts-apply-to-instances) and [savings plans](../../cost-management-billing/savings-plan/savings-plan-compute-overview.md) to further reduce your costs. For information on cost saving opportunities, see [Cost saving opportunities after upgrading to App Service Environment v3](upgrade-to-asev3.md#cost-saving-opportunities-after-upgrading-to-app-service-environment-v3).
 
 > [!NOTE]
 > Due to the conversion of App Service plans from Isolated to Isolated v2, your apps may be over-provisioned after the migration since the Isolated v2 tier has more memory and CPU per corresponding instance size. You'll have the opportunity to [scale your environment](../manage-scale-up.md) as needed once migration is complete. For more information, review the [SKU details](https://azure.microsoft.com/pricing/details/app-service/windows/).

articles/automation/automation-runbook-authoring.md

@@ -1,5 +1,5 @@
 ---
-title: Runbook authoring using VS code in Azure Automation
+title: Runbook authoring using VS Code in Azure Automation
 description: This article provides an overview authoring runbooks in Azure Automation using the visual studio code.
 services: automation
 ms.subservice: process-automation

articles/automation/automation-runbook-types.md

@@ -68,7 +68,7 @@ The following are the current limitations and known issues with PowerShell runbo
 > [!NOTE]
 > Currently, PowerShell 7.2 runtime version is supported for both Cloud and Hybrid jobs in all Public regions except Central India, UAE Central, Israel  Central, Italy North, and Germany North.
 
-- For the PowerShell 7.2 runtime version, the module activities aren't extracted for the imported modules. Use [Azure Automation extension for VS code](automation-runbook-authoring.md) to simplify runbook authoring experience. 
+- For the PowerShell 7.2 runtime version, the module activities aren't extracted for the imported modules. Use [Azure Automation extension for VS Code](automation-runbook-authoring.md) to simplify runbook authoring experience. 
 - PowerShell 7.x doesn't support workflows. For more information, see [PowerShell workflow](/powershell/scripting/whats-new/differences-from-windows-powershell#powershell-workflow) for more details.
 - PowerShell 7.x currently doesn't support signed runbooks.
 - Source control integration doesn't support PowerShell 7.2. Also, PowerShell 7.2 runbooks in source control get created in Automation account as Runtime 5.1.

articles/automation/whats-new.md

@@ -83,7 +83,7 @@ On **31 August 2024**, Azure Automation will  retire [Automation Update manageme
 
 ### General Availability: Azure Automation supports PowerShell 7.2 runbooks
 
-Azure Automation announces General Availability of PowerShell 7.2 runbooks. This enables you to author runbooks in the long-term supported version of PowerShell using [Azure Automation extension for VS code](how-to/runbook-authoring-extension-for-vscode.md) and execute them on a secure and reliable platform. [Learn more](automation-runbook-types.md).
+Azure Automation announces General Availability of PowerShell 7.2 runbooks. This enables you to author runbooks in the long-term supported version of PowerShell using [Azure Automation extension for VS Code](how-to/runbook-authoring-extension-for-vscode.md) and execute them on a secure and reliable platform. [Learn more](automation-runbook-types.md).
 
 ## October 2023
 

articles/azure-netapp-files/azure-netapp-files-metrics.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 03/18/2025
+ms.date: 04/16/2025
 ms.author: anfdocs
 ---
 # Metrics for Azure NetApp Files
@@ -150,21 +150,39 @@ Azure NetApp Files metrics are natively integrated into Azure monitor. From with
 
 Azure NetApp Files provides metrics on allocated storage, actual storage usage, volume I/OPS, and latency. Use these metrics to understand usage and performance.
 
-- *Percentage Volume Consumed Size*    
+- *Percentage Volume Consumed Size*
+
     The percentage of the volume consumed, including snapshots.  
     Aggregation metrics (for example, min, max) aren't supported for percentage volume consumed size.
-- *Volume Allocated Size*   
+- *Volume Allocated Size* 
+  
     The provisioned size of a volume
 - *Volume Quota Size*    
+
     The quota size (GiB) the volume is provisioned with.   
 - *Volume Consumed Size*   
+
     Logical size of the volume (used bytes).  
     This size includes logical space used by active file systems and snapshots.  
 - *Volume Snapshot Size*   
+ 
    The size of all snapshots in a volume.  
+- *Volume Inodes Quota*
+    
+    The volume's maximum allowed [inodes (or `maxfiles`)](maxfiles-concept.md) if the limit was increased via support request. If the limit hasn't been increased via support request, this metric's value is 0.
+
+- *Volume Inodes Total*
+
+    The volume's maximum allowed [inodes (or `maxfiles`)](maxfiles-concept.md) based on the volume size.
+- *Volume Inodes Used*
+
+    The volume's used [inodes (or `maxfiles`)](maxfiles-concept.md).
+
 - *Volume Inodes Percentage* 
 
-    The percentage of the volume's available [inodes (or `maxfiles`)](maxfiles-concept.md) consumed. 
+    The percentage of the volume's available [inodes (or `maxfiles`)](maxfiles-concept.md) consumed.
+
+    If the volume inode limit has been increased by a support request, the percentage is calculated based on Volume Inodes Quota metric. If the volume inode limit is the default value based on the volume size, the percentage is calculated based on the Volume Inodes Total metric.
 
 - *Throughput limit reached*
 

articles/azure-netapp-files/maxfiles-concept.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 03/18/2025
+ms.date: 04/16/2025
 ms.author: anfdocs
 ---
 # Understand `maxfiles` limits in Azure NetApp Files
@@ -41,7 +41,7 @@ The following table shows examples of the relationship `maxfiles` values based o
 | 200 TiB (214,748,364,800 KiB)	| 6,375,342,024  |
 | 500 TiB (536,870,912,000 KiB)	| 15,938,355,048 |
 
-To see the `maxfiles` allocation for a specific volume size, check the **Maximum number of files** field in the volume’s overview pane. You can also view the `maxfiles` consumption for a volume as a percentage in [Azure monitor](azure-netapp-files-metrics.md#volumes).
+To see the `maxfiles` allocation for a specific volume size, check the **Maximum number of files** field in the volume’s overview pane. You can also view metrics for available and consumed `maxfiles` in [Azure monitor](azure-netapp-files-metrics.md#volumes).
 
 :::image type="content" source="./media/azure-netapp-files-resource-limits/maximum-number-files.png" alt-text="Screenshot of volume overview menu." lightbox="./media/azure-netapp-files-resource-limits/maximum-number-files.png":::
 

articles/azure-netapp-files/whats-new.md

@@ -6,7 +6,7 @@ author: b-hchen
 ms.service: azure-netapp-files
 ms.custom: linux-related-content
 ms.topic: overview
-ms.date: 04/01/2025
+ms.date: 04/16/2025
 ms.author: anfdocs
 ---
 
@@ -16,6 +16,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## April 2025
 
+* [New volume usage metrics:](azure-netapp-files-metrics.md#volumes) Volume Inodes Quota, Volume Inodes Total, Volume Inodes Used
+
+    Azure NetApp Files supports [new metrics](azure-netapp-files-metrics.md#volumes) to monitor consumption of [inodes (also known as maxfiles)](maxfiles-concept.md), which is the maximum number of files a volume can hold. These metrics are especially useful for workloads with high file counts, such as high-performance compute (HPC) or electronic design automation (EDA), where you might have millions of small files. By monitoring these metrics, you can avoid running out of inodes thus keeping your storage running smoothly and making it easier to plan for future needs.
+
 * [File access logs](manage-file-access-logs.md) (preview)
 
     File Access Logs provides detailed logging of file access activities, including user identity, operation type, and timestamps, enhancing security, reliability, and operational insights. It supports SMB, NFSv4.1, and dual-protocol volumes, offering valuable features for monitoring unauthorized access, tracing activity for compliance, resolving incidents, and optimizing data usage patterns. By embedding this capability, you can strengthen your organization's security posture, maintain system reliability, and achieve operational excellence in alignment with the Well-Architected Framework security best practices. Azure NetApp Files file access logs play a critical role in safeguarding sensitive data, detecting anomalies while enabling operational excellence.