Merge pull request #287306 from MicrosoftDocs/main

Merge main to live, 4 AM

Author: v-ccolin

articles/backup/sap-hana-backup-support-matrix.md

@@ -2,7 +2,7 @@
 title: SAP HANA Backup support matrix
 description: In this article, learn about the supported scenarios and limitations when you use Azure Backup to back up SAP HANA databases on Azure VMs.
 ms.topic: reference
-ms.date: 09/11/2024
+ms.date: 09/25/2024
 ms.custom: references_regions 
 ms.service: azure-backup
 author: AbhishekMallick-MS
@@ -49,7 +49,6 @@ Azure Backup supports the backup of SAP HANA databases to Azure. This article su
 
 ## Support for multistreaming data backups
 
-- **Supported HANA versions**: SAP HANA 2.0 SP05 and prior.
 - **Parameters to enable SAP HANA settings for multistreaming**: 
   - *parallel_data_backup_backint_channels*
   - *data_backup_buffer_size (optional)*

articles/backup/scripts/geo-code-list.md

@@ -49,7 +49,7 @@ This sample XML provides you an insight about the geo-codes mapped with the resp
   <GeoCodeRegionNameMap GeoCode="gec" RegionName="Germany Central" />
   <GeoCodeRegionNameMap GeoCode="gne" RegionName="Germany Northeast" />
   <GeoCodeRegionNameMap GeoCode="krc" RegionName="Korea Central" />
-  <GeoCodeRegionNameMap GeoCode="frc" RegionName="France Central" />
+  <GeoCodeRegionNameMap GeoCode="fc" RegionName="France Central" />
   <GeoCodeRegionNameMap GeoCode="frs" RegionName="France South" />
   <GeoCodeRegionNameMap GeoCode="krs" RegionName="Korea South" />
   <GeoCodeRegionNameMap GeoCode="ugt" RegionName="USGov Texas" />
@@ -86,4 +86,4 @@ This sample XML provides you an insight about the geo-codes mapped with the resp
 
 ## Next steps
 
-[Learn](../private-endpoints.md) to create and add DNS zones for Azure Backup private endpoints using geo-codes.
+[Learn](../private-endpoints.md) to create and add DNS zones for Azure Backup private endpoints using geo-codes.

articles/communication-services/concepts/telephony/emergency-calling-concept.md

@@ -15,17 +15,17 @@ ms.subservice: pstn
 
 [!INCLUDE [Emergency Calling Notice](../../includes/emergency-calling-notice-include.md)]
 
-You can use the Azure Communication Services Calling SDK to add Enhanced Emergency dialing and Public Safety Answering Point (PSAP) callback support to your applications in the United States (US), Puerto Rico (PR), the United Kingdom (GB), Canada (CA), and Denmark (DK). The capability to dial 911 (in US, PR, and CA), to dial 112 (in DK), and to dial 999 or 112 (in GB) and receive a callback might be a requirement for your application. Verify the emergency calling requirements with your legal counsel.
+You can use the Azure Communication Services Calling SDK to add Enhanced Emergency dialing and Public Safety Answering Point (PSAP) callback support to your applications in the United States (US), Puerto Rico (PR), the United Kingdom (GB), Canada (CA), Denmark (DK) and Australiua (AU). The capability to dial 911 (in US, PR, and CA), to dial 112 (in DK), to dial 000 (in AU) and to dial 999 or 112 (in GB) and receive a callback might be a requirement for your application. Verify the emergency calling requirements with your legal counsel.
 
-Calls to an emergency number are routed over the Microsoft network. Microsoft assigns a temporary phone number as the Call Line Identity (CLI) when a user places an emergency call from US, PR, GB, CA, or DK. Microsoft temporarily maintains a mapping of the phone number to the caller's identity.
+Calls to an emergency number are routed over the Microsoft network. Microsoft assigns a temporary phone number as the Call Line Identity (CLI) when a user places an emergency call from US, PR, GB, CA, DK or AU. Microsoft temporarily maintains a mapping of the phone number to the caller's identity.
 
 If there's a callback from the PSAP, Microsoft routes the call directly to the originating caller. The caller can accept the incoming PSAP call even if inbound calling is disabled.
 
 The service is available for Microsoft phone numbers. It requires the Azure resource that the emergency call originates from to have a Microsoft-issued phone number enabled with outbound dialing (also known as *make calls*).
 
 ## Call flow
 
