Merge branch 'master' into piiDetectionSkill

Author: Carey MacDonald

articles/cost-management-billing/costs/index.yml

@@ -10,7 +10,7 @@ metadata:
   ms.collection: collection
   author: bandersmsft
   ms.author: banders
-  ms.date: 01/24/2020
+  ms.date: 01/28/2020
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | whats-new
 
@@ -89,9 +89,12 @@ landingContent:
     - linkListType: whats-new
       links:
       - text: Monthly updates
-        url: https://azure.microsoft.com/blog/tag/cost-management/
+        url: https://azure.microsoft.com/blog/tag/cost-management
       - text: Feature updates
-        url: https://azure.microsoft.com/updates/?product=cost-management
+        url: https://azure.microsoft.com/updates/cost-management-features-now-available-october-2019
+      - text: Features in development
+        url: https://azure.microsoft.com/updates/azure-cost-management-features-in-development-october-2019
+
 
   # Card (optional)
   - title: Analyze and manage AWS costs

articles/cost-management-billing/reservations/reserved-instance-purchase-recommendations.md

@@ -1,6 +1,6 @@
 ---
-title: How reservation recommendations are created
-description: Learn how reservation recommendations are created for virtual machines.
+title: How Azure reservation recommendations are created
+description: Learn how Azure reservation recommendations are created for virtual machines.
 author: banders
 ms.reviewer: yashar
 ms.service: cost-management-billing

articles/governance/policy/overview.md

@@ -3,6 +3,7 @@ title: Overview of Azure Policy
 description: Azure Policy is a service in Azure, that you use to create, assign and, manage policy definitions in your Azure environment.
 ms.date: 11/25/2019
 ms.topic: overview
+ms.custom: fasttrack-edit
 ---
 # What is Azure Policy?
 
@@ -90,11 +91,11 @@ To learn more about the structures of policy definitions, review
 ## Policy assignment
 
 A policy assignment is a policy definition that has been assigned to take place within a specific
-scope. This scope could range from a [management group](../management-groups/overview.md) to a
-resource group. The term *scope* refers to all the resource groups, subscriptions, or management
-groups that the policy definition is assigned to. Policy assignments are inherited by all child
-resources. This design means that a policy applied to a resource group is also applied to resources
-in that resource group. However, you can exclude a subscope from the policy assignment.
+scope. This scope could range from a [management group](../management-groups/overview.md) to an
+individual resource. The term *scope* refers to all the resources, resource groups, subscriptions,
+or management groups that the policy definition is assigned to. Policy assignments are inherited
+by all child resources. This design means that a policy applied to a resource group is also applied
+to resources in that resource group. However, you can exclude a subscope from the policy assignment.
 
 For example, at the subscription scope, you can assign a policy that prevents the creation of
 networking resources. You could exclude a resource group in that subscription that is intended for
@@ -155,7 +156,7 @@ Under this initiative, you would have policy definitions such as:
 
 Like a policy assignment, an initiative assignment is an initiative definition assigned to a
 specific scope. Initiative assignments reduce the need to make several initiative definitions for
-each scope. This scope could also range from a management group to a resource group.
+each scope. This scope could also range from a management group to an individual resource.
 
 Each initiative is assignable to different scopes. One initiative can be assigned to both
 **subscriptionA** and **subscriptionB**.
@@ -234,4 +235,4 @@ next steps:
 
 - [Assign a policy definition using the portal](./assign-policy-portal.md).
 - [Assign a policy definition using the Azure CLI](./assign-policy-azurecli.md).
-- [Assign a policy definition using PowerShell](./assign-policy-powershell.md).
+- [Assign a policy definition using PowerShell](./assign-policy-powershell.md).

articles/sql-data-warehouse/sql-data-warehouse-develop-transactions.md

@@ -20,7 +20,7 @@ Tips for implementing transactions in Azure SQL Data Warehouse for developing so
 As you would expect, SQL Data Warehouse supports transactions as part of the data warehouse workload. However, to ensure the performance of SQL Data Warehouse is maintained at scale some features are limited when compared to SQL Server. This article highlights the differences and lists the others. 
 
 ## Transaction isolation levels
-SQL Data Warehouse implements ACID transactions. However, the isolation level of the transactional support is limited to READ UNCOMMITTED; this level cannot be changed. If READ UNCOMMITTED is a concern, you can implement a number of coding methods to prevent dirty reads of data. The most popular methods use both CTAS and table partition switching (often known as the sliding window pattern) to prevent users from querying data that is still being prepared. Views that pre-filter the data are also a popular approach.  
+SQL Data Warehouse implements ACID transactions. The isolation level of the transactional support is default to READ UNCOMMITTED.  You can change it to READ COMMITTED SNAPSHOT ISOLATION by turning ON the READ_COMMITTED_SNAPSHOT database option for a user database when connected to the master database.  Once enabled, all transactions in this database are executed under READ COMMITTED SNAPSHOT ISOLATION and setting READ UNCOMMITTED on session level will not be honored. Check [ALTER DATABASE SET options (Transact-SQL)](https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql-set-options?view=azure-sqldw-latest) for details.
 
 ## Transaction size
 A single data modification transaction is limited in size. The limit is applied per distribution. Therefore, the total allocation can be calculated by multiplying the limit by the distribution count. To approximate the maximum number of rows in the transaction divide the distribution cap by the total size of each row. For variable length columns, consider taking an average column length rather than using the maximum size.