Merge pull request #294614 from MicrosoftDocs/main

2/13/2025 AM Publish

Author: Taojunshen

.github/policies/disallow-edits.yml

@@ -190,5 +190,5 @@ configuration:
         then:
           - addReply:
               reply: >-
-                @${issueAuthor} - This PR modifies the breadcrumb file for the entire repository in this pull request; the breadcrumb supports 100s of services. Please make sure your changes to the breadcrumb file are intentional. Do not delete this file. 
+                @${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/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-vmware/configure-azure-elastic-san.md

@@ -14,6 +14,8 @@ This article explains how to use Azure Elastic SAN as backing storage for Azure
 
 Azure Elastic storage area network (SAN) addresses the problem of workload optimization and integration between your large scale databases and performance-intensive mission-critical applications. For more information on Azure Elastic SAN, see [What is Azure Elastic SAN?](../storage/elastic-san/elastic-san-introduction.md).
 
+To accompany the steps below, you can use this [interactive demo](https://regale.cloud/microsoft/play/4092/expand-storage-with-elastic-san#/0/0) as a visual representation of what you need to do to connect Elastic SAN and AVS.
+
 ## Prerequisites
 
 The following prerequisites are required to continue.

articles/energy-data-services/how-to-enable-legal-tags-restricted-country-of-origin.md

@@ -0,0 +1,77 @@
+---
+title: Microsoft Azure Data Manager for Energy - How to enable legal tag creation for restricted country of origin data
+description: "This article describes how to enable legal tag creation for restricted country of origin data."
+author: bharathim
+ms.author: bselvaraj
+ms.service: azure-data-manager-energy
+ms.topic: how-to #Don't change
+ms.date: 02/08/2025
+
+#customer intent: As a data manager, I need an ability to create legal tag definitions for restricted country of origin data.
+
+---
+# How to enable legal tag creation for OSDU® restricted COO (Country of Origin) data?
+Legal tag definitions represent the legal status of the data hosted on an Azure Data Manager for Energy resource. A valid legal tag is required for data ingestion and retrieval stored on the resource. See [How to manage legal tags](how-to-manage-legal-tags.md).
+
+## COO (Country of Origin) configuration
+The creation of legal tags is governed by a configuration hosted on each Azure Data Manager for Energy resource, defined in OSDU® as the [legal service default configuration](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/blob/master/legal-core/src/main/resources/DefaultCountryCode.json?ref_type=heads). This is a JSON configuration that defines data residency risk for data originating from these countries using the parameter **residencyRisk** and the data types to which this risk status doesn't apply using the parameter **typesNotApplyDataResidency**. Below is a sample configuration for data originating from Australia as an example:
+
+```json
+{
+    "name": "Australia",
+    "alpha2": "AU",
+    "numeric": 36,
+    "residencyRisk": "No restriction",
+    "typesNotApplyDataResidency": ["Transferred Data"]
+}
+```
+
+The **residencyRisk** can take the values `default`, `Not Assigned`, `Embargoed`, and `No restriction`. For countries configured as `No restriction`, creating legal tags and later data ingestion is allowed. However, for all other statuses, an attempt to create legal tags would fail.
+
+For countries with status as `default` and `Not Assigned`, the default configuration can be overridden by changing the residencyRisk to `client consent required` in a legal service configuration maintained in `Legal_COO.json`. This change in configuration is the recommended method to enable legal tags for restricted COO. As an example, Brazil’s default status doesn't allow the creation of legal tags for data ingestion with Brazil as the COO:
+
+```json
+{
+  "name": "Brazil",
+  "alpha2": "BR",
+  "numeric": 76,
+  "residencyRisk": "Default",
+  "typesNotApplyDataResidency": ["Transferred Data"]
+}
+```
+
+However, the configuration can be changed as below in the `Legal_COO.json` for the partition to allow the creation of legal tags:
+
+```json
+{
+  "name": "Brazil",
+  "alpha2": "BR",
+  "numeric": 76,
+  "residencyRisk": "Client consent required",
+  "typesNotApplyDataResidency": ["Transferred Data"]
+}
+```
+
+> [!NOTE]
+> The configuration change is specific to the data partition in which the configuration is applied. Hence, these change requests require the reference of the data partition.
+
+To enable this change, you should raise a support ticket on the Azure portal using the following information:
+- Subscription ID
+- Region in which the instance is deployed
+- Azure Data Manager for Energy developer tier resource name
+- Data partition name on which the configuration is to be changed.
+- List of country-specific configurations with new values to be applied (as shown above).
+
+> [!TIP]
+> Multiple partition configuration changes can be submitted in the same request by clearly specifying the partition name and the associated country-specific configuration changes.
+
+> [!NOTE]
+> The country-specific configuration can also be reversed to the original state of 'default' or 'Not Assigned' if the customer chooses.
+
+> [!IMPORTANT]
+> Microsoft isn't responsible for, and consults not or recommends changes to the **residencyRisk** status of country-specific configurations. The customer, by making such a request to allow data from these countries of origin by changing the configuration, is doing so at their own risk and understanding.
+
+## Related content
+
+* [Legal service](https://osdu.pages.opengroup.org/platform/security-and-compliance/legal/)
+* [Allow data ingestion from specific country of origin](https://osdu.pages.opengroup.org/platform/security-and-compliance/legal/AllowDataIngestionFromCertainCOO/)

articles/energy-data-services/index.yml

@@ -74,6 +74,8 @@ landingContent:
             url: tutorial-petrel-ddms.md
           - text: Reservoir DDMS API tutorial
             url: tutorial-reservoir-ddms-apis.md
+          - text: Reservoir DDMS websocket API tutorial
+            url: tutorial-reservoir-ddms-websocket.md
       - linkListType: how-to-guide
         links:
           - text: How to convert SEG-Y to oVDS
@@ -86,6 +88,8 @@ landingContent:
             url: how-to-enable-external-data-sources.md
           - text: How to register External Data Sources (EDS)
             url: how-to-register-external-data-sources.md
+          - text: How to enable legal tags restricted COO (Country of Origin)
+            url: how-to-enable-legal-tags-restricted-country-of-origin.md
   - title: Administration
     linkLists:
       - linkListType: how-to-guide