-1. An Azure Communication Services user identity dials an emergency number by using the Calling SDK from US or PR.
+1. An Azure Communication Services user identity dials an emergency number by using the Calling SDK.
 1. Microsoft validates that the Azure resource has a Microsoft phone number enabled for outbound dialing.
 1. The Microsoft Azure Communication Services emergency service replaces the user's phone number (the `alternateCallerId` value) with a temporary unique phone number. This number allocation remains in place for at least 60 minutes from the time that the emergency number is dialed.
 1. Microsoft maintains a temporary record (for about 60 minutes) that maps the unique phone number to the user identity.
@@ -43,7 +43,7 @@ Emergency calling is automatically enabled for all users of the Azure Communicat
 
     - Microsoft uses the ISO 3166-1 alpha-2 standard for country/region codes.
 
-    - Microsoft supports US, PR, GB, CA, and DK country/region codes for emergency number dialing.
+    - Microsoft supports US, PR, GB, CA, DK or AU country/region codes for emergency number dialing.
 
     - If you don't provide the country/region code to the SDK, Microsoft uses the IP address to determine the country or region of the caller.
 
@@ -72,4 +72,4 @@ There's also an option to use a purchased number as a caller ID for direct routi
 Try these quickstarts:
 
 - [Outbound call to a phone number](../../quickstarts/telephony/pstn-call.md)
-- [Add emergency calling to your app](../../quickstarts/telephony/emergency-calling.md)
+- [Add emergency calling to your app](../../quickstarts/telephony/emergency-calling.md)

articles/communication-services/includes/emergency-calling-notice-include.md

@@ -8,6 +8,6 @@ ms.author: bobazile
 ms.custom: emergency_calling
 ---
 > [!IMPORTANT]
-> Azure Communication Services supports emergency calling to emergency numbers in the United States, Puerto Rico, Canada, Denmark, and the United Kingdom only.
+> Azure Communication Services supports emergency calling to emergency numbers in the United States, Puerto Rico, Canada, Denmark, United Kingdom and Australia only.
 >
-> Azure Communication Services voice calling (PSTN) can be used to dial emergency number 911 in the United States, Puerto Rico, and Canada, to dial emergency number 112 in Denmark, and to dial emergency numbers 999 and 112 in the United Kingdom. Azure Communication Services doesn't currently support dialing those emergency numbers from outside those countries or regions, or dialing emergency services in other countries or regions.
+> Azure Communication Services voice calling (PSTN) can be used to dial emergency number 911 in the United States, Puerto Rico, and Canada, to dial emergency number 112 in Denmark, to dial 000 in Australia and to dial emergency numbers 999 and 112 in the United Kingdom. Azure Communication Services doesn't currently support dialing those emergency numbers from outside those countries or regions, or dialing emergency services in other countries or regions.

articles/data-factory/connector-azure-cosmos-db.md

@@ -7,7 +7,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 08/13/2024
+ms.date: 09/04/2024
 ---
 
 # Copy and transform data in Azure Cosmos DB for NoSQL by using Azure Data Factory
@@ -222,7 +222,7 @@ You can also store service principal key in Azure Key Vault.
 ### <a name="managed-identity"></a> System-assigned managed identity authentication
 
 >[!NOTE]
