Merge branch 'main' into release-psqlflex-backup

Author: v-alje

.github/policies/disallow-edits.yml

@@ -177,4 +177,18 @@ configuration:
               label: do-not-merge
           - removeLabel:
               label: ready-to-merge
-
+      
+      - description: Write a message if the breadcrumb file is modified in the azure-docs-pr repository.
+        if:
+        - payloadType: Pull_Request
+        - isAction:
+            action: Opened
+        - filesMatchPattern:
+              matchAny: true
+              pattern: bread/*
+              
+        then:
+          - addReply:
+              reply: >-
+                @${issueAuthor} - This PR modifies the breadcrumb file for the entire repository: bread/toc.yml. This file supports the on-site navigation for 100s of services. Please make sure your changes to the breadcrumb file are intentional. Do not delete this file. 
+          

.github/workflows/stale.yml

@@ -0,0 +1,40 @@
+name: Mark stale pull requests
+
+permissions:
+  issues: write
+  pull-requests: write
+      
+on:
+  schedule:
+  - cron: "0 */6 * * *"
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+   
+    steps:
+    - uses: actions/stale@v3
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        days-before-pr-stale: 14
+        days-before-pr-close: 90
+        stale-pr-label: inactive
+        close-pr-label: auto-close
+        exempt-pr-labels: keep-open
+        operations-per-run: 1300
+        ascending: false
+        # start-date: '2021-03-19'
+        stale-pr-message: >
+          This pull request has been inactive for at least 14 days.
+
+          If you are finished with your changes, don't forget to sign off. See the [platform guide](https://review.learn.microsoft.com/help/platform/prmerger-hashtag-commands?branch=main) for instructions.
+             
+          [Get Help](https://review.learn.microsoft.com/help/platform/help-options?branch=main)  
+          
+          [Learn Support Teams Channel](https://teams.microsoft.com/l/channel/19%3a7ecffca1166a4a3986fed528cf0870ee%40thread.skype/General?groupId=de9ddba4-2574-4830-87ed-41668c07a1ca&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47)  
+          
+          [Resolve Merge Conflicts](https://review.learn.microsoft.com/help/contribute/resolve-merge-conflicts?branch=main)  
+        close-pr-message: >
+          This pull request has been inactive for 90 days, and an `auto-close` label has been added. At this time, the system is closing the PR automatically. If you decide to continue working on your changes, scroll to the bottom of the pull request comments and select the **Reopen pull request** button.
+          <br/>

articles/app-service/configure-language-python.md

@@ -19,6 +19,9 @@ This article describes how [Azure App Service](overview.md) runs Python apps, ho
 
 The App Service deployment engine automatically activates a virtual environment and runs `pip install -r requirements.txt` for you when you deploy a [Git repository](deploy-local-git.md), or when you deploy a [zip package](deploy-zip.md) [with build automation enabled](deploy-zip.md#enable-build-automation-for-zip-deploy).
 
+> [!NOTE]
+> Currently App Service requires `requirements.txt` in your project's root directory, even if you're using modern Python packaging tools such as `pyproject.toml`.
+
 This guide provides key concepts and instructions for Python developers who use a built-in Linux container in App Service. If you've never used Azure App Service, first follow the [Python quickstart](quickstart-python.md) and [Flask](tutorial-python-postgresql-app-flask.md), [Django](tutorial-python-postgresql-app-django.md), or [FastAPI](tutorial-python-postgresql-app-fastapi.md) with PostgreSQL tutorial.
 
 You can use either the [Azure portal](https://portal.azure.com) or the Azure CLI for configuration:

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

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 11/19/2021
+ms.date: 11/19/2024
 ms.author: anfdocs
 ---
 # Manage volumes in an application volume group for SAP HANA
@@ -14,24 +14,24 @@ You can manage a volume from its volume group. You can resize, delete, or change
 
 ## Steps
 
-1. From your NetApp account, select **Application volume groups**. Click a volume group to display the volumes in the group.  
+1. From your NetApp account, select **Application volume groups**. Select a volume group to display the volumes in the group.  
 
 2. Select the volume you want to resize, delete, or change throughput. The volume overview is displayed. 
 
     [![Screenshot that shows Application Volume Groups overview page.](./media/application-volume-group-manage-volumes/application-volume-group-overview.png)](./media/application-volume-group-manage-volumes/application-volume-group-overview.png#lightbox)  
 
-    * To resize the volume, click **Resize** and specify the quota in GiB.
+    * To resize the volume, select **Resize** and specify the quota in GiB.
 
     ![Screenshot that shows the Update Volume Quota window.](./media/application-volume-group-manage-volumes/application-volume-resize.png)
 
-    * To change the throughput for the volume, click **Change throughput** and specify the intended throughput in MiB/s.
+    * To change the throughput for the volume, select **Change throughput** and specify the intended throughput in MiB/s.
 
     ![Screenshot that shows the Change Throughput window.](./media/application-volume-group-manage-volumes/application-volume-change-throughput.png)
 
-    * To delete the volume in the volume group, click **Delete**. If you are prompted, type the volume name to confirm the deletion.  
+    * To delete the volume in the volume group, select **Delete**. If prompted, enter the volume name to confirm the deletion.  
 
     > [!IMPORTANT]
-    > The volume deletion operation cannot be undone.
+    > Volume deletion is permanent. It can't be undone.
     
     ![Screenshot that shows the Delete Volume window.](./media/application-volume-group-manage-volumes/application-volume-delete.png)
 

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

@@ -4,9 +4,9 @@ description: Learn how to connect to Azure Government to use Azure NetApp Files
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
-ms.custom: devx-track-azurecli, has-azure-ad-ps-ref
+ms.custom: devx-track-azurecli, no-azure-ad-ps-ref
 ms.topic: conceptual
-ms.date: 07/17/2024
+ms.date: 02/13/2025
 ms.author: anfdocs
 ---
 
@@ -70,10 +70,11 @@ When you connect to Azure Government through PowerShell, you must specify an env
 
 | Connection type | Command | 
 | --- | --- | 
-| [Azure](/powershell/module/az.accounts/Connect-AzAccount) commands |`Connect-AzAccount -EnvironmentName AzureUSGovernment` | 
-| [Microsoft Entra ID](/powershell/module/azuread/connect-azuread) commands |`Connect-AzureAD -AzureEnvironmentName AzureUSGovernment` | 
-| [Azure (Classic deployment model)](/powershell/module/servicemanagement/azure/add-azureaccount) commands |`Add-AzureAccount -Environment AzureUSGovernment` | 
-| [Microsoft Entra ID (Classic deployment model)](/previous-versions/azure/jj151815(v=azure.100)) commands |`Connect-MsolService -AzureEnvironment UsGovernment` | 
+| [Azure](/powershell/module/az.accounts/Connect-AzAccount) commands | `Connect-AzAccount -EnvironmentName AzureUSGovernment` | 
+| [Microsoft Graph PowerShell](/powershell/microsoftgraph/authentication-commands) | `Connect-MgGraph -Environment USGov` |
+| [Microsoft Entra PowerShell](/powershell/module/microsoft.entra/connect-entra) | `Connect-Entra -Environment USGov` | 
+| [Azure (Classic deployment model)](/powershell/module/servicemanagement/azure/add-azureaccount) commands | `Add-AzureAccount -Environment AzureUSGovernment` | 
+| [Microsoft Entra ID (Classic deployment model)](/previous-versions/azure/jj151815(v=azure.100)) commands | `Connect-MsolService -AzureEnvironment UsGovernment` | 
 
 For more information, see [Connect to Azure Government with PowerShell](../azure-government/documentation-government-get-started-connect-with-ps.md).
 
@@ -83,4 +84,4 @@ For more information, see [Connect to Azure Government with PowerShell](../azure
 * [What's new in Azure NetApp Files](whats-new.md)
 * [Compare Azure Government and global Azure](../azure-government/compare-azure-government-global-azure.md)
 * [Azure NetApp Files REST API](azure-netapp-files-develop-with-rest-api.md)
-* [Azure NetApp Files REST API using PowerShell](develop-rest-api-powershell.md)
+* [Azure NetApp Files REST API using PowerShell](develop-rest-api-powershell.md)

articles/azure-netapp-files/cross-region-replication-requirements-considerations.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 09/12/2024
+ms.date: 02/13/2025
 ms.author: anfdocs
 ---
 
@@ -37,29 +37,6 @@ This article describes requirements and considerations about [using the volume c
 * [Large volumes](large-volumes-requirements-considerations.md) are supported with cross-region replication only with an hourly or daily replication schedule.
 * If the volume's size exceeds 95% utilization, there's a risk that replication to the destination volume can fail depending on the rate of data changes. 
 
-## Large volumes configuration
-
-[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) are supported with cross-region replication. You must [first register for the large volumes feature](large-volumes-requirements-considerations.md#register-the-feature) then register to use large volumes with cross-region replication:
-
->[!NOTE]
->Cross-zone and cross-region replication use the same Azure Feature Exposure Control (AFEC) name of `ANFLargeVolumesCRR`. If you've registered for cross-zone replication, the registration also works for cross-region replication. 
-
-1.  Register the feature by running the following commands:
-
-    ```azurepowershell-interactive
-    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFLargeVolumesCRR
-    ```
-
-2. Check the status of the feature registration: 
-
-    > [!NOTE]
-    > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is `Registered` before continuing.
-    ```azurepowershell-interactive
-    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFLargeVolumesCRR
-    ```
-
-You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 
-
 ## Next steps
 * [Create volume replication](cross-region-replication-create-peering.md)
 * [Display health status of replication relationship](cross-region-replication-display-health-status.md)

articles/azure-netapp-files/cross-zone-replication-requirements-considerations.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 07/30/2024
+ms.date: 02/13/2025
 ms.author: anfdocs
 ---
 # Requirements and considerations for using cross-zone replication 
@@ -25,37 +25,14 @@ This article describes requirements and considerations about [using the volume c
 * Azure NetApp Files replication doesn't currently support multiple subscriptions; all replications must be performed under a single subscription.
 * See [resource limits](azure-netapp-files-resource-limits.md) for the maximum number of cross-zone destination volumes. You can open a support ticket to [request a limit increase](azure-netapp-files-resource-limits.md#request-limit-increase) in the default quota of replication destination volumes (per subscription in a region). 
 * There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.  
-* Cross-zone replication does not support cascading and fan in/out topologies.
-* After you set up cross-zone replication, the replication process creates *SnapMirror snapshots* to provide references between the source volume and the destination volume. SnapMirror snapshots are cycled automatically when a new one is created for every incremental transfer. You cannot delete SnapMirror snapshots until you delete the replication relationship and volume. 
-* You cannot mount a dual-protocol volume until you [authorize replication from the source volume](cross-region-replication-create-peering.md#authorize-replication-from-the-source-volume) and the initial [transfer](cross-region-replication-display-health-status.md#display-replication-status) happens.
-* You can delete manual snapshots on the source volume of a replication relationship when the replication relationship is active or broken, and also after you've deleted replication relationship. You cannot delete manual snapshots for the destination volume until you break the replication relationship.
-* When reverting a source volume with an active volume replication relationship, only snapshots that are more recent than the SnapMirror snapshot can be used in the revert operation. For more information, see [Revert a volume using snapshot revert with Azure NetApp Files](snapshots-revert-volume.md).
+* Cross-zone replication doesn't support cascading and fan in/out topologies.
+* After you set up cross-zone replication, the replication process creates *SnapMirror snapshots* to provide references between the source volume and the destination volume. SnapMirror snapshots are cycled automatically when a new one is created for every incremental transfer. You can't delete SnapMirror snapshots until you delete the replication relationship and volume. 
+* You can't mount a dual-protocol volume until you [authorize replication from the source volume](cross-region-replication-create-peering.md#authorize-replication-from-the-source-volume) and the initial [transfer](cross-region-replication-display-health-status.md#display-replication-status) happens.
+* You can delete manual snapshots on the source volume of a replication relationship when the replication relationship is active or broken, and also after you've deleted replication relationship. You can't delete manual snapshots for the destination volume until you break the replication relationship.
+* When you revert a source volume with an active volume replication relationship, only snapshots dated more recently than the SnapMirror snapshot can be used in the revert operation. For more information, see [Revert a volume using snapshot revert with Azure NetApp Files](snapshots-revert-volume.md).
 * Data replication volumes support [customer-managed keys](configure-customer-managed-keys.md).
 * [Large volumes](large-volumes-requirements-considerations.md) are supported with cross-zone replication only with an hourly or daily replication schedule.
 
-## Large volumes configuration
-
-[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) are supported in cross-zone replication. You must [first register for the large volumes feature](large-volumes-requirements-considerations.md#register-the-feature) then register to use large volumes with cross-zone replication:
-
->[!NOTE]
->Cross-zone and cross-region replication use the same Azure Feature Exposure Control (AFEC) name of `ANFLargeVolumesCRR`. If you've registered for cross-region replication, the registration also works for cross-zone replication. 
-
-1.  Register the feature by running the following commands:
-
-    ```azurepowershell-interactive
-    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFLargeVolumesCRR
-    ```
-
-2. Check the status of the feature registration: 
-
-    > [!NOTE]
-    > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is `Registered` before continuing.
-    ```azurepowershell-interactive
-    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFLargeVolumesCRR
-    ```
-
-You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 
-
 ## Next steps
 * [Understand cross-zone replication](cross-zone-replication-introduction.md)
 * [Create cross-zone replication relationships](create-cross-zone-replication.md)

articles/azure-netapp-files/regional-capacity-quota.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 10/11/2021
+ms.date: 10/11/2024
 ms.author: anfdocs
 ---
 # Regional capacity quota for Azure NetApp Files
@@ -14,7 +14,7 @@ This article explains regional capacity quota of Azure NetApp Files.
 
 ## Display regional capacity quota
 
-You can click **Quota** under Settings of Azure NetApp Files to display the current and default quota sizes for the region. 
+You can select **Quota** under Settings of Azure NetApp Files to display the current and default quota sizes for the region. 
 
 For example: 
 

articles/azure-netapp-files/request-region-access.md

@@ -5,12 +5,12 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 11/15/2021
+ms.date: 02/10/2025
 ms.author: anfdocs
 ---
 # Request region access for Azure NetApp Files
 
-In some special situations, you might need to explicitly request access to a region. This article explains how to submit a request. 
+In special situations, you need to explicitly request access to a region. Learn how to submit a request. 
 
 ## Steps
 
@@ -23,7 +23,7 @@ In some special situations, you might need to explicitly request access to a reg
 
     ![Screenshot that shows the Problem Description tab.](./media/shared/support-problem-descriptions.png)
 
-3. Under the **Additional details** tab, click **Enter details** in the Request Details field.  
+3. In the **Additional details** tab, select **Enter details** in the Request Details field.  
 
     ![Screenshot that shows the Details tab and the Enter Details field.](./media/shared/quota-additional-details.png)
 
@@ -33,7 +33,7 @@ In some special situations, you might need to explicitly request access to a reg
 
     ![Screenshot that shows the Quota Details window for requesting region access.](./media/request-region-access/quota-details-region-access.png)
 
-5. Click **Save and continue**. Click **Review + create** to create the request.
+5. Select **Save and continue**. Click **Review + create** to create the request.
 
 ## Next steps