Merge pull request #302354 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

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

articles/azure-functions/functions-bindings-signalr-service-trigger.md

@@ -101,7 +101,7 @@ app.generic("function1",
     {
         trigger: { "type": "signalRTrigger", "name": "invocation", "direction": "in", "hubName": "hubName1", "event": "SendMessage", "category": "messages" },
         handler: (triggerInput, context) => {
-            context.log(`Receive ${context.Arguments[0]} from ${triggerInput.ConnectionId}.`)
+            context.log(`Receive ${triggerInput.Arguments[0]} from ${triggerInput.ConnectionId}.`)
         }
     })
 ```

articles/data-factory/connector-google-bigquery.md

@@ -7,7 +7,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 04/14/2025
+ms.date: 06/09/2025
 ---
 
 # Copy data from Google BigQuery V2 using Azure Data Factory or Synapse Analytics
@@ -74,6 +74,7 @@ The following properties are supported for the Google BigQuery linked service.
 | Property | Description | Required |
 |:--- |:--- |:--- |
 | type | The type property must be set to **GoogleBigQueryV2**. | Yes |
+| version |The version that you specify. Recommend upgrading to the latest version to take advantage of the newest enhancements. | Yes for version 1.1 |
 | projectId | The project ID of the default BigQuery project to query against.  | Yes |
 | authenticationType | The OAuth 2.0 authentication mechanism used for authentication.</br>Allowed values are **UserAuthentication** and **ServiceAuthentication**. Refer to sections below this table on more properties and JSON samples for those authentication types respectively. | Yes |
 
@@ -94,6 +95,7 @@ Set "authenticationType" property to **UserAuthentication**, and specify the fol
     "name": "GoogleBigQueryLinkedService",
     "properties": {
         "type": "GoogleBigQueryV2",
+        "version": "1.1",
         "typeProperties": {
             "projectId" : "<project ID>",
             "authenticationType" : "UserAuthentication",
@@ -127,6 +129,7 @@ Set "authenticationType" property to **ServiceAuthentication**, and specify the
     "name": "GoogleBigQueryLinkedService",
     "properties": {
         "type": "GoogleBigQueryV2",
+        "version": "1.1",
         "typeProperties": {
             "projectId": "<project ID>",
             "authenticationType": "ServiceAuthentication",
@@ -220,21 +223,25 @@ To copy data from Google BigQuery, set the source type in the copy activity to *
 
 To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
 
+## <a name="differences-between-google-bigquery-and-google-bigquery-legacy"></a> Google BigQuery connector lifecycle and upgrade
 
-## <a name="upgrade-the-google-bigquery-linked-service"></a> Upgrade the Google BigQuery connector
+The following table shows the release stage and change logs for different versions of the Google BigQuery connector:
 
-To upgrade the Google BigQuery connector, create a new Google BigQuery linked service and configure it by referring to [Linked service properties](#linked-service-properties).
+| Version | Release stage | Change log | 
+| :----------- | :------- | :------- |
+| Google BigQuery V1 | End of support | / |
+| Google BigQuery V2 (version 1.0) | GA version available | • Service authentication is supported by the Azure integration runtime and the self-hosted integration runtime. <br>The properties `trustedCertPath`, `useSystemTrustStore`, `email` and `keyFilePath` are not supported as they are available on the self-hosted integration runtime only. <br><br> • `requestGoogleDriveScope` is not supported. You need additionally apply the permission in Google BigQuery service by referring to [Choose Google Drive API scopes](https://developers.google.com/drive/api/guides/api-specific-auth) and [Query Drive data](https://cloud.google.com/bigquery/docs/query-drive-data). <br><br> • `additionalProjects` is not supported. As an alternative, [query a public dataset with the Google Cloud console](https://cloud.google.com/bigquery/docs/quickstarts/query-public-dataset-console).<br><br> • NUMBER is read as Decimal data type. <br><br> • Timestamp and Datetime are read as DateTimeOffset data type.|
+| Google BigQuery V2 (version 1.1) | GA version available | • Fixed a bug: when executing multiple statements, the `query` now returns the results of the first statement after excluding the evaluation statements, rather than always returning the result of the first statement.  |
 
-## <a name="differences-between-google-bigquery-and-google-bigquery-legacy"></a> Differences between Google BigQuery V2 and V1
+### <a name="upgrade-the-google-bigquery-linked-service"></a> Upgrade the Google BigQuery connector
 
-The Google BigQuery V2 connector offers new functionalities and is compatible with most features of Google BigQuery V1 connector. The table below shows the feature differences between Google BigQuery V2 and V1.
+To upgrade your Google BigQuery connector:
 
-| Google BigQuery V2 | Google BigQuery V1 | 
-| :----------- | :------- |
-| Service authentication is supported by the Azure integration runtime and the self-hosted integration runtime.<br>The properties trustedCertPath, useSystemTrustStore, email and keyFilePath are not supported as they are available on the self-hosted integration runtime only. | Service authentication is only supported by the self-hosted integration runtime. <br>Support trustedCertPath, useSystemTrustStore, email and keyFilePath properties. | 
-| The following mappings are used from Google BigQuery data types to interim data types used by the service internally. <br><br>Numeric -> Decimal<br>Timestamp -> DateTimeOffset<br>Datetime -> DatetimeOffset | The following mappings are used from Google BigQuery data types to interim data types used by the service internally. <br><br>Numeric -> String<br>Timestamp -> DateTime<br>Datetime -> DateTime | 
-| requestGoogleDriveScope is not supported. You need additionally apply the permission in Google BigQuery service by referring to [Choose Google Drive API scopes](https://developers.google.com/drive/api/guides/api-specific-auth) and [Query Drive data](https://cloud.google.com/bigquery/docs/query-drive-data). | Support requestGoogleDriveScope. | 
-| additionalProjects is not supported. As an alternative, [query a public dataset with the Google Cloud console](https://cloud.google.com/bigquery/docs/quickstarts/query-public-dataset-console). | Support additionalProjects. | 
+- **From V1 to V2:**  
+  Create a new Google BigQuery linked service and configure it by referring to [Linked service properties](#linked-service-properties).
+
+- **From V2 version 1.0 to version 1.1:**  
+  In the **Edit linked service** page, select **1.1** for version. For more information, see [Linked service properties](#linked-service-properties).
 
 ## Related content
 

articles/data-factory/media/connector-google-bigquery/configure-google-bigquery-linked-service.png

@@ -72,7 +72,7 @@ The `details` property of the DeployIfNotExists effect has all the subproperties
   - A _location_ property must be specified in the _Deployment_ when using subscription level deployments.
   - Default is _ResourceGroup_.
 - `deployment` (required)
-  - This property should include the full template deployment as it would be passed to the `Microsoft.Resources/deployments` PUT API. For more information, see the [Deployments REST API](/rest/api/resources/deployments).
+  - This property should include the full template deployment as it would be passed to the `Microsoft.Resources/deployments` PUT API. For more information, see the [Deployments REST API](/azure/azure-resource-manager/templates/deploy-rest).
   - Nested `Microsoft.Resources/deployments` within the template should use unique names to avoid contention between multiple policy evaluations. The parent deployment's name can be used as part of the nested deployment name via `[concat('NestedDeploymentName-', uniqueString(deployment().name))]`.
 
   > [!NOTE]

articles/governance/policy/concepts/effect-deploy-if-not-exists.md

@@ -66,7 +66,7 @@ By default, service tags reflect the ranges for the entire cloud. Some service t
 | **[AzureDevOps](/azure/devops/organizations/security/allow-list-ip-url)** | Azure DevOps. | Inbound | Yes | Yes |
 | **[AzureDigitalTwins](/azure/digital-twins/concepts-security#service-tags)** | Azure Digital Twins.<br/><br/>**Note**: This tag or the IP addresses covered by this tag can be used to restrict access to endpoints configured for event routes. | Inbound | No | Yes |
 | **[AzureEventGrid](/azure/event-grid/network-security#service-tags    )** | Azure Event Grid. | Both | No | Yes |
-| **[AzureFrontDoor.Frontend](/azure/frontdoor/origin-security)** <br/> **[AzureFrontDoor.Backend](/azure/frontdoor/origin-security)** <br/> **[AzureFrontDoor.FirstParty](/azure/frontdoor/origin-security)** <br/> **[AzureFrontDoor.MicrosoftSecurity](/azure/frontdoor/origin-security)**  | *Frontend* service tag contains the IP addresses that clients use to reach Front Door. You can apply the **AzureFrontDoor.Frontend** service tag when you want to control the outbound traffic that can connect to services behind Azure Front Door. *Backend* service tag contains the IP addresses that Azure Front Door uses to access your origins. You can apply this service tag when you [configure security for your origins](../frontdoor/origin-security.md). *FirstParty* and *MicrosoftSecurity* are special tags reserved for a select group of Microsoft services hosted on Azure Front Door. | Both | Yes | Yes |
+| **[AzureFrontDoor.Frontend](/azure/frontdoor/origin-security)** <br/> **[AzureFrontDoor.Backend](/azure/frontdoor/origin-security)** <br/> **[AzureFrontDoor.FirstParty](/azure/frontdoor/origin-security)** <br/> **[AzureFrontDoor.MicrosoftSecurity](/azure/frontdoor/origin-security)**  | *Frontend* service tag contains the IP addresses that clients use to reach Front Door. You can apply the **AzureFrontDoor.Frontend** service tag when you want to control the outbound traffic that can connect to services behind Azure Front Door. *Backend* service tag contains the IP addresses that Azure Front Door uses to access your origins. You can apply this service tag when you [configure security for your origins](../frontdoor/origin-security.md). *FirstParty* and *MicrosoftSecurity* are special tags reserved for a select group of Microsoft services hosted on Azure Front Door. *FirstParty* service tag is only available in public cloud while the other service tags are available in public and government clouds. | Both | Yes | Yes |
 | **[AzureHealthcareAPIs](/azure/healthcare-apis/fhir/configure-import-data)**  | The IP addresses covered by this tag can be used to restrict access to Azure Health Data Services. | Both | No | Yes |
 | **AzureInformationProtection** | Azure Information Protection.<br/><br/>**Note**: This tag has a dependency on the **AzureActiveDirectory**, **AzureFrontDoor.Frontend** and **AzureFrontDoor.FirstParty** tags. | Outbound | No | Yes |
 | **AzureIoTHub** | Azure IoT Hub. | Outbound | Yes | Yes |