->Currently, the system-assigned managed identity authentication is not supported in data flow.
+>Currently, the system-assigned managed identity authentication is supported in data flows through the use of advanced properties in JSON format.
 
 A data factory or Synapse pipeline can be associated with a [system-assigned managed identity for Azure resources](data-factory-service-identity.md#system-assigned-managed-identity), which represents this specific service instance. You can directly use this managed identity for Azure Cosmos DB authentication, similar to using your own service principal. It allows this designated resource to access and copy data to or from your Azure Cosmos DB instance.
 
@@ -240,6 +240,9 @@ These properties are supported for the linked service:
 | accountEndpoint | Specify the account endpoint URL for the Azure Cosmos DB instance. | Yes |
 | database | Specify the name of the database. | Yes |
 | connectVia | The [integration runtime](concepts-integration-runtime.md) to be used to connect to the data store. You can use the Azure integration runtime or a self-hosted integration runtime if your data store is in a private network. If not specified, the default Azure integration runtime is used. |No |
+| subscriptionId | Specify the subscription id for the Azure Cosmos DB instance | No for Copy Activity, Yes for Mapping Data Flow |
+| tenantId | Specify the tenant id for the Azure Cosmos DB instance | No for Copy Activity, Yes for Mapping Data Flow |
+| resourceGroup | Specify the resource group name for the Azure Cosmos DB instance | No for Copy Activity, Yes for Mapping Data Flow |
 
 **Example:**
 
@@ -250,7 +253,10 @@ These properties are supported for the linked service:
         "type": "CosmosDb",
         "typeProperties": {
             "accountEndpoint": "<account endpoint>",
-            "database": "<database name>"
+            "database": "<database name>",
+            "subscriptionId": "<subscription id>",
+            "tenantId": "<tenant id>",
+            "resourceGroup": "<resource group>"
         },
         "connectVia": {
             "referenceName": "<name of Integration Runtime>",

articles/data-factory/connector-microsoft-fabric-warehouse.md

@@ -7,7 +7,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 02/23/2024
+ms.date: 09/04/2024
 ---
 
 # Copy and transform data in Microsoft Fabric Warehouse using Azure Data Factory or Azure Synapse Analytics
@@ -23,6 +23,7 @@ This Microsoft Fabric Warehouse connector is supported for the following capabil
 | Supported capabilities|IR | Managed private endpoint|
 |---------| --------| --------|
 |[Copy activity](copy-activity-overview.md) (source/sink)|① ②|✓ |
+|[Mapping data flow](concepts-data-flow-overview.md) (source/sink)|① |✓ |
 |[Lookup activity](control-flow-lookup-activity.md)|① ②|✓ |
 |[GetMetadata activity](control-flow-get-metadata-activity.md)|① ②|✓ |
 |[Script activity](transform-data-using-script.md)|① ②|✓ |
@@ -513,6 +514,47 @@ To use this feature, create an [Azure Blob Storage linked service](connector-azu
 ]
 ```
 
+## Mapping data flow properties
+
+When transforming data in mapping data flow, you can read and write to tables from Microsoft Fabric Warehouse. 
+For more information, see the [source transformation](data-flow-source.md) and [sink transformation](data-flow-sink.md) in mapping data flows.
+
+### Microsoft Fabric Warehouse as the source
+Settings specific to Microsoft Fabric Warehouse are available in the Source Options tab of the source transformation.
+
+| Name                     | Description                                                  | Required | Allowed Values | Data flow script property |
+| :--------------------------- | :----------------------------------------------------------- | :------- |:-------------------- |:------- |
+| Input                          | Select whether you point your source at a table (equivalent of Select * from tablename) or enter a custom SQL query or retrieve data from a Stored Procedure. Query: If you select Query in the input field, enter a SQL query for your source. This setting overrides any table that you've chosen in the dataset. **Order By** clauses aren't supported here, but you can set a full SELECT FROM statement. You can also use user-defined table functions. **select * from udfGetData()** is a UDF in SQL that returns a table. This query will produce a source table that you can use in your data flow. Using queries is also a great way to reduce rows for testing or for lookups.SQL Example: ```Select * from MyTable where customerId > 1000 and customerId < 2000``` | Yes      | Table or Query or Stored Procedure    | format: 'table' |
+| Batch size               | Enter a batch size to chunk large data into reads. In data flows, this setting will be used to set Spark columnar caching. This is an option field, which will use Spark defaults if it is left blank. | No       | Numeral values | batchSize: 1234|
+| Isolation Level          | The default for SQL sources in mapping data flow is read uncommitted. You can change the isolation level here to one of these values:•	Read Committed  • Read Uncommitted • Repeatable Read • Serializable • None (ignore isolation level) | Yes       | •	Read Committed  • Read Uncommitted • Repeatable Read • Serializable • None (ignore isolation level) | isolationLevel|
+
+>[!NOTE]
+>Read via staging is not supported. CDC support for Microsoft Fabric Warehouse source is currently not available.
+
+### Microsoft Fabric Warehouse as the sink
+Settings specific to Microsoft Fabric Warehouse are available in the Settings tab of the sink transformation.
+
+| Name                     | Description                                                  | Required | Allowed Values | Data flow script property |
+| :--------------------------- | :----------------------------------------------------------- | :------- |:-------------------- |:------- |
+| Update method                         | Determines what operations are allowed on your database destination. The default is to only allow inserts. To update, upsert, or delete rows, an alter-row transformation is required to tag rows for those actions. For updates, upserts and deletes, a key column or columns must be set to determine which row to alter. | Yes      | true or false    | insertable deletable upsertable updateable |
+| Table action              | Determines whether to recreate or remove all rows from the destination table prior to writing.• None: No action will be done to the table. • Recreate: The table will get dropped and recreated. Required if creating a new table dynamically.• Truncate: All rows from the target table will get removed. | No       | None or recreate or truncate | recreate: true truncate: true |
+| Enable staging          | The staging storage is configured in [Execute Data Flow activity](control-flow-execute-data-flow-activity.md). When you use managed identity authentication for your storage linked service, learn the needed configurations for [Azure Blob](connector-azure-blob-storage.md#managed-identity) and [Azure Data Lake Storage Gen2](connector-azure-data-lake-storage.md#managed-identity) respectively.If your Azure Storage is configured with VNet service endpoint, you must use managed identity authentication with "allow trusted Microsoft service" enabled on storage account, refer to [Impact of using VNet Service Endpoints with Azure storage](/azure/azure-sql/database/vnet-service-endpoint-rule-overview#impact-of-using-virtual-network-service-endpoints-with-azure-storage).| No       | true or false |staged: true |
+| Batch size               | Controls how many rows are being written in each bucket. Larger batch sizes improve compression and memory optimization, but risk out of memory exceptions when caching data. | No       | Numeral values | batchSize: 1234|
+| Use sink schema             | By default, a temporary table will be created under the sink schema as staging. You can alternatively uncheck the **Use sink schema** option and instead, in **Select user DB schema**, specify a schema name under which Data Factory will create a staging table to load upstream data and automatically clean them up upon completion. Make sure you have create table permission in the database and alter permission on the schema. | No       | true or false | stagingSchemaName|
+| Pre and Post SQL scripts   | Enter multi-line SQL scripts that will execute before (pre-processing) and after (post-processing) data is written to your Sink database| No       | SQL scripts | preSQLs:['set IDENTITY_INSERT mytable ON'] postSQLs:['set IDENTITY_INSERT mytable OFF'],|
+
+### Error row handling
+By default, a data flow run will fail on the first error it gets. You can choose to Continue on error that allows your data flow to complete even if individual rows have errors. The service provides different options for you to handle these error rows.
+ 
+Transaction Commit: Choose whether your data gets written in a single transaction or in batches. Single transaction will provide better performance and no data written will be visible to others until the transaction completes. Batch transactions have worse performance but can work for large datasets.
+ 
+Output rejected data: If enabled, you can output the error rows into a csv file in Azure Blob Storage or an Azure Data Lake Storage Gen2 account of your choosing. This will write the error rows with three additional columns: the SQL operation like INSERT or UPDATE, the data flow error code, and the error message on the row.
+ 
+Report success on error: If enabled, the data flow will be marked as a success even if error rows are found.
+
+>[!NOTE]
+>For Microsoft Fabric Warehouse Linked Service, the supported authentication type for Service Principal is 'Key'; 'Certificate' authentication is not supported.
+
 ## Lookup activity properties
 
 To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
@@ -548,4 +590,4 @@ When you copy data from Microsoft Fabric Warehouse, the following mappings are u
 
 ## Next steps
 
-For a list of data stores supported as sources and sinks by the copy activity, see [Supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).
+For a list of data stores supported as sources and sinks by the copy activity, see [Supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).