Merge pull request #302204 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

articles/automation/runtime-environment-overview.md

@@ -36,7 +36,7 @@ Runtime environment captures the following details about the job execution envir
 - **Runtime version** - The version of the language selected for runbook execution. For example - PowerShell 7.4 and Python 3.10.
 - **Packages** - The packages are the assemblies and the *.dll* files that you import and required by runbooks for execution. There are two types of packages supported for Runtime environment.
 
-   |**Package Types** | **Description** |
+   |**Package types** | **Description** |
    |---------|---------|
    |**Default packages**  | The packages enable you to manage Azure resources. For example, Az PowerShell 12.3.0, Azure CLI 2.64.0|
    |**Customer-provided packages** | These are custom packages that are required by runbooks during execution. The packages can be from: </br> - Public gallery: PSGallery, pypi </br> - Self-authored |
@@ -83,7 +83,7 @@ You can't edit these Runtime environments. However, any changes that are made in
 - RBAC permissions cannot be assigned to Runtime environment.
 - Runtime environment can't be configured through Azure Automation extension for Visual Studio Code.
 - Deleted Runtime environments cannot be recovered.  
-- This feature is currently supported through Azure portal and [REST API](/rest/api/automation/runtime-environments?view=rest-automation-2023-05-15-preview&preserve-view=true).
+- This feature is currently supported through Azure portal and [REST API](/rest/api/automation/runtime-environments?view=rest-automation-2024-10-23&preserve-view=true).
 - Management of modules for Azure Automation State Configuration is not supported through Runtime environment experience. You can continue using the old experience for managing modules and packages for Azure Automation State Configuration.
 
 ## Switch between new and old experience

articles/data-factory/connector-lifecycle-overview.md

@@ -9,7 +9,7 @@ ms.topic: concept-article
 ms.custom:
   - references_regions
   - build-2025
-ms.date: 05/27/2025
+ms.date: 06/25/2025
 ---
 
 # Connector lifecycle overview
@@ -45,7 +45,7 @@ A connector lifecycle includes multiple stages with thorough and measurable asse
 | Private Preview      | The private preview phase marks the initial release of a new connector version to limited users. During this phase, opt-in users can use the latest version of the connector and provide feedback. | 3 months or above       |
 | Public Preview      | This stage marks the initial release of a new connector version to all users publicly. During this phase, users are encouraged to try the latest connector version and provide feedback. For newly created connections, it defaults to the latest connector version. Users can switch back to the previous version. | 1 month or above*       |
 | General Availability  | Once a connector version meets the General Availability (GA) criteria, it's released to the public and is suitable for production workloads. To reach this stage, the new connector version must meet the requirements in terms of performance, reliability, and its capability to meet business needs. | 12 months or above*     |
-| End-of-Support (EOS) announced | When a connector version reaches its EOS, it will not receive any further updates or support. Typically, a three to six-month notice is given before the EOS date of this version. This is documented together with the version removal date. | 3-6 months before the end-of-support date* |
+| End-of-Support (EOS) announced | When a connector version reaches its EOS, it will not receive any further updates or support. A six-month notice is announced before the EOS date of this version. This is documented together with the removal date. | 6 months before the end-of-support date* |
 | End-of-Support (EOS)  | Once the previously announced EOS date arrives, the connector version becomes officially unsupported. This implies that it will not receive any updates or bug fixes, and no official support will be provided. Users will not be able to create new workloads on a version that is under EOS stage. Using an unsupported connector version is at the user's own risk. The workload running on EOS version may not fail immediately, the service might expedite moving into the final stage at any time, at Microsoft's discretion due to outstanding security issues, or other factors. | /                        |
 | Version removed  | Once the connector version passes its EOS date, the service will remove all related components associated with this connector version. This implies that pipelines using this connector version will discontinue to execute. | 1-12 months after the end of support date* |
 
@@ -60,14 +60,36 @@ To manage connection updates effectively, it's important to understand versionin
 
 ## How Data Factory handles connector version upgrade
 
-**Major and minor version** updates may include changes that can impact your pipeline output or related components. To help you prepare, we will notify you in advance, providing a window for testing and upgrading to the latest version. Specific examples of version changes can be found in the documentation for each individual connector. We recommend reviewing and upgrading to new versions as early as possible to take advantage of the latest enhancements and ensure your pipelines continue to run smoothly and reliably.
+**Major and minor version** updates may include changes that can impact your pipeline output or related components. To help you prepare, we will notify you in advance, providing a window for testing and upgrading to the latest version. Specific examples of version changes can be found in the documentation for each individual connector. We recommend reviewing and upgrading to the latest version as early as possible to take advantage of the up-to-date enhancements and ensure your pipelines continue to run smoothly and reliably.
 
 When new versions are released, the service starts to always set to the latest new versions by default for all newly created linked service. At that time, users can fall back to the earlier version if needed.
 
 When a version reaches its end-of-support date, users are no longer allowed to create new linked service on that version.
 
 In addition to major and minor version updates, the service also delivers new features and bug fixes that are fully backward compatible with your existing setup. These changes do not require a version update to the connector. Depending on the nature of the change, users may either receive the improvements automatically or have the option to enable new features as needed. This approach ensures a seamless experience while maintaining stability and flexibility.
 
