Merge pull request #215647 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/cost-management-billing/reservations/prepay-databricks-reserved-capacity.md

@@ -34,10 +34,11 @@ Before you buy, calculate the total DBU quantity consumed for different workload
 
 ## Purchase Databricks commit units
 
-You can buy Databricks plans in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Reservations/CreateBlade/referrer/documentation/filters/%7B%22reservedResourceType%22%3A%22Databricks%22%7D). To buy reserved capacity, you must have the owner role for at least one enterprise subscription.
+You can buy Databricks plans in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Reservations/CreateBlade/referrer/documentation/filters/%7B%22reservedResourceType%22%3A%22Databricks%22%7D). To buy reserved capacity, you must have the owner role for at least one enterprise or Microsoft Customer Agreement or an individual subscription with pay-as-you-go rates subscription, or the required role for CSP subscriptions.
 
 - You must be in an Owner role for at least one Enterprise Agreement (offer numbers: MS-AZR-0017P or MS-AZR-0148P) or Microsoft Customer Agreement or an individual subscription with pay-as-you-go rates (offer numbers: MS-AZR-0003P or MS-AZR-0023P).
 - For Enterprise subscriptions, **Add Reserved Instances** must be enabled in the [EA portal](https://ea.azure.com/). Or, if that setting is disabled, you must be an EA Admin of the subscription to enable it. Direct EA customers can now update **Reserved Instance** setting on [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_GTM/ModernBillingMenuBlade/AllBillingScopes). Navigate to the Policies menu to change settings.
+- For CSP subscriptions, follow the steps in [Acquire, provision, and manage Azure reserved VM instances (RI) + server subscriptions for customers](/partner-center/azure-ri-server-subscriptions).
 
 
 **To Purchase:**

articles/cost-management-billing/reservations/prepay-sql-data-warehouse-charges.md

@@ -1,5 +1,5 @@
 ---
-title: Save on Azure Synapse Analytics (data warehousing only) charges with Azure reserved capacity
+title: Save on Azure Synapse Analytics - Dedicated SQL pool (formerly SQL DW) charges with Azure reserved capacity
 description: Learn how you save costs for Azure Synapse Analytics charges with reserved capacity to save money.
 author: bandersmsft
 ms.reviewer: sapnakeshari
@@ -10,9 +10,9 @@ ms.date: 10/19/2021
 ms.author: banders
 ---
 
-# Save costs for Azure Synapse Analytics (data warehousing only) charges with reserved capacity
+# Save costs for Azure Synapse Analytics - Dedicated SQL pool (formerly SQL DW) charges with reserved capacity
 
-You can save money with Azure Synapse Analytics (data warehousing only) by committing to a reservation for your cDWU usage for a duration of one or three years. To purchase Azure Synapse Analytics reserved capacity, you need to choose the Azure region, and term. Then, add the Azure Synapse Analytics SKU to your cart and choose the quantity of cDWU units that you want to purchase.
+You can save money with Azure Synapse Analytics - Dedicated SQL pool (formerly SQL DW) by committing to a reservation for your cDWU usage for a duration of one or three years. To purchase Azure Synapse Analytics reserved capacity, you need to choose the Azure region, and term. Then, add the Azure Synapse Analytics SKU to your cart and choose the quantity of cDWU units that you want to purchase.
 
 When you purchase a reservation, the Azure Synapse Analytics usage that matches the reservation attributes is no longer charged at the pay-as-you go rates.
 

articles/cost-management-billing/reservations/synapse-analytics-pre-purchase-plan.md

@@ -34,10 +34,11 @@ For more information about available SCU tiers and pricing discounts, you'll use
 
 ## Purchase Synapse commit units
 
-You buy Synapse plans in the [Azure portal](https://portal.azure.com). To buy a Pre-Purchase Plan, you must have the owner role for at least one enterprise subscription.
+You buy Synapse plans in the [Azure portal](https://portal.azure.com). To buy a Pre-Purchase Plan, you must have the owner role for at least one enterprise or Microsoft Customer Agreement or an individual subscription with pay-as-you-go rates subscription, or the required role for CSP subscriptions.
 
 - You must be in an Owner role for at least one Enterprise Agreement (offer numbers: MS-AZR-0017P or MS-AZR-0148P) or Microsoft Customer Agreement or an individual subscription with pay-as-you-go rates (offer numbers: MS-AZR-0003P or MS-AZR-0023P).
 - For Enterprise Agreement (EA) subscriptions, the **Add Reserved Instances** option must be enabled in the [EA portal](https://ea.azure.com/). Or, if that setting is disabled, you must be an EA Admin of the subscription.
+- For CSP subscriptions, follow the steps in [Acquire, provision, and manage Azure reserved VM instances (RI) + server subscriptions for customers](/partner-center/azure-ri-server-subscriptions).
 
 ### To Purchase:
 

articles/digital-twins/concepts-data-explorer-plugin.md

@@ -134,9 +134,9 @@ Once the target table is created, you can use the Azure Digital Twins plugin to
 
 Here's an example of a schema that might be used to represent shared data.
 
-| `timestamp` | `twinId` | `modelId` | `name` | `value` | `relationshipTarget` | `relationshipID` |
-| --- | --- | --- | --- | --- | --- | --- |
-| 2021-02-01 17:24 | ConfRoomTempSensor | `dtmi:com:example:TemperatureSensor;1` | temperature | 301.0 |  |  |
+| `TimeStamp` | `SourceTimeStamp` | `TwinId` | `ModelId` | `Name` | `Value` | `RelationshipTarget` | `RelationshipID` |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| 2021-02-01 17:24 | 2021-02-01 17:11 | ConfRoomTempSensor | `dtmi:com:example:TemperatureSensor;1` | temperature | 301.0 |  |  |
 
 Digital twin properties are stored as key-value pairs (`name, value`). `name` and `value` are stored as dynamic data types. 
 

articles/service-bus-messaging/service-bus-go-how-to-use-queues.md

@@ -148,10 +148,7 @@ func GetMessage(count int, client *azservicebus.Client) {
 	}
 
 	for _, message := range messages {
-		body, err := message.Body()
-		if err != nil {
-			panic(err)
-		}
+		body := message.Body
 		fmt.Printf("%s\n", string(body))
 
 		err = receiver.CompleteMessage(context.TODO(), message, nil)
@@ -317,10 +314,7 @@ func GetMessage(count int, client *azservicebus.Client) {
 	}
 
 	for _, message := range messages {
-		body, err := message.Body()
-		if err != nil {
-			panic(err)
-		}
+		body := message.Body
 		fmt.Printf("%s\n", string(body))
 
 		err = receiver.CompleteMessage(context.TODO(), message, nil)
@@ -430,4 +424,4 @@ go run main.go
 For more information, check out the following links:
 
 - [Azure Service Bus SDK for Go](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/messaging/azservicebus)
-- [Azure Service Bus SDK for Go on GitHub](https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/messaging/azservicebus)
+- [Azure Service Bus SDK for Go on GitHub](https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/messaging/azservicebus)

articles/stream-analytics/blob-storage-azure-data-lake-gen2-output.md

@@ -70,7 +70,7 @@ To receive exactly once delivery for your Blob storage or ADLS Gen2 account, you
 
 ### Regions Availability
 
-This feature is currently supported in West Central US, Japan East and Canada Central.
+The feature is currently supported in West Central US, Japan East, Canada Central, Korea Central, North Europe, and South India.
 
 ## Blob output files
 

articles/synapse-analytics/sql-data-warehouse/maintenance-scheduling.md

@@ -58,6 +58,10 @@ To view the maintenance schedule that has been applied to your Synapse SQL pool,
 
 A maintenance schedule can be updated or changed at any time. If the selected instance is going through an active maintenance cycle, the settings will be saved. They'll become active during the next identified maintenance period. [Learn more](../../service-health/resource-health-overview.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json) about monitoring your data warehouse during an active maintenance event.
 
+> [!NOTE]
+> In case you are using DW400c or lower, you will not be able to change the maintenance schedule because DW400c and lower data warehouse tiers could complete maintenance outside of a designated maintenance window.
+
+
 ## Identifying the primary and secondary windows
 
 The primary and secondary windows must have separate day ranges. An example is a primary window of Tuesday–Thursday and a secondary of window of Saturday–Sunday.

articles/virtual-network/ip-services/ipv6-overview.md

@@ -75,6 +75,7 @@ The current IPv6 for Azure virtual network release has the following limitations
 - Forward DNS for IPv6 is supported for Azure public DNS today but Reverse DNS is not yet supported.
 - While it is possible to create NSG rules for IPv4 and IPv6 within the same NSG, it is not currently possible to combine an IPv4 Subnet with an IPv6 subnet in the same rule when specifying IP prefixes.
 - ICMPv6 is not currently supported in Network Security Groups.
+- Azure Virtual WAN currently supports IPv4 traffic only.
 
 ## Pricing