+## Automatic connector upgrade 
+
+In addition to providing [tools](connector-upgrade-advisor.md) and [best practices](connector-upgrade-guidance.md) to help users manually upgrade their connectors, the service now also provides a more streamlined upgrade process for some cases where applicable. This is designed to help users adopt the most reliable and supported connector versions with minimal disruption.
+
+The following section outlines the general approach that the service takes for automatic upgrades. While this provides a high-level overview, it is strongly recommended to review the documentation specific to each connector to understand which scenarios are supported and how the upgrade process applies to your workloads.
+
+In cases where certain scenarios running on the latest GA connector version are fully backward compatible with the previous version, the service will automatically upgrade existing workloads (such as Copy, Lookup, and Script activities) to a compatibility mode that preserves the behavior of the earlier version.
+
+These auto-upgraded workloads are not affected by the announced removal date of the older version, giving users additional time to evaluate and transition to the latest GA version without facing immediate failures. 
+
+You can identify which activities have been automatically upgraded by inspecting the activity output, where relevant upgrade information is recorded.
+
+> [!NOTE]
+> While compatibility mode offers flexibility, we strongly encourage users to upgrade to the latest GA version as soon as possible to benefit from ongoing improvements, optimizations, and full support. 
+
+You can find more details from the table below on the connector list that is planned for the automatic upgrade.  
+
+| Connector        | Scenario |
+|------------------|----------|
+| [Google BigQuery](connector-google-bigquery.md)  | Scenario that does not rely on below capability in Google BigQuery V1:<br><br>  • Use `trustedCertsPath`, `additionalProjects`, `requestgoogledrivescope` connection properties.<br>  • Set `useSystemTrustStore` connection property as `false`.<br>  • Use **STRUCT** and **ARRAY** data types. |
+| [Teradata](connector-teradata.md)         | Scenario that does not rely on below capability in Teradata (version 1.0):<br><br>  • Set below value for **CharacterSet**:<br>&nbsp;&nbsp;• BIG5 (TCHBIG5_1R0)<br>&nbsp;&nbsp;• EUC (Unix compatible, KANJIEC_0U)<br>&nbsp;&nbsp;• GB (SCHGB2312_1T0)<br>&nbsp;&nbsp;• IBM Mainframe (KANJIEBCDIC5035_0I)<br>&nbsp;&nbsp;- NetworkKorean (HANGULKSC5601_2R4)<br>&nbsp;&nbsp;• Shift-JIS (Windows, DOS compatible, KANJISJIS_0S)|
+
 ## Related content
 
 - [Connector overview](connector-overview.md)  

articles/sap/center-sap-solutions/get-sap-installation-media.md

@@ -89,7 +89,7 @@ Next, set up a virtual machine (VM) where you will download the SAP components l
     curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
     ```
 
-1. If the Azure CLI version is not version 2.30.0 or higher, [Update the Azure CLI](/cli/azure/update-azure-cli). You can run below command to check the version
+1. If the Azure CLI version is not version 2.30.0 or higher(except 2.74.0), [Update the Azure CLI](/cli/azure/update-azure-cli). You can run below command to check the version
 
     ```azurecli
     az --version
@@ -108,20 +108,20 @@ Next, set up a virtual machine (VM) where you will download the SAP components l
     sudo apt install python3-pip
     ```
 
-1. Install Ansible 2.11.12 on the VM.
+1. Install Ansible 2.16.14 on the VM.
 
     ```Bash
-    sudo pip3 install ansible-core==2.11.12
+    sudo pip3 install ansible-core==2.16.14
     ```
 
 1. Install Ansible galaxy collection modules
 
     ```Bash
-   sudo ansible-galaxy collection install ansible.netcommon:==5.0.0 -p /opt/ansible/collections
-   sudo ansible-galaxy collection install ansible.posix:==1.5.1 -p /opt/ansible/collections
-   sudo ansible-galaxy collection install ansible.utils:==2.9.0 -p /opt/ansible/collections
-   sudo ansible-galaxy collection install ansible.windows:==1.13.0 -p /opt/ansible/collections
-   sudo ansible-galaxy collection install community.general:==6.4.0 -p /opt/ansible/collections
+    sudo ansible-galaxy collection install ansible.netcommon:==7.2.0 -p /opt/ansible/collections
+    sudo ansible-galaxy collection install ansible.posix:==2.0.0 -p /opt/ansible/collections
+    sudo ansible-galaxy collection install ansible.utils:==5.1.2 -p /opt/ansible/collections
+    sudo ansible-galaxy collection install ansible.windows:==2.8.0 -p /opt/ansible/collections
+    sudo ansible-galaxy collection install community.general:==10.5.0 -p /opt/ansible/collections
     ```
 
 1. Clone the SAP automation samples repository from GitHub.

articles/storage/blobs/blobfuse2-how-to-deploy.md

@@ -94,18 +94,23 @@ sudo rpm -Uvh https://packages.microsoft.com/config/sles/15/packages-microsoft-p
 sudo yum install blobfuse2
 ```
 
+Similarly, change the package name to `blobfuse2-<version>` to install specific version. 
+
 # [Ubuntu](#tab/Ubuntu)
 
 ```bash
 sudo apt-get install blobfuse2
 ```
+Similarly, change the package name to `blobfuse2=<version>` to install specific version. 
+
 # [SLES](#tab/SLES)
 
 ```bash
 sudo zypper install blobfuse2
 ```
----
+Similarly, change the package name to `blobfuse2-<version>` to install specific version. 
 
+---
 ### Option 2: Build the binaries from source code
 
 To build the BlobFuse2 binaries from source code: